Playbook
Leading a Change Programme
Change lands person by person or it does not land at all. Diagnose the culture underneath, respect the physics of unfreeze and refreeze, run the programme in the right order, and check where each individual has actually got stuck.
I once introduced a new system into my firm with a memo, a training morning and a great deal of optimism. Six months later the old spreadsheets were back, living quietly in personal drives like weeds under a patio. Nobody had refused the change. It simply had not taken. That experience taught me the lesson this playbook is built on: an organisation changes when the people in it do, and people change slowly, for their own reasons, in their own order. Announcements achieve very little on their own. So the sequence starts below the surface with Schein, because the culture you cannot see is the thing your programme will actually collide with. Lewin then gives you the basic physics: destabilise, move, anchor, and never skip the anchoring. Kotter provides the operating manual for the programme itself, urgency through to consolidation. ADKAR brings it down to the only level where change genuinely happens, one person at a time. Four frameworks feels like a lot. In my defence, the graveyard of change programmes is full of efforts that used none, and reversal is far more expensive than diagnosis.
Org, people & execution
Schein's Three Levels of Culture
For understanding a culture by working down from what you can see, through what people say they believe, to the assumptions that actually drive behaviour. Leave it alone when you need to compare many organisations in numbers; use a survey instrument. Instead The Competing Values Framework, a survey instrument built for comparing many organisations in numbers.
Before designing any programme, find out what the organisation actually believes, as opposed to what the posters in reception claim. Schein's three levels give you the method: inventory the visible artefacts, record the espoused values, then hunt the contradictions between them, because the contradictions point to the underlying assumptions your change will really be negotiating with. My spreadsheet counter-revolution was a contradiction of exactly this kind. The firm espoused efficiency; the assumption underneath was that your own numbers were the only numbers you could trust.
Watch forDo not stop at the artefact level; a diagnosis that lists the visible symptoms and calls them culture will design a change that bounces straight off.
Org, people & execution
Lewin's Three-Step Model
For the simplest picture of change there is: loosen the current way, move, then settle the new way so it does not snap back. Leave it alone when your organisation must change continuously; settling is the wrong ambition. Instead Kaizen and PDCA, built for change that never settles; refreezing is the wrong ambition.
Lewin supplies the physics every later model descends from: unfreeze the current pattern, move to the new one, refreeze so the group does not snap back. Before planning anything, weigh the force field. List what pushes towards the change and what holds the old pattern in place, and be honest about the strongest restraining force, because if your design leaves it untouched, your plan is a polite request. Most failed changes were never properly unfrozen, and the ones that reverse, like my spreadsheets, were never refrozen.
Watch forThe trap is declaring victory at go-live; the refreeze is the part everyone is too tired to do, and it decides whether the change holds.
Org, people & execution
Kotter's 8-Step Change Model
For leading a major change in the order the research says works, from urgency and a coalition to anchoring it in the culture. Leave it alone when the change is small and contained; a plan and some communication will do. Instead PDCA, if you want a shape for it; a plan and some communication will do for a change this size.
For a programme of real scale, Kotter gives you the operating sequence: urgency, coalition, vision, communication, empowerment, short-term wins, consolidation, anchoring. Two uses. As a plan it stops you skipping the unglamorous early steps, and as a diagnostic it tells you where a stalling programme actually broke, since a communication problem at step four is usually a vision problem from step three wearing a disguise. Schedule the short-term wins deliberately. Eighteen months is a long time to run on faith.
Watch forProgress at any step is capped by the weakest step before it, so resist the executive urge to start at step four because the first three feel soft.
Org, people & execution
ADKAR Model
For understanding why a change has not stuck with a particular person: awareness, desire, knowledge, ability, reinforcement, in that order, and which one is missing. Leave it alone when the block is structural or political; incentives and turf do not yield to individual treatment. Instead Stakeholder Mapping, because the block is in the incentives and the turf, not in the individuals.
Programmes move organisations on paper; ADKAR is where you check the change is landing in actual human beings. Five outcomes in sequence for each person: awareness, desire, knowledge, ability, reinforcement. Find each group's weakest element and treat that barrier first, because effort spent further down the line is wasted until it clears. Sending a third all-staff email to people whose problem is desire achieves nothing except a quieter inbox for you and a fuller one for them.
Watch forExpect different groups to stall at different points, front-line desire problems alongside management reinforcement problems, and do not prescribe one group's cure for everyone.
In the end
You should finish with a cultural diagnosis that names what the change will really collide with, a force field you have honestly weighed, a staged programme with scheduled wins, and a person-level view of where adoption is sticking. The honest caveat is time. Real change is slow because trust is slow, and none of these frameworks lets you skip that part. What they prevent is the expensive version of the lesson, where you discover the underlying assumptions six months after go-live, in the shape of old spreadsheets quietly coming back.