Study smarter with Fiveable
Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.
Design thinking isn't just a buzzword—it's the foundational framework that separates strategic designers from those who simply make things look pretty. You're being tested on your ability to understand when and why each stage matters, not just what happens in each one. The process demonstrates core principles of user-centered design, iterative development, and evidence-based decision making that appear throughout advanced design strategy.
Here's what makes this tricky: the stages aren't strictly linear. Real-world design problems require you to move fluidly between stages, sometimes looping back multiple times before moving forward. Don't just memorize the stage names—know what triggers movement between stages, what outputs each stage produces, and how the entire framework embodies divergent and convergent thinking patterns.
These first two stages focus on diverging to gather information, then converging to define the challenge. The goal isn't to solve anything yet—it's to ensure you're solving the right problem.
Compare: Empathize vs. Define—both are research-focused, but Empathize is about gathering insights while Define is about synthesizing them into actionable direction. If an exam question asks about moving from ambiguity to clarity, Define is your answer.
This is where divergent thinking dominates. The goal is quantity over quality—you're generating options, not committing to answers.
Compare: Define vs. Ideate—Define converges on one problem, while Ideate diverges into many solutions. This diverge-converge rhythm is the heartbeat of design thinking.
These stages shift from thinking to making and measuring. The goal is learning through tangible artifacts and real user feedback.
Compare: Prototype vs. Test—Prototyping is about building to think, while Testing is about building to learn from users. A prototype without testing is just an expensive guess.
This stage acknowledges that design thinking is cyclical, not linear. It's the mechanism that connects outputs back to inputs.
Compare: Test vs. Iterate—Testing generates insights, but Iterate is the decision point where you determine which stage to revisit. Strong designers can articulate why they're looping back and what they expect to learn.
| Concept | Best Examples |
|---|---|
| Divergent Thinking | Empathize, Ideate |
| Convergent Thinking | Define, Prioritization in Ideate |
| User Research | Empathize (primary), Test (validation) |
| Synthesis | Define, Iterate |
| Making & Building | Prototype |
| Evidence-Based Decisions | Test, Iterate |
| Problem Framing | Define |
| Solution Generation | Ideate, Prototype |
Which two stages primarily employ divergent thinking, and what distinguishes their outputs?
A usability test reveals users don't understand the core value proposition. Which stage should you return to—Define or Ideate—and why?
Compare and contrast empathy maps and user personas: when is each tool most valuable, and what stage produces each?
If an FRQ asks you to explain why low-fidelity prototypes are preferred early in the process, what principle should anchor your response?
A team skips the Define stage and moves directly from Empathize to Ideate. What specific risks does this create, and how might it manifest in their final product?