A technical challenge is a problem that can be solved with existing expertise: the problem is clear, the solution is known, and an authority can implement it. An adaptive challenge is one where the problem itself is unclear or contested and the solution requires the people involved to learn, change their behavior, or give something up.
The distinction comes from Ronald Heifetz’s work at the Harvard Kennedy School and sits at the center of adaptive leadership. As a Harvard Medical School overview puts it, technical problems can be handed to experts, while adaptive ones must be owned by the stakeholders, because the obstacles are values, loyalties, and relationships. In practice, one of the most common leadership failures is treating an adaptive challenge as if it were technical.
The difference at a glance
| Question | Technical challenge | Adaptive challenge |
|---|---|---|
| Is the problem clearly defined? | Yes | No, or people disagree about what it is |
| Is the solution known? | Yes, by someone with the right expertise | No; it has to be discovered |
| Who does the work? | The expert or authority | The people with the problem |
| What has to change? | A process, system, or tool | Beliefs, habits, priorities, or relationships |
| How long does it take? | Often fast once resourced | Longer; involves learning and setbacks |
| Typical example | Fixing a payroll error, upgrading a server | Getting two teams to trust each other’s commitments |
Examples of technical vs adaptive challenges
Most real situations contain both kinds of work. The skill is separating them.
- Launching a new CRM. Configuring the software and migrating data is technical. Getting salespeople to log activity honestly, when they have always kept their pipeline in their heads, is adaptive.
- Missed project deadlines. Adding a scheduling tool is technical. Getting a team to stop saying yes to dates it does not believe in is adaptive.
- A merger. Combining systems and policies is technical. Building a shared way of working between two cultures is adaptive.
- Low employee engagement. Running a survey is technical. Changing how managers listen and follow through on what they hear is adaptive.
- A new strategy. Writing the plan is technical. Getting leaders to stop funding the projects the strategy deprioritized is adaptive.
How to diagnose which one you are facing
Ask these questions before you assign the work:
- Has this problem been solved before, here or elsewhere, by applying known methods? If yes, it is likely technical.
- Do the people involved agree on what the problem is? Disagreement about the definition is a strong adaptive signal.
- Will solving it require someone to lose something? Status, control, a favored project, or a familiar way of working. Loss is the signature of adaptive work.
- Have previous fixes come back? A problem that keeps returning after “solutions” is usually an adaptive challenge that was treated as technical.
- Does progress depend on people keeping new commitments to each other? If so, no expert can install the answer.
How to lead each kind of challenge
For technical challenges, lead with clarity. Find the right expertise, define the outcome, set the deadline, and remove obstacles. Directive leadership is appropriate here, and over-consulting wastes time.
For adaptive challenges, lead with questions. Frame the issue, bring the people who own it into the work, keep the discomfort in a productive range, and make the tradeoffs visible. Then, critically, turn the conversation into specific commitments. In DorWay’s view, an organization is a Network of Agreements™, and an adaptive challenge is resolved only when people make new agreements with each other and keep them, or renegotiate them openly. A team that “aligns” in a workshop but never agrees on who does what by when has not done the adaptive work yet.
Common mistakes leaders make
- Applying a technical fix to an adaptive problem. A new policy, tool, or reorganization announced from the top, when the real issue is how people treat their commitments.
- Treating a technical problem as adaptive. Running long listening sessions on something an expert could fix in a day.
- Doing the adaptive work for the team. If the leader solves it, the team learns nothing and the pattern returns.
- Avoiding the losses. People sense what they stand to lose. Pretending there is no loss erodes trust and, with it, integrity in leadership.
If you want to reflect on which mode you default to under pressure, the free PACT™ Leadership Assessment looks at how you lead when accountability, agreements, and trust are on the line.
FAQ
What is the difference between technical and adaptive challenges?
Technical challenges have known solutions that experts can implement. Adaptive challenges have no ready answer and require the people involved to change their own beliefs, habits, or relationships for progress to happen.
Who came up with technical and adaptive challenges?
Ronald Heifetz of the Harvard Kennedy School introduced the distinction in his work on adaptive leadership, later developed further with Marty Linsky and Alexander Grashow.
What is an example of an adaptive challenge at work?
A leadership team that repeatedly agrees on priorities and then keeps funding its own pet projects faces an adaptive challenge. No tool fixes it; the leaders have to change how they make and keep commitments to each other.
Can a problem be both technical and adaptive?
Yes, and most are. Separate the parts: hand the technical work to experts, and engage the people who own the adaptive part directly.
