In this article
- The 5 Stages of Design Thinking
- The Empathize Stage: The Most Skipped Step
- Writing a Good Problem Statement (How Might We...)
- Prototyping: Low Fidelity First, Always
- How Design Thinking Applies to UI/UX Design
Design thinking gets described in a lot of different ways — sometimes as a mindset, sometimes as a methodology, sometimes as a set of sticky-note workshops. In practice, it's a structured approach to solving problems that puts the user at the center of every decision. Once you understand the framework, it changes how you approach every design challenge.
The 5 Stages of Design Thinking
The Stanford d.school framework — which has become the industry standard — defines five stages: Empathize, Define, Ideate, Prototype, and Test. These are not strictly sequential. In practice, design teams move back and forth between stages as they learn more. The framework is a guide, not a checklist.
- Empathize: Understand the user through research — interviews, observations, immersion. The goal is to see the problem through their eyes.
- Define: Synthesize your research into a clear problem statement. A good problem statement focuses on user needs, not product features.
- Ideate: Generate as many possible solutions as you can — quantity before quality. Defer judgment during ideation.
- Prototype: Build rough, low-cost representations of your best ideas. A prototype is not a finished product — it's a tool for learning.
- Test: Put prototypes in front of real users. Observe and listen. What works? What doesn't? What surprises you?
The Empathize Stage: The Most Skipped Step
The vast majority of design problems — and failed products — come from skipping or shortchanging the empathy stage. It's tempting to rush to solutions because solutions feel productive. But solutions built on assumptions are expensive. Thirty minutes of user observation saves thirty days of building the wrong thing.
The worst product decisions are made by people who think they know their users without ever actually talking to them. Schedule a user interview before you design anything.
Writing a Good Problem Statement (How Might We...)
The 'How Might We' (HMW) format is the industry standard for turning research insights into actionable design challenges. It starts with a question: 'How might we help [user] accomplish [goal] despite [constraint]?' This framing is intentionally open — it invites solutions without prescribing them. Compare: 'We need to add a filter to the search results' (solution-first) vs 'How might we help users find the right product faster?' (problem-first, invites better solutions).
Prototyping: Low Fidelity First, Always
A design thinking prototype is not a polished Figma file. It's a paper sketch, a whiteboard diagram, or a rough clickable mockup made in 30 minutes. The purpose is to make your thinking tangible enough to get feedback. High-fidelity prototypes too early create a false sense of completion and make it psychologically harder to throw out and rethink ideas.
How Design Thinking Applies to UI/UX Design
In UI/UX design, design thinking maps directly to the design process: user research (empathize), problem framing and user stories (define), wireframing and sketching (ideate), interactive prototyping (prototype), and usability testing (test). The difference between a designer who uses this framework and one who doesn't is measurable in product quality and user satisfaction.
Design thinking is at the core of how Aizenmarq teaches product design — students apply the full framework on every project from day one. Visit aizenmarq.com to see how we approach design education.
