The board wants the operating model. The ideal customer profile. The playbook. The metrics framework.
Every item on that list is reasonable. Each one is somewhere you genuinely need to get to.
So when the slide goes up, the instinct is to deliver. Produce the artefacts, show the progress, demonstrate that you are building the thing. Anything else can sound like you do not have a plan.
But notice what each of those artefacts actually is.
An operating model encodes how authority is distributed.
A customer profile encodes which opportunities you pursue.
A playbook encodes how judgement should be exercised in front of a buyer.
Each one writes down a decision the system has already made.
Which means the real question is not whether to build them.
It is whether the system has decided yet.
Codify too early and you do not capture how the organisation works.
You freeze how it was guessing.
The playbook captures current behaviour, not the behaviour that holds once sellers have met enough pressure to tell what works from what merely sounds right. The customer profile fixes today’s pipeline assumptions before the pattern has shown itself. You write it all down, and it looks like a system. But it is a snapshot of an unfinished one, made permanent.
And the cost is not just that it is wrong. A codified model gets taught, measured, and enforced. People stop reasoning and start complying with assumptions no one has tested. The artefact that was meant to scale judgement quietly replaces it.
This is why the move that looks most like leadership – producing what was asked for – can be the one that does the damage. The harder move is to hold the sequence: to say the model is coming, and it will be real when it describes how the system actually decides – not how we hoped it would.
That is not refusing the board.
It is protecting the thing the board actually wants from arriving in a form that cannot survive contact with pressure.
When your organisation’s senior stakeholders ask for the operating model, the playbook, and the metrics framework, does your response defend the sequence – or does it produce the artefacts?
This question closes a chapter of The Architecture of Commercial Performance, where the thinking behind it is developed in full.
