The system finally feels coherent. Meetings are calmer, the language is aligned, escalation has dropped. It feels ready. So you move to make it official – name the strategy, formalise the operating model, lock the design.
But pause on what “ready” is actually telling you.
Those signals are real, and they are good. They are also exactly the signals a leader is trained to read as readiness.
And they are not.
Calmer meetings and aligned language do not mean the system can reason its way through a hard, novel case on its own. They mean it has stopped fighting itself. That is a necessary step. It is not the same as being able to carry intent – and the two feel almost identical from the inside.
Because early coherence and genuine readiness look the same on the surface. The difference does not show in calm conditions. It shows in variance – when conditions shift, when the numbers turn, when the senior person is not in the room. That is the only place readiness is visible, and it is precisely the place the reassuring signals never test.
So readiness is not a feeling. It is a set of things you can actually watch for. The same logic holds as situations differ, without an alignment meeting to re-establish it. Escalation changes character: it arrives with context and names the boundary, asking for judgement rather than rescue. The decision logic holds when the numbers disappoint and the trade-offs sharpen, not only when things are going well. And the fourth signal is not in the system at all. It is in you – the particular discomfort of not stepping in when you know you could. When that restraint stops feeling like neglect, the system has usually started carrying itself.
Name the strategy before those hold, and you do not get a system executing clear intent.
You get a system performing the language of it.
The words align within weeks – they always do, language is cheap – while the judgement underneath is still forming. And now it is forming under a name, which means it is forming under pressure to match the words rather than to reason freely. You have given the system a script before it learned to think, and scripts are easy to recite and hard to depart from.
But the part most worth sitting with is why the move gets made early. The honest answer is often not about the system at all. The board wants the strategy. The market expects a narrative. A leader is supposed to look like they have it handled. The pressure to articulate frequently comes from how leadership needs to appear – settled, in control, ahead of it – rather than from any change in how the system actually reasons. And a system named to serve the leader’s need to look ready is being asked to carry something it never showed it could.
Which is the question underneath the timing. Not “does this feel coherent?” – it will, or you would not be tempted. The question is what is actually driving the urge to name it now. A change in how the system reasons, demonstrated under real variance? Or a change in what leadership needs to project? The first earns the articulation.
The second compresses uncertainty into language and calls it progress.
Articulation is not the reward for coherence. It is a bet that the system can carry what you are about to make permanent – and the only honest basis for that bet is evidence the system has reasoned well when it was hard, not the relief of it finally feeling calm. When your organisation last articulated strategy or formalised an operating model, was the trigger a change in how the system was reasoning – or a change in how leadership needed to appear?
This question closes a chapter of The Architecture of Commercial Performance, where the thinking behind it is developed in full.
