Most of the problems sitting on your desk right now don’t need a better solution. They need a different kind of work entirely.

Ronald Heifetz, the Harvard Kennedy School professor who coined the term “adaptive leadership,” draws a distinction that changed how I think about every challenge I face as a manager. Some problems are technical: the answer exists, someone with the right expertise can implement it, and the problem goes away. A broken deployment pipeline is technical. A misconfigured access policy is technical. A missing SOP is technical. You diagnose, you fix, you move on.

Then there are adaptive challenges. These are the ones where the problem itself is unclear, where the people involved are part of the problem, and where progress requires changes in values, habits, or identity. A team that won’t surface disagreements in meetings isn’t missing a process. A senior engineer who undermines every new hire isn’t a performance management checkbox. A department that resists every workflow change despite clear evidence the old way is failing doesn’t need a better change management plan.

Heifetz and his collaborators Marty Linsky and Alexander Grashow published The Practice of Adaptive Leadership in 2009. Seventeen years later, the framework has only become more relevant. DDI’s 2025 Global Leadership Forecast surveyed more than 13,000 leaders worldwide and found that only 13% of HR leaders believe their organization’s leaders can anticipate and react to change effectively. That number has declined by nearly half over five years. Leaders are less prepared for adaptive work than they were in 2020, despite living through a period that demanded more of it than any other in recent corporate memory.

Technical Fixes for Adaptive Problems

Applying technical solutions to adaptive challenges is the single most common leadership failure pattern. McKinsey’s research on organizational transformation found that roughly 70% of change initiatives fail. The primary barrier, cited by 72% of organizations with failed transformations, is employee resistance and management behavior. Not strategy. Not resources. People.

I watched this pattern repeat across every management role I held. A team misses a deadline, so the manager adds a status meeting. The next deadline still slips, so the manager adds a tracking spreadsheet. After the third miss, the manager mandates daily standups and wonders why morale has cratered while delivery hasn’t improved.

Every one of those interventions was technical. Each one assumed the problem was visibility or process. But the actual problem was something harder: the team didn’t trust the manager enough to flag risks early. Or two subteams carried an unresolved conflict from a botched project six months ago. Or the senior developer had quietly decided the project was doomed and was protecting her time for the next thing.

No amount of standups fixes a trust deficit. No spreadsheet resolves an unspoken conflict. The manager who keeps reaching for technical solutions is doing the equivalent of turning up the volume on a radio that’s tuned to the wrong station.

The Diagnostic Question

Heifetz offers a simple diagnostic. When you face a problem, ask: can someone with the right expertise solve this? If yes, it’s technical. Find that person (or be that person) and execute. If the answer is “the people involved need to change something about how they work, what they value, or how they relate to each other,” you’re looking at an adaptive challenge.

Most management problems land somewhere in the middle. Heifetz calls these “problems with technical and adaptive components.” A system migration is technical; getting three departments to agree on shared data standards requires adaptive work. Rolling out a new performance review process is technical; shifting a culture that avoids honest feedback requires people to change their relationship with discomfort.

The mistake isn’t failing to recognize pure adaptive challenges (those are rare). It’s treating the mixed problems as purely technical and wondering why the technical fix only works for about six weeks before the old patterns reassert themselves.

During an infrastructure consolidation in 2012, I inherited a technical problem with an adaptive core. Four separate ops teams needed to merge their monitoring stacks into one platform. The technical work was straightforward: evaluate tools, pick one, migrate. Three months, by my estimate.

Six months later, we had barely started. Each team treated their monitoring setup as an identity marker. The NOC team had built custom dashboards they considered a competitive advantage internally. The systems team had automated their alerting in ways they were proud of. Asking them to adopt a shared platform felt, to them, like being told their professional judgment didn’t matter.

I was solving a tools problem. The actual challenge was about professional identity and team autonomy. Once I understood that, the work changed completely. Instead of presenting a decision, I brought the teams together to define what “good monitoring” meant from the user’s perspective. The tool selection became their conclusion, not my mandate. The migration took four months after that, and the teams owned the result because they’d built it.

What Adaptive Leadership Looks Like in Practice

Heifetz describes five principles that define adaptive leadership. None of them look like traditional problem solving.

Get on the balcony. Stop participating in the pattern long enough to observe it. Most managers are so embedded in daily operations that they can’t see the dynamics driving the problem. This is different from delegation; it’s deliberate observation. When a conflict keeps recurring in your team, the adaptive move isn’t to mediate it (again). It’s to step back and ask what structural or relational dynamic keeps producing it.

Identify the adaptive challenge. Name the loss. Adaptive change requires people to give something up: a comfortable habit, a professional identity, a way of working they’ve invested years in building. If you can’t articulate what your team would need to lose for the change to succeed, you haven’t diagnosed the challenge. Active listening is the primary tool here. The real resistance rarely shows up in the stated objections.

Regulate distress. Adaptive work is uncomfortable by definition. Too much discomfort and people shut down or revolt. Too little and they stay complacent. Gallup’s 2025 research showed global manager engagement dropped to 27%, with managers under 35 declining five points in a single year. Managers are already stretched. Piling adaptive demands on top of that without managing the psychological load produces exactly the disengagement Gallup is measuring.

The practical version: pace the change. Don’t introduce three adaptive challenges simultaneously. Give people enough psychological safety to voice discomfort without feeling punished. Monitor stress signals, not just progress metrics.

Maintain disciplined attention. Teams under pressure look for work avoidance: blaming external factors, picking fights about side issues, demanding the leader “just decide.” Heifetz calls these “displacement activities.” Your job is to redirect attention to the adaptive issue without letting the team off the hook. This is the opposite of commander’s intent, which works beautifully for technical execution. Adaptive work requires you to stay in the discomfort with your team, not hand them a destination and step back.

Give the work back. The most counterintuitive principle. When the challenge is adaptive, the leader cannot solve it for the team. The team must do the work of changing their own values, habits, or relationships. Your role is to create the conditions, hold the space, and resist the pressure (from the team and from yourself) to provide the answer. If you’ve been a high performer your entire career, this is the hardest transition you’ll make.

The Skill Nobody Trains You For

A 2025 study published in Discover Education (Springer) found that adaptive leadership significantly improves team performance, with employee empowerment as a mediating factor. But the study also confirmed that organizational culture moderates the effect: adaptive leadership works best in cultures that already tolerate some ambiguity and distributed authority.

That creates a chicken-and-egg problem for managers in rigid organizations. You need adaptive leadership to shift the culture, but the culture resists adaptive leadership.

The answer is to start small. Pick one problem on your plate that you’ve tried to solve technically more than once and the fix hasn’t stuck. Ask yourself: what would my team need to change about how they work (not what tools they use) for this to actually resolve? That question is the beginning of adaptive work.

DDI’s data shows that 40% of leaders have considered leaving their roles entirely because of stress. Not workload stress. The stress of facing problems they don’t have the skills to solve. The problems aren’t getting simpler. The technical fixes aren’t working. What’s left is the harder, slower, more human work that Heifetz has been describing for three decades.

Most leadership development programs still train managers to diagnose and fix. Situational leadership teaches you to match your style to your team member’s readiness. Leading through change teaches you to communicate transitions effectively. Both are genuinely useful. Neither prepares you for the moment when the problem isn’t something you can solve at all, and the only path forward is helping your team confront what they’ve been avoiding.

That’s adaptive leadership. It’s not a technique. It’s a willingness to sit with the discomfort of not having the answer, and to trust that the people closest to the problem can find it if you create the conditions for them to look.