Public preview
Distinguishing Technical from Adaptive Challenges
Classify your problem: technical (known solution) or adaptive (requires shifting minds and values)? Confusing them is leadership failure #1.
Goal
Beat the impulse to fix adaptive problems with technical tools (policy, training, hiring) — top cause of major initiative failure.
Steps
-
1
Write your team's biggest current challenge in one specific sentence, no vague language.
Expected Outcome
Immediate
You stop wasting resources on "more training" for adaptive problems. Immediate savings.
Evidence base
School: Adaptive Leadership
Founders: Ron Heifetz · Marty Linsky (1994)
Developed by Ron Heifetz at Harvard Kennedy School in "Leadership Without Easy Answers" (1994). World's leading executive leadership framework for 30 years.
Keywords
Frequently asked questions
How long does "Distinguishing Technical from Adaptive Challenges" take?
This exercise takes about 45 minutes, practiced with another person in a Written reflection format.
When will I notice the effect of "Distinguishing Technical from Adaptive Challenges"?
You stop wasting resources on "more training" for adaptive problems. Immediate savings. In the short term: Within a quarter, stuck initiatives move because you address real loss, not symptom.
Is "Distinguishing Technical from Adaptive Challenges" evidence-based?
Yes — it draws on Adaptive Leadership (Ron Heifetz, Marty Linsky (1994)). Developed by Ron Heifetz at Harvard Kennedy School in "Leadership Without Easy Answers" (1994). World's leading executive leadership framework for 30 years.
Is "Distinguishing Technical from Adaptive Challenges" suitable for beginners?
Its difficulty level is: Advanced. No external tools required — it can be practiced directly inside the app.
Subscribe for full access
Subscribe to Plus for full access to this practice and the whole catalogue, or try first — free, no sign-in, no commitment.
7 complete practices (one per domain) are free forever, no sign-in.