Problem-Solution Decoupling¶

Why It Matters¶

Humans have a powerful cognitive bias toward premature convergence - we generate a plausible solution and immediately begin working on it, foreclosing exploration of the problem space. This leads to solving the wrong problem well, or missing superior solutions that require different problem framings. Problem-solution decoupling forces you to earn the right to solve by first demonstrating understanding.

The Key Move¶

When facing any challenge, split your work into two explicit phases with a clear boundary. Phase 1: Investigate the problem without proposing solutions. If you catch yourself thinking "we could just...", stop and redirect to understanding. Phase 2: Generate solutions only after you can articulate the problem in multiple distinct ways. The transition between phases should be deliberate - you should be able to state when and why you're switching from problem to solution mode.

Classic Application¶

IDEO's redesign of the shopping cart (1999). Instead of asking "how do we build a better cart?", the team spent a week in grocery stores observing shopping behavior, talking to customers and staff, and identifying pain points. Only after this immersion did they begin sketching solutions. The resulting design addressed problems (child safety, theft, maneuverability) that weren't in the original brief because they emerged from problem-space exploration.

Surprising Application¶

Debugging relationship conflicts. The natural response to relationship friction is immediate solution generation ("we should schedule more date nights"). Problem-solution decoupling forces a different approach: spend time understanding what each person actually experiences as the problem, without proposing fixes. Often the "problem" transforms - what looked like insufficient time together reveals itself as feeling unheard during the time you already have. The solution space for the second problem is entirely different from the first.

Failure Modes¶

Infinite deferral - using "we need to understand the problem better" to avoid taking action. Works poorly for true emergencies where any solution now beats the perfect solution later. Can feel wasteful in situations where the problem genuinely is well-understood and implementation is the bottleneck. Breaks down when problem and solution co-evolve (common in research and innovation) rather than following a linear sequence.

Go Deeper¶

Dorst, "The Core of 'Design Thinking' and Its Application" (Design Studies, 2011); Rittel & Webber, "Dilemmas in a General Theory of Planning" (Policy Sciences, 1973)

Friction - Military Strategy & Strategic Thinking: A Map of the Territory