Plan the change workflow

1. Several channels can feed a coherent record

A request may arrive through a meeting, email or work tool. The plan should explain how communication becomes a trackable record: who registers it, what information makes the proposal understandable and how the sender receives its reference.

Banning every channel except one is unnecessary if a reliable recording process exists. In a fictional example, Business requests an earlier close and APS sends a message about the same proposal. These may contribute to one request while retaining both origins and concerns.

Conversely, two messages titled “change close” may propose different days or consumers. Plan confirmation of identity and intent before merging records. Message count does not equal the number of distinct changes.

If a proposal evolves, preserve differences relevant to whoever analyzes it. Organized intake should reduce context loss without demanding information impossible to know before analysis itself.

2. Define each state's meaning and exit condition

Received may mean only that a record exists. Ready for analysis may require an identifiable proposal and a contact for clarification. Analyzed may mean impacts were documented while a decision remains pending.

Choose enough states for actual work and define transition owner, evidence and next recipient. In a fictional workflow, analysis ends when it includes proposed behavior, dependencies, alternatives and known impact; uncertainty may remain explicit.

The decision maker may accept, reject or request further information under agreed rules. An information request should neither disappear from the queue nor return as a history-free request. Approval also does not establish implementation: it may depend on a window or confirmation of a dependency.

These states illustrate a design, not a mandatory PMI sequence. Their usefulness is showing what happened and what remains, avoiding “closed” for different decisions and outcomes.

3. Classify by effect and mandate

The plan may allow spelling corrections through a simple route and require different analysis for behavioral changes. The criterion should be explicit. Correcting a letter in a heading, with no effect on identifiers, contracts or meaning, may fit documentary delegation.

Replacing “business days” with “calendar days” changes a condition even though only two words change. Edited text size does not measure impact. It also helps to distinguish restoration of approved behavior from a request for a different capability during an incident.

If an authorized operational procedure permits recovery of known configuration, that action follows the applicable mandate. Changing the service commitment to prevent future failures is a separate proposal requiring its own analysis and decision.

Link records sharing an origin without turning the incident into unlimited authorization. Classification should route work to those able to decide and act while preserving what the simpler route permits without adding an unrequired committee.

4. Specify what the deadline actually promises

A four-hour acknowledgement target does not promise completed analysis or implementation. Define starting event, ending event, calendar and waiting treatment. In this exercise, the team works Monday to Friday, 09:00 to 17:00, with no holidays in one time zone.

Four working hours after Monday at 15:00 end Tuesday at 11:00. If a different rule pauses counting when information is requested Monday at 16:00 and resumes it on receipt Tuesday at 10:00, the deadline becomes Tuesday at 13:00: one hour was consumed before the pause and three remain.

Do not apply a pause unless the rule exists. Record start, suspension, resumption and reason when these conditions belong to the agreement. An exceeded target should trigger the defined action, such as communicating delay or reallocating analysis; it does not mean approval by silence unless an applicable explicit rule actually provides that.

5. Make team handoffs visible

A sent task is not necessarily a task received by someone able to execute it. The workflow needs to identify who owns the next step, what happens when information is missing and how the sender sees that situation. In an international example, APS completes analysis and sends a link to a mailbox with no owner available for two days.

“Analyzed” may be accurate, but the decision has no operationally available recipient. Plan coverage, authorized substitution and target handling; an alternative recipient is not automatically a new approval authority. At implementation handoff, retain decision conditions, proposal version and any time limits.

If a condition expires, the queue should not treat approval as current authorization merely because the request number stays the same. A short report can distinguish requests waiting for information, a decision, a window or outcome confirmation. That distinction supports action on the cause of waiting.

6. Workshop: separate recovery, proposal and document correction

Prepare a table of request, route, next owner and completion evidence for three fictional situations. A: during a failure, an authorized operational procedure restores approved configuration. B: someone proposes accepting instructions after the close cutoff to reduce future rejections.

C: the document owner may correct a heading typo without changing meaning, identifiers or contracts; that absence of effect was confirmed. Worked reasoning: A follows the defined operational route, retaining the record and recovery confirmation; B is recorded and analyzed as a change to agreed behavior; C may follow the simple delegation with correction history.

If B arose during A, link its origin without transferring recovery authorization to the new commitment. Add that “received within four working hours” does not promise a decision in that period. Exercise the workflow with a duplicate request, an incomplete response and an expired implementation condition.

Identify the part of the plan addressing each situation before selecting a tool.

Common pitfalls

Confusing receipt with decision; merging matching titles without comparing proposals; turning delay into approval; using an urgent route beyond its mandate.