Building Behavioural Capability
What remains when the expert leaves.
Organisations buy capability roughly the way people buy exercise bikes. The purchase itself feels like the accomplishment. There is a moment of genuine intent, a handing over of money, a sense that a thing has been solved. Then the beautiful object stands in the corner, holding coats, quietly reproaching everyone who walks past. The toolkit launches. The shelf receives it. And a year later someone asks, reasonably, what happened to all that capability they paid for.
What happened is that capability was never the toolkit. Capability is what people do differently in real decisions when no expert is in the room. It is four things at once: judgement, tools, rhythm, and permission. A purchase supplies one of them, the tools, and leaves the other three to fend for themselves.
Teach, embed, retain
Capability building fails most often because everything gets treated as training. The work splits three ways, and each way has its own mechanics.
- Teach what needs judgement
- Defining behaviours, reading situations, choosing which shifts matter. Judgement does not grow through slides. It grows through live decisions with feedback, made out loud, on real problems.
- Embed what needs consistency
- Checks, prompts, templates and questions, placed inside meetings that already happen. The tool has to live where the decision lives, or it does not live at all.
- Retain what still needs expert hands
- The novel, the high-stakes, the politically loaded call. Full independence is the wrong target. A team that knows exactly when to pick up the phone is the right one.
Most programmes do only the first, and do it as a workshop rather than as practised decisions. Then they wonder where the capability went. It went nowhere, because judgement taught by slide is a fact about judgement, not judgement itself, and facts about swimming keep no one afloat.
A toolkit needs a ritual
A tool becomes capability at the exact moment it changes a real decision, and real decisions get made in meetings. So the meetings are where the tools have to live. Without a recurring moment of use, the finest toolkit ever built is shelfware by the end of the quarter, not through anyone's fault, but because nothing in the week ever calls for it.
The everyday version is a kitchen. A recipe book on the shelf feeds nobody, however good the recipes. Tuesday-night pasta feeds a family every week, and the difference between them was never the quality of the book. It was the slot in the week that the cooking already lived in. Capability is the pasta, not the book.
Design your own exit
There is a quiet conflict of interest at the centre of capability work, and the honest thing is to name it rather than pretend it is not there. Dependency pays the consultant. Independence serves the client. A practice that never hands anything over is renting out its judgement indefinitely, and rented judgement never compounds into something the client owns.
A driving instructor's success is the empty passenger seat, plus a learner who has been taught that motorway fog is a day to be careful rather than a day to be confident. The lessons ending is not the failure. The lessons ending well is the entire point.
Get the full guide
The complete guide, with worked examples, the running order for a team session, and all the detail the excerpt leaves out, is available as a free PDF.
Free. No spam. One email with your download link.