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.
Phase 3: Ideate – Generating Creative Solutions
With the problem defined, ideation opens up the solution space. The purpose of this phase is to explore as many possibilities as possible—brainstorming, divergent thinking, and generating a wide range of creative solutions without initial judgment. The AMA's phase overview notes that the best solutions often emerge from uncertainty, and that embracing ambiguity and iteration is a core mindset of the approach rather than a flaw in it.
IDEO's model folds prototyping into ideation itself: the ideation stage is where teams explore creative possibilities, challenge assumptions, and prototype. That overlap is instructive for founders with limited time—idea generation and rough expression of ideas can reinforce each other, because making an idea tangible quickly reveals whether it survives contact with its own logic.
The key behavioral rule is deferral of judgment. Early criticism collapses the solution space before it has been explored; the divergent phase deliberately widens it. A founder running this phase should aim for quantity and variety first, then converge on the ideas most directly tied to the defined user problem. The exit condition is a shortlist of solution concepts that each plausibly address the problem statement.
Phase 4: Prototype – Making Ideas Tangible
Prototyping turns selected ideas into tangible representations—sketches, wireframes, mockups, or physical models. The point is speed and cost: low-fidelity representations let a team test new concepts quickly and cheaply, before significant development resources are committed. IDEO U's own explanation of the process emphasizes that testing is "not just about validating an idea—it's about uncovering what doesn't work so you can improve," and prototypes are what make that discovery possible.
For founders, the prototype phase is a risk-reduction mechanism. A sketch or wireframe invites critique that a polished product discourages; users respond more honestly to something obviously unfinished. Rapid prototyping also allows teams to test new concepts quickly, as TechBlocks notes in its discussion of combining design thinking with Agile engineering—each prototype is a cheap experiment against an expensive build decision.
The phase's exit criterion is a prototype concrete enough to put in front of real users. It does not need to be functional or beautiful; it needs to express the proposed solution clearly enough that a user can react to it, and that the team can observe where the reaction diverges from expectation.
Phase 5: Test – Refining Solutions with Users
Testing closes the loop by putting prototypes in front of users and learning from what fails. IDEO U frames evaluation through four lenses: desirability—does this meet a real human need; feasibility—can we realistically build it; viability—will it be sustainable over time; and responsibility—is it ethical and does it avoid unintended harm. Its worked example, a medication management app, shows the lenses in action: does it make tracking medications easier, can users update their lists easily, will enough people use it to make it sustainable, and does it protect patient data.
Testing is iterative, not terminal. Findings feed back into earlier phases—a failed assumption may send the team back to ideation, or even back to the problem definition. The AMA's overview of the methodology stresses iteration as a defining feature, and Miro's guidance treats incorporating user feedback as an integral part of user-focused product development rather than a final sign-off step.
For a founder, the test phase answers a go/no-go question with evidence: which elements of the solution users actually value, which confuse them, and whether the concept holds up across desirability, feasibility, viability, and responsibility before scaling investment behind it.
Design Thinking Decision Framework for Founders
The table below consolidates the five phases into a sequential decision process. For each phase, it states the key question a founder must answer, the core activities that answer it, and the exit criteria that signal readiness to move on. Work through it in order; a phase you cannot exit cleanly is a phase you have not finished.
| Phase | Key Question | Core Activities | Exit Criteria |
|---|---|---|---|
| Empathize | What are the users' needs, desires, and pain points? | Conduct user research, observations, and immerse in user experiences; research recurring pain points and how the product could ease them. | A body of firsthand evidence about user needs and pain points, rooted in actual experiences rather than assumptions or internal business goals. |
| Define | What is the core user problem we are trying to solve? | Synthesize research, frame the problem from a user perspective, create a problem statement, and identify key insights; prioritize the most significant challenges. | A clear, user-centered problem statement that names who is affected and what they struggle with. |
| Ideate | How might we solve the defined user problem? | Brainstorming, divergent thinking, and generating a wide range of creative solutions without initial judgment. | A shortlist of solution concepts, each plausibly tied to the defined problem statement. |
| Prototype | How can we make our ideas tangible? | Create tangible representations like sketches, wireframes, mockups, or physical models. | A low-fidelity prototype concrete enough to put in front of real users. |
| Test | Does the solution hold up across desirability, feasibility, viability, and responsibility? | Evaluate prototypes with users through the four lenses: does it meet a real human need, can it realistically be built, will it be sustainable, and is it ethical without unintended harm. | Evidence of which elements users value and which fail, feeding iteration or a go/no-go decision on further investment. |
Note that the framework is a loop, not a line. Testing that uncovers a flawed assumption sends you back to define or ideate; that return is the method working as intended, not a failure of process.
Design Thinking vs. Agile vs. Lean Startup: Choosing the Right Methodology
Founders often treat design thinking, Agile, and Lean Startup as competing options, but the AMA's comparison positions them as serving different purposes at different stages of the creative and development process. All three emphasize iteration, user feedback, and adaptability; their primary focus differs. Design thinking focuses on understanding user needs and designing innovative solutions. Agile focuses on developing a working product through continuous iteration. Lean Startup focuses on testing business assumptions with rapid experiments.
The practical division of labor follows from those focuses. Design thinking is a discovery process—its research techniques, drawn from social sciences like ethnography and psychology, find human needs and motivations, which makes it most valuable early, when uncertainty about the problem is highest. Agile excels at delivery: TechBlocks' analysis of combining the two notes that Agile teams can risk losing sight of client satisfaction if they focus too much on incremental changes, and design thinking supplies the human insight that keeps those iterations pointed at real needs. A Forrester Consulting study for IBM, cited in that analysis, found that a design thinking strategy can cut development and testing time by up to 33%.
Lean Startup, as Appcues' Katryna Balboni explains, treats every idea as a hypothesis that must be validated or invalidated through small prototypes—minimum viable products—whose results feed the next iteration. Where design sprints validate solutions to customers' problems, the lean startup approach extends validation to the business model itself, testing elements like marketing messages and pricing. The AMA concludes that understanding how the three interact helps teams apply the right methodology at the right time, or combine them for maximum impact. This comparison is conceptual—it clarifies roles rather than prescribing a technical integration.
Applying Design Thinking for User-Centric Product Success
Founders should integrate Design Thinking into the early stages of product development to ensure solutions are deeply rooted in user needs before transitioning to development and validation methodologies. Use design thinking to discover and define the problem and to shape and test solution concepts; hand off to Agile for continuous delivery once a core problem and solution direction are established; and use Lean Startup's build-measure-learn cycles to validate the business model around the product with MVPs.
The measurable indicator of readiness to move forward is successful completion of the 'Define' phase with a validated, user-centered problem statement, indicating readiness to move to ideation and prototyping. If you cannot write that statement from evidence you gathered in the empathize phase, you are not ready to ideate—and the cheapest place to fix that gap is before a single line of code is written. This article is a guide to the methodology, not a substitute for professional product management or UX design expertise.
Sources
- What Is Design Thinking & Why Is It Important? — Harvard Business School
- What Is Design Thinking and Why You Need It — MiroBlog
- The 5 Phases of Design Thinking — American Marketing Association
- What is Design Thinking & Why Is It Beneficial? — IDEO U
- Combining Design Thinking & Agile for Software Engineering — TechBlocks
- Agile, design sprints, lean startup, or design thinking: Which methodology is right for your team? — Appcues




