Anti-patterns: what can go wrong
Over years of practice, we've identified recurring failure patterns in Problem Phase. Knowing them doesn't guarantee avoiding them, but it significantly increases the probability of detecting them in time.
1
Organized Bias
›2
Express Discovery
›3
Problem Statement by Committee
›4
The Invisible Stakeholder
›5
The Solution Disguised as a Problem
›6
Undefined Success
›7
Phantom Constraints
›Quick reference
| Anti-pattern | Symptom | Root cause | Prevention |
|---|---|---|---|
| Organized Bias | Problem Statement identical to starting hypothesis | Interviews designed to confirm, not challenge | Document hypotheses before discovery; "devil's advocate" role |
| Express Discovery | Fewer than 5 interviews, no tensions | Pressure to move forward | Minimum 5 interviews as non-negotiable rule |
| Problem Statement by Committee | Generic statement valid for any company | Optimizing for political consensus | One person drafts, team reviews; specificity test |
| Invisible Stakeholder | Single-perspective Problem Statement | Key actors excluded from interviews | Verify Actor Map coverage before closing |
| Solution Disguised as Problem | Statement describes absence of a tool | Skipping from symptom to solution | Multiple-solution test: at least 3 solutions possible |
| Undefined Success | Each stakeholder assumes different definition | No explicit success criteria | Ask each stakeholder "how will you know it's solved?" |
| Phantom Constraints | Unverified constraints limiting solution space | Assumptions not checked with source | Every constraint needs a verified source |