Few leadership briefs are purely technical or purely adaptive. How to split one, which frame each half needs, and what you can honestly promise.
A client tells you their transformation has stalled. Managers nod in workshops and nothing moves. They want a leadership programme, they want it to be twelve weeks, and they want to know what it will change.
Somewhere in the next few days you will decide whether that programme is built on Kotter's eight steps or on adaptive leadership. Most designers make that call while writing the proposal, which is the worst possible moment: early enough that you have no evidence, late enough that the price is already in the client's head.
The two frames are not two styles of the same programme. They rest on incompatible claims about what is in the way, and each one commits you to a different unit of intervention, a different set of modules, a different measurement plan and — this is the part that gets people into trouble — a different set of promises you are allowed to make. Picking the wrong one produces a well-run programme that changes nothing, and an evaluation that looks fine until someone asks what moved.
This is the narrow version of a wider question. If you are still deciding between six frameworks rather than two, start with the symptom-to-framework decision guide and come back here once the shortlist is down to these two.
Kotter's claim is that you know where you are going and the process is failing.
In "Leading Change: Why Transformation Efforts Fail" (Harvard Business Review, March–April 1995), Kotter sets out eight errors: not establishing a great enough sense of urgency; not creating a powerful enough guiding coalition; lacking a vision; undercommunicating the vision by a factor of ten; not removing obstacles to the new vision; not systematically planning for and creating short-term wins; declaring victory too soon; and not anchoring changes in the corporation's culture.
Read that list as a designer and notice what it assumes. Every one of those errors is an error of execution toward a known destination. None of them is "we disagreed about where to go." Kotter's model is a sequencing discipline, and he is explicit about what happens when you rush it: "Skipping steps creates only the illusion of speed and never produces a satisfying result".
Heifetz's claim is that the destination itself is the problem.
Heifetz and Laurie's distinction is between problems that yield to expertise and problems that do not. "Adaptive work is required when our deeply held beliefs are challenged, when the values that made us successful become less relevant, and when legitimate yet competing perspectives emerge" ("The Work of Leadership," Harvard Business Review, January–February 1997; quoted here from HBR reprint R0111K, December 2001). And the consequence for anyone designing an intervention: "Solutions to adaptive challenges reside not in the executive suite but in the collective intelligence of employees at all levels."
Heifetz names the failure mode directly in his own teaching material: "We treat adaptive challenges as technical problems. We do this for both political and personal reasons." The political and personal reasons matter to us, because a training request is one of the most respectable ways an organisation has of doing exactly that. Commissioning a programme is a way of locating the problem in a population of managers, which is more comfortable than locating it in a decision nobody wants to revisit.
One question, asked of the client, in the room:
If this programme works perfectly, who has to give something up?
If the honest answer is "nobody — people just need to be better at this," you are looking at execution, and Kotter is the useful frame. If the answer names somebody — a function that loses budget, a leader who loses a veto, a group that loses status — that loss is the actual obstacle, and no amount of skill-building removes it.
Two follow-ups that sharpen it:
Get these answers in the client's own words, not your paraphrase — that is what the diagnostic conversation is for.
Here is the thing the comparison articles never get to. Almost no real brief is purely one or the other. The stalled transformation in the opening paragraph is typically three things at once:
If you pick one frame for the whole engagement, you will either build a well-sequenced programme that runs straight into the knot, or a searching, uncomfortable programme that fails to deliver the ordinary skills the client also genuinely needs.
So split the brief instead of choosing between frames.
The piles then take different designs, and mixing the designs is the error, not mixing the frames.
| Technical component | Adaptive component | |
|---|---|---|
| Frame | Kotter's eight errors, run as a diagnostic checklist against the client's own programme | Heifetz and Laurie's adaptive work |
| Unit of intervention | The guiding coalition, plus individual managers on specific skills | The group that holds the competing perspectives — with the people who would lose something in the room |
| Modules look like | Urgency evidence-building; coalition composition; a communication cadence sized against the factor-of-ten problem; short-term wins planned rather than hoped for | Case-in-point work on the organisation's own live problem; structured surfacing of what each party would lose; sessions that hand the problem back rather than resolving it |
| Facilitator's job | Teach, sequence, hold the standard | Keep the question open and tolerable. Heifetz and Laurie: "Because a leader must strike a delicate balance between having people feel the need to change and having them feel overwhelmed by change, leadership is a razor's edge." |
| Measure at Level 3 | Yes, and cleanly — the behaviour is specified, so observe it | No. Measure whether the trade-off was named, by whom, and what was decided as a result |
| You may promise | Specific behaviours, on a date | A named trade-off, a decision, and who owns it |
| You may not promise | That it will hold. Kotter: cultural embedding "can take five to ten years" | Observable behaviour change inside the engagement |
The bottom two rows are the ones that cost money to honour, and they are the reason this piece exists. A proposal that promises measurable behaviour change from the adaptive half of a programme is promising something the underlying theory says is not available on that timescale. The only verified duration either author gives is illustrative rather than reassuring: Heifetz and Laurie report that at British Airways the shift from an internal focus to a customer focus "took place over four or five years", and Kotter observes that "renewal efforts take not months but years".
You can still win the work. You win it by being the person who said this at proposal stage rather than the person who discovers it at the review.
Do the technical work first, and say why.
Not because it matters more, but because the adaptive conversation requires people to say costly things in front of each other, and a group that has just succeeded at something ordinary together is in better condition to do that than a group that has not. There is also a plainer reason: the technical pile produces the short-term wins Kotter names as a distinct error to skip, and those wins buy you the standing to open the harder conversation.
One caution about the sequencing that does not go in the proposal but should be in your own notes. Kotter's threshold for urgency is specific — he writes that the transformation usually gets going when "about 75% of a company's management is honestly convinced that business as usual is totally unacceptable". If you are nowhere near that, the technical component will not hold either, and what you are actually being asked to do is manufacture urgency in a twelve-week programme. That is a different job, and it is worth naming as one.
Kotter applied to a contested destination. The programme is well run. The coalition is assembled, the cadence is right, the short-term wins are real. And the thing does not move, because two of the people in the coalition would describe success differently and the programme never created a place to discover that. This is the most saleable wrong answer in leadership development: it looks rigorous, it has a clear structure, it fits a twelve-week grid, and Kotter's own model does not claim to resolve disagreement about where to go.
Adaptive framing applied to an ordinary skills gap. The mirror error, and the one consultants who like the adaptive literature make. A group of managers who genuinely do not know how to run a difficult conversation are put through case-in-point work about what they would have to give up, and emerge thoughtful, uncomfortable and no more capable. Heifetz and Laurie's own framing is about balance, not about maximum discomfort.
Say this to the client before they work it out themselves.
Neither of these is an experimental result. Kotter's base is stated in the article: companies he has watched — "Well over 50% of the companies I have watched fail in this first phase". Heifetz and Laurie's is a set of cases and a conceptual distinction. Both are practitioner theory from close observation by people with a great deal of exposure — which is a real kind of evidence and not the same kind as a controlled study.
That is not a reason to avoid them. It is a reason to describe them accurately in a design document, and to be careful about which claims you attach a number to. A framework is a hypothesis about cause. It earns its place by being the one that best explains what you found in the diagnosis, not by being well known.
Try it on a live brief. The Diagnostic Conversation Coach is free, needs no signup, and runs this split against a gap you describe in your own words — including the give-something-up test, the three piles, and what each one commits you to measuring. If it does not sharpen the way you run a discovery call, nothing else here will interest you.
Working through a longer shortlist of frameworks? The symptom-to-framework decision guide covers six of them, including the two here.