Challengeescape

Challenge/Escape (Lateral Thinking)

Overview

A lateral thinking technique from Edward de Bono where you deliberately challenge existing assumptions, rules, or approaches, then escape from conventional thinking patterns to generate novel alternatives. Unlike random provocation, challenge/escape is systematic: identify what you take for granted, question whether it must be so, then explore what becomes possible if you abandon that assumption.

Core Principle

Most limitations are self-imposed mental constraints, not physical realities. Escaping these assumptions unlocks breakthrough solutions.

Why this works:

• Dominant patterns suppress alternatives (functional fixedness)
• Expertise creates blindness to violations of "best practice"
• Historical accidents become unquestioned "rules"
• Challenging assumptions creates new solution spaces

Types of Challenges

Challenge Necessity

"Does this have to exist at all?"

• Why do we need this step, component, or feature?
• What if we eliminated it entirely?

Example: "Do we need a checkout page?" (Amazon One-Click escapes this)

Challenge Uniqueness

"Why only one? Why not zero or many?"

• Assumption: One manager per team → Escape: Self-organizing teams or multiple managers
• Assumption: One screen → Escape: No UI or multi-screen experiences

Challenge Sequence

"Does it have to happen in this order?"

• Traditional: Design → Build → Test → Deploy
• Escape: Deploy → Test in production → Iterate

Challenge Magnitude

"Why this amount? Why not 10x more or 1/10th?"

• Assumption: Meetings are 60 minutes → Escape: 5-minute standups
• Assumption: $10 product → Escape: $100 premium or $0 free

Challenge Boundaries

"Why does this constraint exist?"

• Assumption: Must be local → Escape: Remote-first
• Assumption: Must be synchronous → Escape: Async collaboration

Execution Steps

1. Make Assumptions Explicit

• List all implicit assumptions in current approach
• Identify "sacred cows" (things "everyone knows" you must do)
• Notice words like "obviously," "always," "never," "can't"

Example: "Users obviously want more features" (assumption to challenge)

2. Select Assumption to Challenge

• Pick non-obvious constraint (not laws of physics)
• Choose high-impact assumption (if removed, opens big opportunities)
• Start with "That's just how it's done" beliefs

Example: "Reviews must be written by professionals" (challenge for Amazon user reviews)

3. Formulate the Challenge

Template: "Why do we assume [X]? What if [opposite/escape]?"

• "Why must signup require email? What if we used phone numbers?"
• "Why do cars need four wheels? What if zero wheels (hovercraft) or six wheels (stability)?"

4. Explore the Escape Space

• Suspend judgment temporarily (generate first, evaluate later)
• Ask "What becomes possible now?"
• Look for second-order implications

Example: If no email requirement → SMS-based auth → emerging market accessibility

5. Extract Usable Insights

• Most escapes won't be directly implementable
• Look for provocative insights that inform practical solutions
• Ask "What principle from this escape can we apply?"

Example: Full escape (no checkout) → Practical insight (reduce checkout friction)

Anti-Patterns

Challenging Physics: Violating actual laws of nature (can't escape gravity for product design)

Pure Contrarianism: Challenging everything just to be different (nihilism, not creativity)

No Follow-Through: Generating escapes without extracting actionable insights

Premature Evaluation: Killing ideas before exploring implications

Ignoring Constraints: Escaping into fantasyland with no connection to reality

Quality Indicators

High Signal (Productive Challenge/Escape):

• Identifies taken-for-granted assumption
• Escape feels initially absurd but intriguing
• Reveals hidden constraint or opportunity
• Generates actionable derivative ideas
• "Why didn't we think of this before?" feeling

Low Signal:

• Challenges obvious constraints (laws of physics, ethics)
• Escape is just random idea, not systematic
• No insights extracted from the escape
• Pure negation without alternative
• No connection to original problem

Cross-Domain Examples

Product Innovation

• Challenge: "Phones need keyboards" → Escape: Touchscreen-only iPhone
• Challenge: "Hotels need front desks" → Escape: Airbnb keyless entry
• Challenge: "Shopping needs stores" → Escape: Amazon (no physical presence)

Business Model

• Challenge: "Software is bought" → Escape: SaaS subscriptions
• Challenge: "TV needs schedules" → Escape: Netflix on-demand
• Challenge: "Education needs classrooms" → Escape: MOOCs, remote learning

Organizational Design

• Challenge: "Need managers" → Escape: Holacracy, self-management
• Challenge: "9-5 workday" → Escape: Results-only work environment
• Challenge: "Office required" → Escape: Remote-first companies

Personal Productivity

• Challenge: "Need to read whole book" → Escape: Summaries, chapters
• Challenge: "Exercise needs gym" → Escape: Bodyweight, walking meetings
• Challenge: "Career needs single path" → Escape: Portfolio careers

Related De Bono Techniques

• Random Entry: Introduce unrelated concept to break patterns
• Provocation (PO): Deliberately absurd statement to spark ideas
• Reversal: Flip assumption to opposite extreme
• Six Thinking Hats: Structured parallel thinking

Related Frameworks

• First Principles Thinking: Break down to fundamentals, rebuild (similar escape from conventions)
• Inversion: Solve by considering opposite
• TRIZ Contradictions: Systematic ways to escape trade-offs
• Jobs-to-be-Done: Challenge product categories by focusing on job

Scoring (34/50)

• Practitioner Weight (6/10): De Bono methodology used in consulting, moderate adoption
• Clarity (8/10): Clear technique with defined steps
• Proven ROI (6/10): Generates insights but hard to measure impact
• Novelty (7/10): Counter-intuitive, non-obvious approach
• Applicability (7/10): Universal across product, strategy, personal decisions

Sources

• Edward de Bono: Lateral Thinking (1970)
• Edward de Bono: Serious Creativity (techniques and applications)
• Edward de Bono: Six Thinking Hats
• TRIZ literature (systematic constraint-breaking)
• Innovation case studies (iPhone, Airbnb, Netflix as challenges to assumptions)