You decided a new way of working — a new commercial playbook, a new operating standard, a new way a certain kind of work should be done. The material is good: tight, well-made, signed off. It went out through the roadshow, the e-learning, the train-the-trainer, the team meetings where leaders walked people through it. Three months on, you sit in on a real meeting and it sounds exactly like it did before.
That's not a delivery failure — it's a category error. The rollout was built as a comms problem: tell people, explain, make sure everyone understands, as if understanding were the same as doing. But a playbook is information, and information has never been behaviour change. Rolling out a transformation means changing how people work, and that's something you design for, not announce. This article is about doing that when the rollout is large and the behaviour is complex.
Some new behaviours can be taught. A playbook mostly can't.
New ways of working sit on a spectrum. Some are codifiable — there's a clear right move and you can teach it. Others are situation-dependent: what "right" looks like shifts with who you're in front of and what's on the table. A needs analysis, a hard customer conversation, an account plan for a major client — you can describe the principles, but you can't explain into existence the judgement that knows which one to reach for when.
Most strategic playbooks live at that complex end, and that's the whole reason a broadcast can't work. When you can't make the right move obvious, you design for practice, reflection, and discussion instead: people try the behaviour on real work, notice what happened, and talk it through with others who met the same reality.
Pick what's new and what actually matters
A playbook is big, and the instinct is to roll out all of it. Resist that. Before you design anything, two questions decide what earns real support: what's genuinely new here, and what genuinely matters? Skip them and the target group and chance decide for you — something comes first and gets more attention regardless, just not on purpose.
So prioritise, then design around the few behaviours that carry the change. Finding what those are — and what's actually blocking them — is its own discipline; designing from the goal and the blockers walks through it. The point here is narrower: a transformation is too big to support all at once, so choose what to support on purpose.
Run it as a sequence of focus periods, not one launch
For a whole playbook, one push isn't enough. You run a sequence of focus periods, each aimed at a single cluster of behaviours — eight periods for eight clusters, say, six weeks each, in an order that builds. One behaviour cluster gets the spotlight at a time, long enough to actually practise, before the next one starts.
That structure is the difference between a transformation people remember hearing about and one they can feel changing their week. The anatomy of a single period — pre-work, session, reflection, and the loop back — is the same shape we walk through in the AI-adoption playbook; here you're simply sequencing several of them across the playbook.
Make each session a gift of time, not lecture time
The default makes the session about delivery: the facilitator explains, everyone listens, then goes off to try. Flip it. Treat the session as a gift of time — ten minutes of framing, then protected time to do the real work that would otherwise have slipped out of a busy week.
That works because of what people bring and leave with: real work in, a real artefact out. The pre-work is to pick an actual task — a customer you'll prep for a meeting that's genuinely booked just after — so the session produces a finished plan and the plan gets tested for real days later. Each period then closes with a peer group, where people compare what actually happened and pull out the judgement the playbook couldn't write down. It stops being a meeting about the work and becomes the work, done together.
Protect the time — the everyday will fight back
The hardest part isn't the design. It's that the old way is held in place by things a rollout doesn't touch: what managers measure, what gets rewarded, what wins when the week gets busy. L&D can't change those — but as a strategic partner you can name them to leadership, so nobody pretends a programme fixed an incentive it can't reach.
What you can do inside the programme is buy the new behaviour enough protected time to take root before the old metrics snap back. That's the manager's job in a rollout, running in parallel with the participants': loop in ahead of each period, notice when their person does the work, and ask about it in the next 1:1. One commercial-playbook rollout built this way saw 80–90% completion per focus period — because nothing rode on anyone remembering.
You wrote the strategy. The real question is whether you designed for people to actually work that way — because that's the part a deck can never carry. Transformation isn't a comms problem; it's a behaviour-change one. Design for it to happen: prioritise what matters, protect the time, and let people practise the new way on real work until it's simply how the work gets done.