A credible plan prepares decisions for the conditions that may move the result in either direction.
The launch plan is green. The supplier date is confirmed, training is booked and go-live is Tuesday.
On Friday, the supplier says the delivery will be six working days late. Procurement has a qualified alternative but needs approval for the higher price. Operations can use the old material at higher scrap. The project manager can arrange a meeting.
Nobody can decide.
Uncertainty did not sink the launch. The missing decision did.
A schedule follows one route
A schedule gives us tasks, dates, dependencies and owners. It describes the intended route under expected conditions.
The line stays straight because PowerPoint still has no pothole tool.
Implementation takes place under moving conditions. A supplier slips. Testing exposes a weakness. Demand arrives early. A pilot beats its target.
A credible implementation plan must therefore do more than coordinate work. It must protect the intended result when an important condition moves in either direction.
The answer is not to predict every surprise. It is to prepare decisions around the uncertainties that could materially change the result.
Make the important conditions visible
For every major result, the plan needs to establish:
- what must be true for the result to be achieved;
- what evidence will show whether it still holds;
- the threshold that requires a decision;
- the prepared response if events move against or in favour of the result; and
- who has the authority, information and resources to act.
“The supplier may be late” is an observation. It is not yet a response.
“If the confirmed delivery moves by more than three working days, Procurement activates the qualified alternative within 24 hours, up to the agreed cost limit” can be acted upon.
The trigger is visible. The response exists. Authority has been settled before the pressure arrives.
Without those three things, “mitigation” often means that people will discuss the problem after it has already chosen the timetable for them.
The better-than-expected result also needs a route
Suppose a pilot reduces rework by 18%. Everyone congratulates the team. Then nothing travels.
The process owner cannot change the standard in another unit. Finance has not tested the result at full volume. No training capacity was reserved beyond the pilot. The opportunity remains a local story.
An opportunity is not a benefit until the organisation can use it.
The plan should therefore contain a positive decision rule as well. For example: if the pilot reduces rework by at least 15% across two shifts, without creating a safety or quality trade-off, the process owner starts a controlled trial in the next unit within ten working days.
That is not blind expansion. It is a prepared next test.
Looking both ways does not mean forcing every uncertainty into a box marked threat or opportunity. The same event may do both. An early surge in orders may improve revenue while damaging delivery and cash. The plan must protect the objective as a whole, not celebrate one attractive number.
Give the decision to somebody who can make it
Naming an owner is easy. Giving that person enough decision power is harder.
A backup supplier is not a response until it has been checked, the commercial limits are known and somebody can activate it. A stop-work rule is decorative if the person seeing the danger must find three travelling managers before using it.
Where implementation crosses functions, decision rights must cross with it—or goals, thresholds and escalation must be aligned well enough that the decision does not die between departments.
The owner needs enough authority for the agreed response and immediate access to the person who holds the rest.
Make evidence change the plan
Implementation reviews should not be guided mainly by green activity boxes.
Training completed is not the same as people performing the new process correctly. A system going live is not evidence that it handles the required volume. A procedure being issued says nothing about whether the result improved.
The review must compare actual evidence with the result, assumptions and thresholds. When a threshold is crossed, a decision follows. When the evidence changes, the plan changes.
Otherwise the organisation protects the original promise while losing the reason the project existed.
This is what addressing risks and opportunities should look like inside an ISO 9001 management system: not an ornamental register beside the implementation plan, but decisions, evidence and authority that help achieve the intended result while conditions remain uncertain. The sixth edition is under publication and scheduled for 16 September 2026, with greater clarity on risks and opportunities.
An implementation plan cannot make the future behave. It can make sure that, when the future does not behave, people know what result they are protecting, what evidence matters, who decides and what happens next.
If your implementation plan is a fine schedule but a poor decision system, send me a message. I can help you find where decisions, evidence or authority will get stuck before the project does.