How to Tell You Can Move On In Each Stage of the Design Thinking Process

A good way to think about Design Thinking is that you don’t leave a stage because you’ve spent enough time there, you leave because you’ve you are confident enough to justify moving forward. Each stage has “exit criteria” in the form of questions. We’ll cover those for each stage here.

Here’s a practical framework:

Understand: Learn the business and technical landscape
Before anything else, you need to get your bearings on the business you’re working on. Understanding the business goals, the technical constraints, and the broader context the problem lives in. You’ll talk to stakeholders, and interview them. Read the briefs, maybe even help draft them. Map out what’s known and what isn’t. You’re ready to move on when you can explain the problem space clearly to someone who knows nothing about it, you’ve surfaced your assumptions and labeled them as such, and you know which constraints are truly fixed and which are negotiable.

Empathize: Understand users and their needs
This is where you shift from the business view to the human view. You’ll get your boots on the ground and observe real people in context of real situations. Watch their actions, not just what they say they would do in a given situation, there’s often a gap. You’re ready to move on when you can predict with reasonable confidence how users will react to a given situation, you’re designing for a real, specific person and not a vague archetype and your insights come from observed behavior rather than assumptions.

Define: Frame the right problem
With your research in hand, you now can synthesize your data into a clear problem statement. This is harder than it sounds. Many design thinking teams are in danger here of defining the wrong problem. You’ll know you are successful when your problem statement is specific enough that you could measure whether it’s been solved, when you’re confident the problem is real and not a symptom of something deeper, and when solving it would genuinely improve the users who interact with the tool or experience.

Ideate: Generate possibilities
Now you can open up you team in the room to some creative fun. The goal in ideation is quantity and diversity of ideas, not quality, that judgment comes later in the process. Explore ideas that feel obvious, ideas that feel out there or even moonshot ideas, after all this is your chance to test something really outlandish. You’re ready to move on when you’ve generated ideas that are fundamentally different from one another (not just variations on one approach), and when you can honestly align with your team you’re choosing this for it’s testable unknown factors that you want to learn more about, it’s something different and unexpected that could work.

Prototype: Learn quickly
Build a prototype to test your assumptions you’re most uncertain about. The biggest mistake here is over-building. Move quickly, be raw, embrace the impact, as long as the core ideas are there. You’re ready to move on when your prototype is far enough along where a user can flow through it and talk about their decisions out loud, directly towards particular uncertainty.

Test: Validate learning
Put your prototype in front of real people and watch what happens. Don’t explain it, defend it, or guide them, just observe and encourage them to be vocal. The goal is to prove users understand, are comfortable or discuss what is challanging to them. You’re ready to move on when you’ve gathered enough signals to make a confident decision about next steps. This might mean iterating on the current idea, pivoting to a different approach, or moving forward with confidence. Document what surprised you. Surprises are where the real learnings are.