What Is Design Thinking?
Design thinking is a human-centered approach to innovation and problem-solving that draws from the mindset and methods of designers. Originally developed in academic and design circles, it has become one of the most widely adopted innovation frameworks in business — used by teams ranging from early-stage startups to global organizations.
At its core, design thinking insists on deeply understanding people's needs before jumping to solutions. This sounds obvious, but it runs counter to how most organizations naturally operate — where solutions are often proposed before the problem is truly understood.
The Five Stages of Design Thinking
1. Empathize
The process begins by setting aside assumptions and genuinely understanding the people you are designing for. This involves:
- Observational research — watching how people interact with products, services, or environments
- In-depth interviews focused on emotions, motivations, and frustrations
- Creating empathy maps that capture what users say, think, feel, and do
The goal is to uncover latent needs — problems people experience but haven't articulated, or needs they don't yet know they have.
2. Define
After gathering empathy data, teams synthesize their findings into a clear problem statement. A well-crafted problem statement (sometimes called a "How Might We" question) is:
- Human-centered — framed around a specific person's need
- Broad enough to allow creative solutions
- Narrow enough to be actionable
Example: Instead of "How do we increase app downloads?" try "How might we help busy parents stay consistent with their wellness goals despite unpredictable schedules?"
3. Ideate
With a clear problem statement in hand, teams enter structured brainstorming. Effective ideation follows a few key principles:
- Defer judgment: No idea is too wild at this stage — evaluation comes later
- Quantity over quality: Generate as many ideas as possible before filtering
- Build on others: Use existing ideas as springboards, not competition
Techniques like SCAMPER, random word association, and "worst possible idea" can break cognitive fixation and unlock genuinely novel approaches.
4. Prototype
Prototyping turns ideas into tangible, testable artifacts — quickly and cheaply. The purpose is not to build a finished product, but to create something that can be placed in front of users to learn from.
Prototypes can be:
- Paper sketches of an interface
- Cardboard models of a physical product
- Role-played service scenarios
- Simple click-through wireframes
The emphasis on "low fidelity" is intentional — teams are more willing to abandon or radically change something they spent hours on, rather than weeks.
5. Test
Prototypes are tested with real users to gather feedback. Unlike user acceptance testing at the end of a project, design thinking tests happen early and often. Key principles:
- Observe how users interact — what they do matters more than what they say
- Ask open-ended questions; avoid leading the witness
- Treat results as learning input, not pass/fail verdicts
Insights from testing feed back into earlier stages. Design thinking is inherently iterative — you may cycle through Empathize → Define → Ideate multiple times before converging on a solution.
Where Design Thinking Works Best
Design thinking excels in situations of ambiguity — when the problem itself isn't well understood, or when multiple stakeholders have conflicting views of what needs to be solved. It is particularly valuable for:
- New product or service development
- Improving customer experience journeys
- Internal process redesign
- Organizational change challenges
Common Mistakes to Avoid
- Skipping empathy: Jumping straight to solutions defeats the entire purpose
- Treating it as linear: The stages are a guide, not a rigid sequence
- Over-polishing prototypes: High-fidelity prototypes discourage honest feedback
- Testing with internal teams only: You need real users, not colleagues who know your context
Starting Your First Design Sprint
If you're new to design thinking, a focused Design Sprint (a 5-day adaptation popularized by Google Ventures) is an excellent entry point. It compresses the full methodology into an intensive week, producing a tested prototype from a defined challenge. It's a powerful way to experience the methodology's value before committing to broader organizational adoption.