Design thinking process define stage design talk focuses on clarifying problem statements and aligning stakeholders before solutions are explored. This phase turns ambiguous challenges into clear, testable problem statements that guide the rest of the design sprint.
During define, teams synthesize research insights into a concise point of view and establish success metrics that stakeholders can reference throughout the project.
| Stage | Primary Goal | Key Activities | Deliverables |
|---|---|---|---|
| Empathize | Understand user needs and context | User interviews, field observations, shadowing | User personas, journey maps |
| Define | Frame the core problem to solve | Affinity mapping, point of view synthesis, problem framing | Problem statement, success metrics |
| Ideate | Generate a wide range of solutions | Brainwriting, SCAMPER, storyboarding | Idea backlog, concept sketches |
| Prototype | Build low-fidelity representations | Paper prototypes, clickable mockups, storyboards | Lo-fi prototypes, scenario cards |
| Test | Validate solutions with users | Usability testing, interviews, analytics review | Test report, iteration backlog |
Define Problem Statement Workshop
A Define Problem Statement Workshop structures messy insights into a clear narrative that the team can rally around. Facilitators guide stakeholders to articulate users, needs, and barriers in a single, testable sentence.
This workshop often includes constraint mapping and impact framing so that business goals remain visible without overshadowing user outcomes.
Stakeholder Alignment Through Design Talk
Design talk in the define stage creates a shared language across product, business, and end users. By narrating user stories aloud, teams surface assumptions that might otherwise derail later work.
Stakeholder alignment is measured not only by agreement but by the ability of each participant to explain the problem statement in their own words.
Journey Map Synthesis in Define
Journey map synthesis transforms research notes into a coherent storyline of user behaviors, emotions, and pain points. Teams highlight critical moments where intervention could significantly improve outcomes.
These synthesized maps become reference artifacts that keep decisions focused on user value throughout ideation and prototyping.
Success Metrics Definition
Success metrics definition ensures that every experiment in later stages can be evaluated against clear, shared criteria. Teams choose leading and lagging indicators that reflect both user satisfaction and business impact.
Documenting these metrics during define prevents scope creep and provides an objective baseline for test results.
Operationalizing Define Phase Insights
Moving define insights into tangible artifacts ensures that every team member understands the problem scope and measurement criteria.
This alignment reduces rework and keeps subsequent ideation tightly focused on validated user needs.
- Synthesize research into a single point of view statement
- Document clear success metrics for user and business outcomes
- Run a Define Problem Statement Workshop to align stakeholders
- Create a lightweight journey map highlighting critical moments
- Use design talk to surface assumptions and build shared language
FAQ
Reader questions
How long should the Define Problem Statement Workshop last with cross-functional stakeholders?
Typically 60 to 90 minutes, with an additional 30 minutes reserved for synthesis and documentation to ensure shared clarity.
What if stakeholders disagree on the core problem statement during design talk?
Facilitators should capture multiple perspectives, then narrow them to a single testable statement that balances user needs with feasible business outcomes.
How do you prioritize which journey map moments to focus on during define stage design talk?
Prioritize moments with high user pain and high business impact, using impact-effort matrices to guide selection while keeping the problem statement coherent.
Can success metrics be changed after testing has started in the define phase?
Yes, but changes require revisiting the point of view to maintain alignment between user outcomes, stakeholder goals, and evolving hypotheses.