Diagnose the challenge before choosing the response

Ask whether the problem requires new expertise (technical) or new values and behavior (adaptive).

Why it works

Technical problems sit in familiar territory — the answer exists, someone with authority or skill can apply it, and stakeholders largely accept the solution. Adaptive challenges require loss: people must give up something they value. Applying a technical fix to an adaptive problem provides the comfort of action while bypassing the real work, which is why so many change initiatives fail without touching the root cause.

How to do it

1. Name the problem precisely, then ask: "Does a proven solution exist, or does this require people to change what they believe or how they work?"
2. If the answer is "change beliefs or habits," treat it as adaptive — not a knowledge gap to fill.
3. Identify who owns the adaptive work (it is rarely the leader alone) and whose loss is required for progress.
4. Resist the pull to act immediately; clarity about type saves wasted effort downstream.

Evidence

The technical/adaptive distinction is a conceptual framework developed from case study research and field observation at Harvard’s Kennedy School of Government. It is widely adopted in leadership education and organizational consulting. (clinical)

The framework is influential and coherent but based on qualitative case analysis rather than controlled trials. Its power is diagnostic, not predictive.

Common mistake

Treating every hard problem as technical because adaptive problems are uncomfortable — resulting in process redesigns and new hires when the real need is a values conversation.