The Define Phase is the second stage of the Design Thinking process, where insights gathered during the Empathize phase are analyzed and synthesized to clearly define the core problem. It transforms raw observations into actionable problem statements that guide ideation and innovation. This phase ensures that design efforts focus on addressing real user needs rather than symptoms of the problem. By using systematic methods and tools, teams can reframe challenges into opportunities and create a strong foundation for creative solutions.
-
Affinity Diagram
The affinity diagram is a tool used to organize large amounts of qualitative data collected during the Empathize phase. It helps teams cluster related insights, ideas, and observations into meaningful categories. By grouping similar themes, patterns become visible, leading to a clearer understanding of user needs. In India, organizations like Infosys and Wipro use this method during brainstorming workshops. The visual structure simplifies complexity, promotes collaboration, and ensures that all perspectives are considered before defining the final problem statement.
-
Point of View (POV) Statement
A Point of View (POV) statement articulates the specific user, their need, and the underlying insight discovered during research. It defines the design challenge in human-centered terms. The format often follows: [User] needs a way to [need] because [insight]. For example, a farmer needs a simple mobile app to check weather updates because literacy barriers prevent using complex tools. This clarity ensures solutions remain user-focused and actionable, helping teams generate targeted ideas during the Ideate phase.
-
Problem Statement
The problem statement is a concise description of the issue that needs to be solved, grounded in empathy research. It focuses on identifying the real problem rather than the apparent one. For instance, instead of “We need better attendance,” the problem could be “Students need engaging learning methods to stay motivated.” A well-defined problem statement narrows focus, aligns team efforts, and sparks innovative thinking. It acts as the guiding light for ideation, ensuring the solution addresses actual user pain points.
-
How Might We (HMW) Questions
“How Might We” (HMW) questions reframe problem statements into open-ended opportunities for innovation. They invite creative thinking and multiple solutions. For example, “How might we make banking easier for rural customers?” encourages exploration beyond traditional methods. HMW questions are widely used in workshops by companies like TCS and Tata Motors to kickstart ideation. This tool transforms challenges into possibilities, ensuring that the problem definition inspires creativity while remaining user-centered and aligned with real-world needs.
-
User Journey Mapping
User journey mapping visualizes the steps users take to achieve a goal, highlighting their emotions, frustrations, and needs at each stage. This tool helps define where problems occur and why. For instance, mapping a customer’s e-commerce journey may reveal difficulties in payment or delivery tracking. In India, companies like Flipkart and Paytm use journey maps to refine user experiences. It ensures problem statements are based on real evidence, guiding teams toward addressing key pain points effectively.
-
Insight Statements
Insight statements are meaningful observations derived from empathy research that reveal hidden user motivations or challenges. They go beyond surface-level data to uncover emotional or contextual truths. For example, “Young professionals value convenience over cost when choosing online services.” These insights guide problem framing and inspire human-centered design. By synthesizing data into insights, organizations like Infosys and Godrej identify innovation opportunities that truly resonate with users, ensuring the Define phase produces problems worth solving.
-
Empathy Mapping
Empathy mapping is used again in the Define phase to synthesize user emotions and behaviors from research data. It captures what users say, think, do, and feel, helping teams refine understanding of their needs. This tool organizes qualitative information visually, revealing contradictions or gaps. For instance, a user might say a service is convenient but appear frustrated using it. Revisiting empathy maps in the Define phase ensures the problem statement reflects both functional and emotional user experiences.
-
Root Cause Analysis
Root Cause Analysis helps identify the fundamental reasons behind a problem rather than its symptoms. One popular technique is the “Five Whys,” where teams repeatedly ask “Why?” until they uncover the true cause. For example, “Why are users abandoning the app?” leads to insights about poor navigation or unclear instructions. This method ensures teams address the right challenge. Indian organizations use this structured approach to improve efficiency and customer satisfaction while building problem statements that drive meaningful innovation.
-
Fishbone Diagram
Also known as the Ishikawa or Cause-and-Effect diagram, this tool helps visualize factors contributing to a specific problem. Categories like people, process, technology, and environment are analyzed to find root causes. For instance, poor product quality might stem from inadequate training or faulty equipment. Indian companies like Tata Motors use fishbone diagrams in product design reviews. The tool ensures that every possible cause is considered, leading to a more accurate and comprehensive problem definition that guides effective solution development.
-
SWOT Analysis
SWOT Analysis evaluates a situation or organization based on Strengths, Weaknesses, Opportunities, and Threats. It helps frame the design challenge by identifying internal and external factors affecting the user or system. For example, in developing an educational app, strengths could be accessibility, while weaknesses may include poor rural connectivity. Indian startups use SWOT to prioritize innovation areas. This analytical method ensures problem statements are strategic, realistic, and aligned with the broader organizational and market context.
-
Stakeholder Mapping
Stakeholder mapping identifies all individuals or groups involved in or affected by a problem. It visualizes their influence, interests, and relationships to the issue. For example, designing a healthcare solution might involve doctors, patients, families, and policymakers. Indian hospitals and NGOs use stakeholder maps to align needs and expectations. Understanding these connections ensures the problem definition is holistic, balancing diverse perspectives. This tool prevents design bias and helps prioritize whose needs should be addressed first for maximum impact.
-
Experience Mapping
Experience mapping provides a comprehensive view of the user’s interactions with a product, service, or organization over time. It tracks emotions, actions, and perceptions to identify friction points and improvement areas. For example, mapping a passenger’s airport experience can uncover issues with check-in or baggage handling. Indian airports use experience maps to enhance customer journeys. This method ensures that the defined problem is grounded in user reality, improving both functional and emotional aspects of the overall experience.
-
Value Proposition Canvas
The Value Proposition Canvas aligns user needs with the value a solution offers. It consists of two parts—the Customer Profile (pains, gains, and jobs) and the Value Map (products, gain creators, and pain relievers). For example, a financial app might relieve pain by simplifying loan applications. Indian fintech companies use this tool to match innovation with user expectations. It ensures that problem statements are strategically focused, guiding teams to design solutions that deliver maximum user and business value.
-
Customer Journey Analytics
Customer Journey Analytics combines qualitative insights and quantitative data to analyze user behavior across digital touchpoints. It identifies where users struggle or disengage. For instance, analyzing drop-offs in an e-commerce checkout process highlights technical or usability issues. Companies like Amazon India and Myntra use this method to refine customer experience. It supports data-driven problem definition by validating assumptions with evidence, ensuring that teams address the most impactful user pain points for optimized innovation outcomes.
-
Problem Framing Canvas
The Problem Framing Canvas helps teams clarify the problem’s context, scope, and significance. It prompts designers to consider who faces the problem, what challenges exist, and why solving it matters. This structured tool prevents teams from jumping to solutions prematurely. Indian innovation hubs and academic institutions use this canvas to train students in structured problem-solving. By visualizing and questioning assumptions, the canvas ensures problem statements are accurate, focused, and capable of driving meaningful design and innovation efforts.