← Leadership research

Adaptive Leadership

Ronald Heifetz and Marty Linsky · Leadership on the Line (2002)

One diagnostic question sits underneath the whole framework: does this problem need a better process, or does it need people to behave differently? Getting that wrong is the most expensive mistake in management.

Technical and adaptive

Heifetz splits problems in two.

A technical problem is one where the problem is understood and a solution exists. Someone with the right expertise, authority or process can fix it. The organization already knows how. Difficult is not the same as adaptive: a very hard engineering problem is still technical.

An adaptive challenge has no known solution. Meeting it requires people to change something about what they believe, value, prioritize or do. No expert can hand it over finished, because the work is in the people who have the problem.

Which has an uncomfortable consequence. Technical problems can be solved by authority. Adaptive challenges cannot, and a leader trying to solve one by announcement is not leading the work, they are absorbing it.

The technical fix trap

The common failure is applying a technical solution to an adaptive challenge.

Collaboration is poor, so you buy a tool. Quality is slipping, so you add a process step. Something cultural is wrong, so there is a reorganization, or a training day, or a new set of values on the wall.

These are popular for an understandable reason: they look decisive and nobody has to change. They also tend not to work, and the giveaway is recurrence. A problem that returns a year later in a new costume was probably never technical.

People do not resist change, they resist loss

This is Heifetz's most useful reframe.

Resistance is usually read as obstruction, inertia or bad attitude. His argument is that it is almost always rational, and it is information. Someone pushing back is protecting something specific: competence they spent years building, status, a relationship, a routine, a view of themselves as the person who knows how this works.

So the question is not how to overcome resistance. It is what this person would be giving up, and whether you have ever said out loud that you know it is a loss.

Get on the balcony

Heifetz's image is a dance floor. In the middle of it you can see the people immediately around you and very little else. To see the patterns you have to go up to the balcony and look down.

The practical version is the discipline of stepping out of the action repeatedly, not once at an offsite, to ask what is actually happening here rather than what is happening to me today. The move is deliberately two-way: you have to get back on the dance floor, because a leader who stays on the balcony is just commentating.

Regulate the heat

Adaptive work needs some discomfort. With none of it nothing changes, because change is harder than carrying on.

Too much and people shut down, fight, or look for someone to blame, which is frequently whoever raised the issue. Heifetz describes the leader's job as holding a productive zone of disequilibrium: enough pressure that the work happens, not so much that the system breaks.

That is also why a leader's steadiness is not merely a personality trait. It is one of the controls. People read the temperature off you.

The part most leadership books leave out

Leadership on the Line is named carefully. Heifetz and Linsky are explicit that leading adaptive change is dangerous, and not metaphorically.

Asking people to face a loss makes you the source of the discomfort. The cheapest way for a system to relieve the pressure is to remove the person applying it, which is why people who raise real problems are so often marginalized, promoted sideways, or exhausted into leaving. The book treats surviving the work as part of the work.

It is unusually honest for the genre, and it is the reason the book is still read twenty years on.

Where it comes from, and how far it stretches

Ronald Heifetz teaches at the Harvard Kennedy School and trained originally as a physician and psychiatrist, which shows: the whole framework is built as a diagnosis before a treatment. Marty Linsky is his long-time collaborator. The main works are Leadership Without Easy Answers (1994), Leadership on the Line (2002) and The Practice of Adaptive Leadership (2009), the last with Alexander Grashow.

The fair criticisms. It is a practitioner framework, developed from case work and teaching rather than controlled study. The technical and adaptive line is much cleaner in hindsight than in the middle of a week. And most real problems are a mixture, so the honest use of the framework is not labelling the whole thing but asking which part of it is which, and refusing to let the technical part stand in for the rest.

Reading on

• Leadership on the Line (2002) — the most readable, and the one about staying in one piece.
• Leadership Without Easy Answers (1994) — the original argument, denser.
• The Practice of Adaptive Leadership (2009) — the toolkit version.

The questions this produces

The diagnosis only counts if you run it on something currently on your desk. These are five of the questions LeaderWise draws from this framework.

Technical vs. adaptive challenges

Does your recurring problem need a better process, or different behavior?

The technical fix trap

Which people problem are you treating as a process problem?

Understanding resistance

What are people protecting when they push back on your change?

Naming the loss

In the change you're leading, did you say out loud what people lose?

Getting on the balcony

Step back from this week. What pattern would you see that you can't from inside it?