From Research to Readiness · Adaptive Leadership
From Research to Readiness: Ronald Heifetz
Not every problem can be fixed with expertise. The hardest ones require the organization itself to change, and that is a different kind of leadership.
Ronald Heifetz drew a distinction that reorganizes how leaders should think about their job: between technical problems, which can be solved with expertise and authority, and adaptive challenges, which require the people with the problem to change their own values, habits, and ways of working. Confusing the two is one of the most common and costly leadership mistakes.
Research Foundation
- Adaptive leadership
- Leadership and authority
- The Four A's of Organizational Readiness
- The Builders Build Framework
Key Takeaways
- Technical problems yield to expertise and authority; adaptive challenges require the people involved to change themselves.
- Leaders routinely treat adaptive challenges as technical, hand down a solution, and watch the problem return.
- This is an Adaptability condition, and Heifetz separates leadership, which mobilizes adaptation, from authority, which can only order a fix.
What Heifetz found
Heifetz distinguished technical problems, which can be solved by expertise and a decision, from adaptive challenges, which cannot, because they require the people with the problem to change their values, habits, or ways of working. In adaptive work, the leader's job is not to supply the answer but to hold people in productive discomfort so they do the changing. He also separated leadership from authority: authority can command a technical fix, but it cannot mandate adaptation.
Why it matters inside organizations
Leaders default to treating adaptive challenges as technical. They issue a solution, reorganize, or bring in an expert, and the problem returns because the people never actually changed. Most failed transformations are adaptive challenges handled as technical ones, solved on paper and unsolved in reality, because no order can make a group adopt a new way of working.
The failure is not that the problem was hard. It is that an adaptive challenge was handed an expert's answer, and the people never had to change.
The condition it affects
This is about adaptability: whether the organization can do the harder work of changing itself, rather than waiting for a fix to be handed down. Diagnosing a challenge as adaptive rather than technical is the first move, and the one leaders most often skip.
Through the Four A's
This lands on Adaptability, with Authority. Adaptability, because adaptive challenges require the organization to learn and change. Authority, because Heifetz's central warning is that authority and leadership are not the same: you can use authority to order a technical fix, but adaptive work has to be mobilized, not commanded.
Evidence matrix
| Claim | Research | Field evidence | Four A's |
|---|---|---|---|
| Technical and adaptive challenges differ | Heifetz (1994) | Expertise cannot solve adaptive work | Adaptability |
| Adaptive work requires the group to change | Heifetz (1994) | The answer is not delivered from above | Adaptability |
| Leadership is distinct from authority | Heifetz (1994) | Orders cannot mandate adaptation | Authority |
Executive reflection questions
- Is the problem in front of you technical or adaptive, and are you sure?
- Where have you handed down a solution to a challenge that required people to change?
- Are you using authority to order a fix that only adaptation can produce?
- Whose work is it to change, and have you given it back to them?
Builder actions
Before solving a problem, diagnose whether it is technical or adaptive. If expertise and a decision can fix it, act. If it requires people to change their own habits, values, or ways of working, resist the urge to hand down an answer, because the answer will not stick. In adaptive work, your job is to keep people in the productive discomfort of doing the change themselves, and to give the work back to those who must own it. Most failed transformations are adaptive challenges that a leader tried to solve technically.