A template is a document. A kit is a programme.
Most change teams start from templates. A stakeholder map, a communications plan, a readiness survey, a sponsor briefing. Each is a reasonable document, and each arrives empty. The work of deciding what goes in it, when it goes out, who sends it and how anyone would know it landed is left to whoever is holding the pen that week.
That is where programmes quietly diverge. Two teams given the same template produce two different programmes, and neither can tell whether the difference matters.
What a template leaves out
A blank template cannot say when. It cannot say who the sender should be, who the audience is, or what should have happened before this step and what must happen after it. It cannot say what evidence would show the step was done. Those are the decisions that carry a programme, and they are the ones a template hands back to you.
The cost is rarely visible on the day. It shows up three months in, when a sponsor briefing was never sent because nobody owned the send, or when a manager email went out before the workshop it was meant to follow.
What a kit carries instead
A kit is a set of artifacts that already know their place. The twelve emails in one capability pack run from twenty five days before the workshop to twenty days after it. Each states who it is from, who it goes to, when it sends and what it attaches. The facilitator slides name the platform activity they belong to. Nothing needs to be invented to run the step, only filled in from the programme record.
That is the difference between a document and a programme. The document describes what could be done. The kit sequences what will be done, and in doing so makes it possible to see what was skipped.
A step with no send point is a step with no owner.
Why this belongs under strategy
It would be easy to file this as a production detail. It is not. SA-1 asks whether the value hypothesis can be tested, and SA-4 asks who holds the authority to act on what the evidence shows. Neither is answerable if the steps that generate the evidence were optional, unowned or undated.
The practical test is short. Pick any step in your current plan and ask four things: who sends it, to whom, when, and how will you know it happened. If the answers live in one person's head, you have a template. If they live in the artifact, you have a kit.
The absorption ceiling nobody scores
Concurrent initiatives draw on the same finite capacity, and no single programme can see the total draw. The ceiling is real, it is measurable, and almost nobody measures it.
Shadow workflows are quietly holding your adoption numbers up
Go-live does not eliminate the parallel process. It drives it underground, where it keeps the numbers looking healthy while the transformation quietly fails to land.
Nobody can prove it worked, and that was decided at the start
The inability to demonstrate return is not a reporting failure discovered at the end. It is a design decision taken in the first ninety days, when the value case was written in a form that could never be tested.
Start with the free diagnostic
Ten questions, an indicative readiness band, and one prescribed next step. Returned on screen, no call required.
See what it measures