Design Thinking¶

"Design thinking is a human-centered approach to innovation that draws from the designer's toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success." — Tim Brown, IDEO

Overview¶

Design thinking is a methodology for creative problem-solving that prioritizes understanding users deeply before jumping to solutions. It encourages iteration, prototyping, and embracing failure as a learning tool.

Key insight: Design thinking treats problems as opportunities for innovation, not just issues to fix. It systematically builds empathy before ideation.

The IDEO 5-Phase Model¶

The most widely used design thinking framework comes from Stanford d.school and IDEO:

flowchart LR
    classDef understand fill:#1E3A5F,stroke:#0D47A1,color:#E3F2FD
    classDef create fill:#5D4037,stroke:#3E2723,color:#FFF8E1
    classDef validate fill:#1B5E20,stroke:#0D3D13,color:#E8F5E9

    E[Empathize]:::understand
    D[Define]:::understand
    I[Ideate]:::create
    P[Prototype]:::create
    T[Test]:::validate

    E --> D --> I --> P --> T
    T -.->|iterate| E

The Double Diamond¶

The British Design Council's Double Diamond visualizes divergent and convergent thinking:

flowchart LR
    classDef problem fill:#1E3A5F,stroke:#0D47A1,color:#E3F2FD
    classDef solution fill:#1B5E20,stroke:#0D3D13,color:#E8F5E9

    subgraph Problem["PROBLEM SPACE"]
        direction LR
        DIS[Discover]:::problem
        DEF[Define]:::problem
    end

    subgraph Solution["SOLUTION SPACE"]
        direction LR
        DEV[Develop]:::solution
        DEL[Deliver]:::solution
    end

    DIS --> DEF --> DEV --> DEL

Key principle: You must diverge (explore widely) before you converge (focus narrowly). Jumping to solutions skips the divergent phase where breakthrough insights emerge.

Empathize Phase¶

Empathy is the foundation. Without deep user understanding, you're guessing.

Techniques¶

Empathy Map¶

Define Phase¶

Synthesis transforms research into actionable problem statements.

Point of View (POV) Statement¶

[USER] needs [NEED] because [INSIGHT].

Example:

"Time-strapped managers need to spot team blockers quickly because delayed intervention leads to cascading delays."

How Might We (HMW) Questions¶

Transform POV statements into design challenges:

HMW sweet spot: Broad enough to encourage creative solutions, narrow enough to be actionable.

Ideate Phase¶

Generate quantity before quality. Defer judgment.

Brainstorming Rules¶

1. Defer judgment — No criticism during ideation
2. Encourage wild ideas — They often lead to practical breakthroughs
3. Build on others' ideas — "Yes, and..." not "No, but..."
4. Stay focused — One conversation at a time
5. Be visual — Sketch, diagram, prototype
6. Go for quantity — More ideas = better ideas

Techniques¶

Prototype Phase¶

Prototypes make ideas tangible and testable. Start rough.

Prototype Fidelity¶

Rule of thumb: Use the lowest fidelity that can answer your question.

Rapid Prototyping Principles¶

• Fast over perfect — Spend hours, not weeks
• Disposable — Don't get attached
• Just enough — Only build what you're testing
• Specific — Test one hypothesis at a time

Test Phase¶

Testing validates (or invalidates) your assumptions.

Testing Approaches¶

Feedback Interpretation¶

Design Thinking and AI Agents¶

For AI agents designing interfaces, design thinking provides:

Key principle for agents: Ask clarifying questions (empathize/define) before generating solutions (ideate/prototype).

Common Pitfalls¶

Related Reading¶

• Lean UX — Design thinking applied to product teams
• User Journeys — Empathy mapping technique
• Personas — Defining who you're designing for

References¶

• Tim Brown, "Change by Design" (2009)
• IDEO, "The Field Guide to Human-Centered Design" (2015)
• Jake Knapp, "Sprint" (2016)