Decision quality is uneven across the team, so you build the enablement.
A programme. A playbook. A certification. A platform that captures how the best people work. The intent is right: take what your strongest people do and make it everyone’s.
And on the surface, it works. Behaviour gets more consistent, the language sharpens, the reviews look better. But whether anything real happened depends entirely on one thing – whether the judgement underneath had actually formed before you tried to scale it.
Because enablement cannot create judgement. It can only extend judgement that already exists. Roll it out after the reasoning has formed, and it carries that reasoning further – to people who were not in the room when it formed, into situations the originators never saw. Roll it out before, and there is nothing underneath to extend. So it scales the only thing available instead: the surface. The visible moves, the language, the steps – copied without the reasoning that made them the right moves in the first place.
And that is the distinction the whole thing turns on. Judgement is reasoning – knowing why this, here, now, and being able to decide well when the situation is one no playbook anticipated. Imitation is reproducing the visible behaviour of someone who had that reasoning.
They look the same on a good day. They come apart completely on a hard one.
Watch the tell. A system running on real judgement, hitting a novel case, decides – the reasoning extends to the new situation. A system running on imitation, hitting the same case, escalates, because there is no script for this one and copying cannot improvise.
Activity goes up. Capability does not.
The system gets busier, more certified, more enabled – and quietly less able to handle the thing it was not drilled on.
This is why timing decides whether enablement builds or substitutes. The identical programme does opposite things depending on what is underneath it. After judgement travels, it protects and extends real reasoning. Before, it papers over the gap where reasoning should be – and worse, it hides the gap, because the surface looks so much better that no one goes looking for the judgement that never formed.
There is a clean test for which one you have built. Imagine removing the programme tomorrow. If decision quality collapses straight away, the programme was holding the system up – capability never formed, and the enablement was the judgement. If its absence would cause only slow drift over months, real capability is there, and the programme was protecting it, not producing it.
Immediate regression means substitution. Gradual drift means it was real.
So before scaling what your best people do, the question is not “how do we capture and roll this out?” It is “has the reasoning underneath this actually formed and travelled – or am I about to scale the behaviour and lose the judgement that produced it?” Build enablement on judgement that holds, and you make good reasoning durable.
Build it on judgement that has not formed, and you make the absence of reasoning invisible. In your organisation, does enablement reinforce decisions people are already making confidently – or does it substitute for the judgement that has not yet stabilised?
This question closes a chapter of The Architecture of Commercial Performance, where the thinking behind it is developed in full.
