Distinguish technical problems from adaptive challenges

Separate problems you can solve with existing expertise from those requiring you to change.

Why it works

Kegan and Lahey (and independently, Ronald Heifetz) draw a sharp distinction between technical problems (solvable with current knowledge) and adaptive challenges (requiring a change in values, beliefs, or behavior — in Kegan’s terms, a subject-object shift). Most people attack adaptive challenges with technical solutions and wonder why nothing changes. Diagnosing correctly is 80% of the work because it changes what kind of response is called for.

How to do it

1. Name a persistent problem you’ve been working on. Ask: "Have I already solved this with better information or skills and it came back?" If yes, it may be adaptive.
2. Ask: "Would solving this require me to change a belief, a value, or a way of relating — or just learn a new technique?"
3. If adaptive: resist the urge to apply a technical fix. Instead, begin immunity mapping.
4. If technical: apply the technique and free up attention for the adaptive work.

Evidence

Adaptive vs. technical challenge distinction originates with Heifetz (1994) and was integrated into Kegan’s framework. It is widely used in leadership development and organizational consulting contexts. (clinical)

This distinction is a conceptual framework; its clinical application is practitioner-validated rather than outcome-trialed in controlled studies.

Sources

• Heifetz (1994), Leadership Without Easy Answers (Harvard University Press)
• Kegan & Lahey (2009), Immunity to Change

Common mistake

Treating all problems as adaptive (as a reason to avoid getting expert help) or all as technical (as a reason to avoid genuine self-examination).