There is a standard shape to change management on a transformation programme. A comms plan. A stakeholder map with people sorted into quadrants. Training, delivered near the end. A resistance log.
All of it treats the organisation's own people as an audience — a group to be informed, persuaded and eventually trained. The unspoken theory is that the answer has been worked out elsewhere, by the programme, and change management is the discipline of getting everyone to accept it.
That theory costs you twice.
"If your change plan is mostly about telling people, you've already decided their knowledge isn't part of the answer."
— Paul Balaam, Rewired+PartnersThe knowledge is already in the building
The first cost is what you never learn.
The people doing a job every day know things no discovery workshop will surface — which exceptions actually matter, which policy is quietly ignored because it doesn't work, where the real bottleneck sits versus where the process map says it sits. That knowledge doesn't emerge from a stakeholder interview, because interviews ask people to summarise. It emerges when someone is in the room while a decision is being made and can say that won't work, and here's why.
On the member experience programme we led for a national union, the programme team deliberately mixed our consultants with the union's own staff champions and specialist partners. That wasn't a goodwill gesture. Unions aren't structurally built for complex technology change — but nobody understands a union's members better than the people who serve them. Handing the work to agencies would have produced something competent and wrong.
Resistance is usually information
The second cost is the resistance itself.
A great deal of what gets logged as resistance is actually expertise arriving too late. Someone objects at user acceptance testing because it's the first time anyone asked them, and what they're saying is not I don't like change — it's this doesn't handle the case that makes up a third of my week.
Involve them at design and the same information arrives as a requirement instead of an obstacle. The objection hasn't disappeared; it has moved to the point in the process where acting on it is cheap.
What this looks like in practice
- Named owners, not representatives. Each of the twelve member journeys we rebuilt had a named internal owner — someone accountable for that journey, not someone attending on behalf of a department.
- In the team, not consulted by it. There's a real difference between being on the team and being on the distribution list. Only one of them changes the design.
- Early enough to be inconvenient. If involving people doesn't slow anything down at the start, they've been brought in too late to affect it.
- Selected for knowledge, not enthusiasm. The most useful champion is often the person with the most detailed objection, not the most positive one.
The awkward part
This is harder than the standard approach, and it's worth being honest about why.
It means the programme cannot fully control the answer. It means design takes longer and involves more disagreement. It means someone's actual job has to be backfilled while they spend four months on a mission.
What you get in return is a design that survives contact with the work, and a group of people who own the outcome because they built it. Adoption stops being something you have to drive, because the people who would have been resisting are the people who made it.
You can pay for that knowledge at the start, in inconvenience, or at the end, in rework. It is the same knowledge either way.
