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 thoughtful, user-centered design from guesswork. You're being tested on your ability to understand when and why each step matters, not just your ability to recite them in order. Exam questions will ask you to identify which phase addresses a specific problem, explain why iteration loops back to earlier stages, and demonstrate how the process creates solutions that actually work for real users.
The six steps represent a shift from designer-centered to user-centered thinking. Each phase builds on the previous one, but the process isn't purely linear—it's deliberately cyclical. Master the purpose behind each step, understand how they connect, and you'll be ready for any scenario-based question thrown your way. Don't just memorize the sequence—know what problem each step solves and when you'd return to it.
Before you can solve anything, you need to deeply understand what you're solving and for whom. These phases focus on discovery and definition—gathering insights and translating them into actionable direction.
Compare: Empathize vs. Define—both deal with understanding users, but Empathize gathers raw data while Define synthesizes it into direction. If an exam asks which phase produces a problem statement, it's always Define.
Once you understand the problem, these phases shift to divergent and convergent thinking—first expanding possibilities, then narrowing to viable concepts worth building.
Compare: Ideate vs. Prototype—Ideate generates concepts while Prototype makes them tangible. A common exam mistake is confusing brainstorming (Ideate) with building mockups (Prototype). Remember: ideas live in Ideate, artifacts emerge in Prototype.
The final phases close the loop by testing assumptions against reality and incorporating what you learn. This is where design thinking proves its value—through evidence-based improvement.
Compare: Test vs. Iterate—Test reveals problems through user feedback, while Iterate addresses them through refinement. FRQ tip: if asked about responding to negative user feedback, your answer involves both phases—Test identifies issues, Iterate resolves them.
| Concept | Best Examples |
|---|---|
| User Research | Empathize (interviews, personas, observation) |
| Problem Framing | Define (problem statements, affinity diagrams) |
| Divergent Thinking | Ideate (brainstorming, mind mapping) |
| Convergent Thinking | Ideate (feasibility filtering), Prototype (selecting features) |
| Rapid Experimentation | Prototype (low-fidelity mockups, paper prototypes) |
| Validation | Test (user testing, feedback collection) |
| Cyclical Process | Iterate (returning to earlier phases) |
| User-Centered Focus | All phases, but especially Empathize and Test |
Which two phases both involve direct interaction with users, and how do their goals differ?
A team realizes their problem statement was too narrow after building a prototype. Which phase should they return to, and why does this demonstrate design thinking's non-linear nature?
Compare and contrast low-fidelity and high-fidelity prototypes—when would you use each, and what phase considerations apply?
If user testing reveals that people love a feature but can't figure out how to access it, which earlier phase's assumptions were likely flawed, and what would you revisit?
Explain why skipping the Empathize phase and jumping straight to Ideate often produces solutions that fail—what specific risks does this create?