This pattern is everywhere. In my experience, it is the single most common leadership failure—not a lack of capability, not a shortage of resources, but a misdiagnosis of what kind of problem you are actually facing. Get the diagnosis right and even mediocre execution can succeed. Get it wrong and brilliant execution makes things worse.
Technical vs. Adaptive Challenges: A Framework for Diagnosing the Real Problem
A few years ago, I worked with a professional services firm that was hemorrhaging talent. Their diagnosis was straightforward: compensation was not competitive. So they raised salaries, improved benefits, and offered retention bonuses. Twelve months later, attrition was worse. The firm had a classic adaptive challenge. But they diagnosed it as technical. They applied the right solution to the wrong problem, and it cost them millions.
The Fundamental Distinction
The distinction between technical and adaptive challenges comes from the work of Ronald Heifetz at Harvard, and I have built on it extensively in my own practice. The core idea is deceptively simple: some problems have known solutions, and some do not. Where the solution comes from determines how you lead.
Technical Challenges
The Situation: The problem is clear. The expertise exists. The solution is known.
What is needed: Skilled execution. Mobilizing the right expertise and deploying it competently.
The work: Think of a surgical procedure. Difficult, high-stakes, but the steps are known. The surgeon does not need to invent the procedure; they need to execute it well.
Example: A legal brief. A financial audit. A well-scoped consulting engagement.
Adaptive Challenges
The Situation: The problem is often poorly defined. The solution does not exist in any playbook. The situation requires people to change.
What is needed: Leadership of learning and change, not delivery of a solution. People must change their beliefs, habits, values, or how they work together.
The work: Think of an organization that needs to shift its culture. There is no technical fix. Part of the work is figuring out what the problem actually is.
Example: Organizational culture change. Digital transformation. Merging two firms with different operating philosophies.
The Four-Zone Model
In my own work, I have extended this into a four-zone model that adds two additional categories critical for modern leadership. Most significant challenges fall into one of these four zones, and the leadership approach required differs dramatically depending on which zone you are actually in.
Zone 1
Expert Delivery
The problem is understood, the solution is known, and what is needed is skilled execution. This is the comfort zone for most professionals. A legal brief. A financial audit. A well-scoped consulting engagement. Your job is to execute the known solution as well as possible.
Zone 2
Expert Response
The problem is understood but requires rapid adaptation of known expertise to a new context. A crisis that fits a known pattern but requires speed and precision. An experienced surgeon facing a complication they recognize from training. The expertise exists; you need to deploy it quickly and adapt it to the specific situation.
Zone 3
Adaptive Challenge
The problem is understood but the solution requires changes in behavior, identity, or values. Organizational culture change. Digital transformation. Merging two firms with different operating philosophies. No playbook exists. You are leading people through a process of learning and change, not delivering a predetermined solution.
Zone 4
The Fog Zone
Neither the problem nor the solution is clear. The situation is genuinely novel, information is unreliable, and the future is unknowable. Early-stage artificial intelligence disruption. A pandemic. Working in a post-conflict environment where the rules of the game have not been written yet. Your job is not to solve but to stabilize, experiment, and learn your way forward.
Why Misdiagnosis Is So Common
Leaders default to technical solutions for three reasons. First, technical solutions are comfortable. They have clear steps, measurable outcomes, and a defined timeline. Leaders know how to manage technical work. Second, technical solutions make you look decisive. "We are raising compensation" sounds like leadership. "We need to fundamentally rethink our culture" sounds uncertain. Third, and most importantly, adaptive work is painful. It requires people to give up something—a belief, a practice, a piece of their identity. Leaders who name adaptive challenges are often punished for making people uncomfortable.
The result is that organizations often apply expensive, expert technical solutions to problems that are fundamentally adaptive. The solution may be executed brilliantly. But it addresses the wrong problem, and the real issue festers and grows.
The Diagnostic Questions
When facing any significant challenge, work through these four questions before deciding on a response. Your answers will tell you which zone you are actually in and what kind of leadership the situation demands.
Do we know the solution?
If yes, this is technical or expert territory. Deploy expertise. Execute well. Do not overcomplicate.
Does the solution require people to change how they work, think, or relate?
If yes, this is adaptive. No amount of expert deployment will resolve it. You need to lead a process of learning, not deliver a solution.
Do we actually understand the problem?
If no—if the situation is genuinely novel, if information is unreliable, if the future is unknowable—you are in the fog zone. Stop trying to solve. Start stabilizing, experimenting, and learning your way forward.
Are we conflating urgency with clarity?
This is the most dangerous diagnostic error. Just because something is urgent does not mean it is clear. Urgency creates pressure to act, which creates pressure to treat the problem as technical. Resist this pressure.
Why This Matters for Women Leaders
Women leaders disproportionately face adaptive and fog-zone challenges—not by accident, but by design. The research is clear: women are more likely to be appointed to leadership positions in crisis (the "glass cliff" phenomenon). And crisis situations are almost never purely technical. They are adaptive or fog-zone challenges that require a different kind of leadership altogether.
This means women leaders need diagnostic discipline more than most. Not because they lack it, but because the situations they face demand it. The four-zone model provides a language and a logic for making the case that the comfortable, technical response is the wrong one—and for building support for the harder, slower, more uncomfortable adaptive work that the situation actually requires. When you have a framework, you have the standing to say: "I know this feels urgent and I know we want a technical fix, but the real problem is adaptive. Here is why, and here is what we need to do instead."
Common Questions About Technical vs. Adaptive Challenges
What is an adaptive challenge?
An adaptive challenge has a poorly defined problem, no playbook, and a solution that requires people to change. Examples: organizational culture change, digital transformation, merging two firms with different operating philosophies. There is no technical fix. Part of the work is figuring out what the problem actually is.
What is the difference between a technical problem and an adaptive challenge?
The core idea is deceptively simple: some problems have known solutions, and some do not. Where the solution comes from determines how you lead. With a technical problem the expertise exists and the solution is known — the work is skilled execution: a legal brief, a financial audit, a well-scoped consulting engagement. With an adaptive challenge the problem is often poorly defined and the solution does not exist in any playbook. People must change their beliefs, habits, values, or how they work together.
What is an example of an adaptive challenge?
Organizational culture change. Digital transformation. Merging two firms with different operating philosophies. In each, no playbook exists, and the work requires people to change behavior, identity, or values rather than execute a predetermined solution.
Why do organizations misdiagnose adaptive challenges as technical problems?
Leaders default to technical solutions for three reasons. First, technical solutions are comfortable: clear steps, measurable outcomes, a defined timeline. Second, technical solutions make you look decisive — "we are raising compensation" sounds like leadership; "we need to fundamentally rethink our culture" sounds uncertain. Third, and most importantly, adaptive work is painful. It requires people to give up something — a belief, a practice, a piece of their identity. Leaders who name adaptive challenges are often punished for making people uncomfortable.
Where does the technical vs adaptive framework come from?
The distinction comes from the work of Ronald Heifetz at Harvard, and I have built on it extensively in my own practice — including a four-zone model that extends Heifetz's original distinction with two additional categories: Expert Response (rapid adaptation of known expertise to a new context) and the Fog Zone (where neither the problem nor the solution is yet clear).
The Bottom Line
Diagnosis before action. Always. The ten minutes you spend figuring out what kind of problem you are actually facing will save you months of wasted effort solving the wrong one. And the courage to name an adaptive challenge when everyone around you wants a technical fix is one of the most valuable things a leader can do.
Get the diagnosis right, and even mediocre execution can succeed. Get it wrong, and no amount of expert deployment will fix it.