Design thinking is a user-centric, solution-based approach to product development that moves through five phases—empathize, define, ideate, prototype, and test—to solve real user problems rather than assumed ones. For founders, its core value is discipline: instead of jumping from an idea to a build, you are forced to understand the person affected by the problem before committing resources. Harvard Business School's Esther Han describes the essence of the method as "human-centric and user-specific," requiring questions such as "Who will be using this product?" and "How will this solution impact the user?" This guide walks through each phase and closes with a comparison against Agile and Lean Startup so you can choose the right methodology at the right stage.

Phase 1: Empathize – Understanding Your Users Deeply

Empathy is the first and, in Han's framing, "arguably most important" step of design thinking. The goal is to understand the person behind the problem, because doing so leads to a more impactful solution. This is not a survey checkbox; it is an effort to appreciate the end-user's interests and preferences directly, before any solution is discussed.

Practically, this is the stage where you collect relevant information about your users. Miro's guidance on design thinking recommends researching what pain points customers grapple with regularly and how your product could alleviate them. The American Marketing Association's overview of the five phases stresses that this grounding ensures solutions are rooted in actual experiences rather than assumptions or internal business goals—a shift that means asking "What problem are we solving for the user?" instead of "What features can we add?"

For a founder, the empathize phase means immersing yourself in user experiences: observing real behavior, gathering firsthand accounts of the problem, and resisting the pull of internal strategy discussions. IDEO's own three-phase model, as summarized by the AMA, begins with exactly this—research and observation of real user behavior to uncover deep insights. The output of this phase is not a solution; it is a body of evidence about what your users actually want and struggle with.

Phase 2: Define – Framing the Core Problem

Once research is gathered, the define phase converts it into a clear, prioritized problem statement. Miro's framework describes this as evaluating the information you've collected and using aids such as the bull's eye diagram to pin down the most important problems—your most significant challenges and how to prioritize them.

The discipline here is framing the problem from the user's perspective rather than the company's. The AMA's guidance contrasts the two mindsets directly: a human-centered definition asks "How does this solution fit into their daily lives?" rather than "How does this align with our internal strategy?" A well-formed problem statement keeps the team anchored to the user even as solution ideas start to multiply.

This phase is also where founders earn the right to move forward. A vague problem statement—"users need a better app"—produces vague solutions. A defined, user-centered statement names who is affected, what they struggle with, and why it matters to them. It becomes the reference point against which every later idea and prototype is judged, and it is the single most important artifact a founder produces before ideation begins.