Core Idea
Definition
Design thinking is an iterative framework for generating and testing solutions by deeply understanding users, reframing problems, exploring alternatives, and learning through prototypes.
In Plain English
Start with the people affected, define the real problem carefully, generate possibilities, and learn by making things testable early.
Framework Structure
Components
Flow
Understand users -> Define the problem -> Generate ideas -> Build low-cost prototypes -> Test and refine
How to Apply
- 1.Spend time understanding the real experience of the people involved
- 2.Define the problem in a way that reflects user needs and constraints
- 3.Generate multiple possible solutions before committing
- 4.Prototype quickly enough that learning is cheap
- 5.Test with real users or realistic feedback loops and revise
When to Use
- •Product and service design
- •Workflow or experience redesign
- •Problems where user perspective is underdeveloped
- •Early-stage solution exploration
- •Any setting where creativity should stay grounded in lived reality
When NOT to Use
- •When the issue is already well-defined and mainly needs execution
- •When the process becomes performative and detached from real user contact
- •When the team mistakes brainstorming theater for insight
- •When a highly technical optimization problem requires other primary tools
Example
Problem
A team wants to improve a confusing onboarding flow.
Application
- 1.Observe and interview users to understand where they struggle
- 2.Define the real friction point instead of the assumed one
- 3.Generate several possible simplifications or guidance patterns
- 4.Prototype the best candidates and test them quickly with real users
Conclusion
The solution quality improves because the process stays tied to user experience rather than internal guesswork.
Takeaway
Design thinking is strongest when empathy and experimentation both stay real.
Common Mistakes
- •Skipping empathy and designing from internal assumptions
- •Falling in love with the first idea instead of exploring alternatives
- •Prototyping too late or too expensively
- •Treating user testing as validation theater rather than learning
- •Confusing novelty with usefulness
How to Practice
user reality first
Before ideating, gather direct evidence of how the current experience actually feels for the user.
prototype before polish
Test rough versions early instead of waiting until the solution feels finished.
three solution rule
Force at least three distinct solution directions before narrowing.
Related Cognitive Biases
curse of knowledge
Teams often design from their own understanding rather than from the user's confusion.
solution fixation
People latch onto early ideas before understanding the problem well enough.
confirmation bias
Teams may use user research only to confirm what they already hoped to build.
Related Frameworks
Related Skills
Variants & Extensions
Typical Failure Modes
- •Empathy skipped
- •Idea fixation
- •Testing theater
Further Reading
- Change by Design by Tim Brown
- Creative Confidence by Tom Kelley and David Kelley
- Design a Better Business by Patrick Van Der Pijl, Justin Lokitz, and Lisa Kay Solomon