In the last piece I described a deployment that was designed right, built right, and signed off by everyone — and stalled at the wall when the site decided, at go-live, that it wasn't ready. I ended on a claim I want to make good on: readiness isn't a softer word for motivation; it's closer to architecture. So here's the harder question. If the problem isn't conviction, what do you actually build?
Two things, it turns out. An owner, and a gate.
Champion ≠ Owner
We had change champions. Good ones. And they still couldn't move it, because a champion is built to supply conviction, not authority. A champion can explain why the system matters, model enthusiasm, answer questions in the town hall. What a champion cannot do is free up an operator's afternoon, reorder the site's competing priorities, or decide that a stack of SOPs will be rewritten before go-live. Those are the constraints that actually determine whether a site can absorb a system — and they sit with line management, not with the champion we appointed to carry the message to them.
So the role that was missing wasn't more advocacy. It was an Operational Readiness Owner: a single named person, on the receiving side, accountable for whether the organization is ready to run the thing — and holding real authority over the constraints that decide it. Not a messenger. A decision-maker.
And the timing matters as much as the title. We named champions once the build was underway. An Operational Readiness Owner has to be named at initiation, before a line of code — because their first job is the one nobody did: telling us, early, what readiness would actually cost.
Change Champion
- Supplies conviction & the "why"
- Models enthusiasm, fields questions
- Can't free capacity
- Can't reorder priorities
- Can't mandate SOP rework
- Named once the build is underway
Operational Readiness Owner
- Holds authority over the line's constraints
- Allocates capacity
- Sets priority
- Mandates rework up front
- Can say no
- Named at project initiation
Commission the organization like equipment.
Here's the discipline we already have, sitting right next to us, that we never thought to point at ourselves.
We would never energize a new line without commissioning it. Installation qualification: is it installed correctly? Operational qualification: does it run across its range? Performance qualification: does it hold up under real conditions, repeatedly? IQ, OQ, PQ. No one argues about this. No one ships a skid to the floor and finds out at startup whether the utilities are connected.
We ship organizations to the floor that way all the time.
So name the parallel and run it. Organizational Commissioning — the same three gates, pointed at the people and the procedures instead of the pipes.
do this
never do
A review that puts three maps on one sheet.
The last piece ended on three maps of the same site: where leadership thought it was, where the project team aimed, and where the site actually stood. The failure wasn't that the maps differed — maps always differ. The failure was that nobody made them disagree out loud until go-live.
That's what the gate is for. A Readiness Review, early, co-owned by the Operational Readiness Owner, whose entire purpose is to force the three maps onto one sheet while the cost of changing course is still low. Not a status update. A go/no-go with the authority to actually say no — the organizational equivalent of a commissioning gate that can hold a startup.
"Not now" is a finding, not a failure.
Here's the part that's hardest to accept and most worth it: the point of commissioning is not to pass. It's to tell you the truth.
A gate that can only return "go" isn't a gate; it's a formality. The value of Organizational Commissioning is that it can return not now — early, cheaply, and with evidence — instead of letting a site discover the same answer at go-live after the money is spent and the team is exhausted. A disciplined "not now" is the system working. It tells you the scope was too big, or the timing was wrong, or the capacity was never real — at the point where you can still do something about it.
Readiness is something you install.
I keep coming back to the same place. The reason leadership's ambition doesn't reach the floor isn't that the floor lacks will. It's that readiness was never installed — and you can't motivate your way to a thing that has to be built. We know how to commission equipment because we've been burned by skipping it. We're still learning that the organization is part of the system, and that it has to be commissioned too.
Give it an owner. Give the owner authority. Run the gates. And let the first honest "not ready" arrive while it's still cheap to hear.