Introduction to the Define Stage and Research Synthesis

The Define stage is a pivotal phase in the Design Thinking process, serving as the bridge between understanding user needs and generating innovative solutions. It's where we synthesize the vast amounts of information gathered during the Empathize stage to pinpoint the real problem that needs solving.

1. The Role and Importance of the Define Stage

The Define stage is often called the 'problem definition' stage because it's precisely where the core challenge is identified, framed, and articulated. This stage is crucial for several reasons:

Provides Focus and Clarity: It ensures the design team has a shared, clear understanding of the specific problem they are addressing. Without this, efforts can become fragmented and misdirected.
Places People at the Center: By synthesizing user research, the team gains profound insights into users' pain points, desires, and motivations, keeping the human element at the forefront of the design challenge.
Improves Alignment and Collaboration: Involving stakeholders and fostering team alignment on the problem statement facilitates smoother collaboration and ensures everyone is working towards a common goal. This reduces roadblocks later in the process.
Serves as a Springboard for Innovation: A precisely defined problem statement acts as a powerful catalyst for the Ideate stage, leading to more targeted, relevant, and innovative solutions. The more accurate the definition, the more effective subsequent phases become.

During this stage, we transition from observing and understanding to making sense of our observations, analyzing patterns in user behavior, uncovering underlying problems, and synthesizing everything into coherent themes and insights.

2. Understanding Research Synthesis

Research synthesis is the analytical process of organizing, interpreting, and consolidating the qualitative and quantitative data collected during the Empathize phase. Its purpose is to convert raw data into actionable insights that directly guide the design process.

The synthesis process typically involves three key stages:

Learnings: This initial stage is about capturing the essence of what stood out during user engagement. It's a collection of raw observations, feelings, quotes, and thoughts that directly emerge from interacting with users and their environments.
Themes: Once learnings are captured, the next step is to organize them into coherent themes. This involves clustering similar observations and insights, helping to identify broader patterns, common challenges, and areas of interest that warrant deeper exploration.
Insights: The culmination of synthesis is the formation of insights. These are the profound realizations that emerge from critically analyzing the themes. An insight is an unexpected discovery or a deep understanding of human behavior, needs, or motivations that can inspire design solutions. It often explains why a particular theme exists or what its implications are.

2.1 Tools for Organizing Research Findings

Designers utilize various tools to collect, organize, and make sense of research data, facilitating the connection of dots and the development of new insights. These include:

Mind Maps: Visual tools for organizing information hierarchically and associatively around a central concept.
Fishbone Diagrams (Ishikawa Diagrams): Used for root cause analysis, categorizing potential causes of a problem to identify its underlying factors.
Affinity Diagrams: A method for organizing a large number of ideas or insights into logical groups based on their natural relationships.
Entity Diagrams: Often used in software engineering, but conceptually can help map relationships between different user types, tasks, and problems.
5 Whys: A questioning technique used to explore the cause-and-effect relationships underlying a particular problem (discussed in detail below).

2.2 Illustrative C++ Example: Basic Data Categorization

While design thinking is primarily qualitative, large-scale user feedback can involve structured data. Here's a simple C++ program illustrating how initial raw feedback might be programmatically categorized to reveal emerging themes, a preliminary step in synthesis. This helps us count occurrences of keywords related to potential user needs or pain points.

3. Crafting a Meaningful Problem Statement

A problem statement is a clear, concise articulation of the gap between the current state (the problem) and the desired state (the goal) of a process or product. It identifies the challenge in a way that is actionable for designers. Without a well-defined problem statement, design efforts can lack focus, and the final solution may not effectively address user needs.

3.1 What Makes a Good Problem Statement?

A strong problem statement drives innovation and provides clear direction:

Human-Centered and User-Focused: The user and their needs must be at the core. Avoid statements that start with "we need to..." or "the product should..." Instead, focus on the user's perspective, e.g., "Young working professionals need...".
Broad Enough for Innovation: It should leave room for a wide range of creative solutions. Avoid references to specific solutions or technical requirements, which can prematurely limit ideation.
Manageable and Actionable: While broad, it must also be specific enough to guide the team without being overwhelming. Prioritize and focus on a specific set of user needs rather than trying to solve everything at once.

3.2 Framing Your Design Problem

Problem statements can be framed in various ways, often drawing from user research:

From the User's Perspective: Directly captures the user's voice and experience. Example: "I am a young working professional trying to eat healthily, but I’m struggling because I work long hours and don’t always have time to go grocery shopping and prepare my meals. This makes me feel frustrated and bad about myself.”
From a User Research Perspective: Translates user observations into a concise need. Example: "Busy working professionals need an easy, time-efficient way to eat healthily because they often work long hours and don’t have time to shop and meal prep.”
Based on the Four Ws (Who, What, Where, Why): This structured approach ensures key contextual elements are included. Example: "Our young working professional struggles to eat healthily during the week because she is working long hours. Our solution should deliver a quick and easy way for her to procure ingredients and prepare healthy meals that she can take to work.”

The "Why does it matter?" aspect often relates to the impact of solving the problem. We can conceptualize this impact as a function of the benefit provided and the reach of the solution:

\text{Impact} = \text{Benefit} \times \text{Reach}

A high impact solution would provide significant benefit to a large number of users.

4. Techniques for Deeper Problem Understanding

To write a meaningful problem statement, several techniques help synthesize research and drill down to the core issue:

4.1 Space Saturation and Grouping

This method involves collecting and visually presenting all observations, notes, photos, and ideas from the Empathize phase in one physical or digital space (e.g., a wall, whiteboard, or digital canvas). By arranging and grouping these findings, teams can explore emerging themes, patterns, and ultimately identify meaningful needs and insights that will inform design solutions.

4.2 The Four Ws (Who, What, Where, Why)

Asking the right questions helps articulate the problem statement clearly:

Who is experiencing the problem? (Target user)
What is the problem? (Pain points, tasks the user is trying to accomplish, obstacles)
Where does the problem present itself? (Physical or digital space, situation, context)
Why does it matter? (Importance of solving it, value to user/business)

4.3 The Five Whys Technique

The Five Whys technique is a powerful root cause analysis tool. By repeatedly asking "Why?" (typically five times, though it can be more or less), you can delve deeper into a problem and identify its underlying cause, rather than just addressing surface-level symptoms.

Let's revisit the example of the young working professional:

Problem: Young working professional is not eating healthily.

Why is she not eating healthily? → She orders takeaway everyday.
Why does she order takeaway everyday? → Her fridge and cupboards are empty.
Why are the fridge and cupboards empty? → She hasn’t been grocery shopping in over a week.
Why hasn’t she been grocery shopping? → She doesn’t have time to go to the supermarket.
Why doesn’t she have time? → She works long hours and is exhausted.

Root Cause: Long working hours leading to exhaustion and lack of time for grocery shopping.

This technique helps shift the focus from the symptom (not eating healthily) to the root cause (lack of time due to long hours and exhaustion), which is a more fundamental problem for designers to address.

5. Developing Point-of-View (POV) Statements

A Point-of-View (POV) statement is a re-framed problem statement that clearly articulates the problem (or need) that needs to be solved, always with the end-user in mind. Its purpose is to define and formulate the right tasks, focusing solely on the target audience, their needs, and the insights gained. You may create multiple POVs depending on the insights from your research.

The three key components of a POV statement are:

User: A descriptive term for the specific user for whom you are designing.
Need: An essential, verb-based statement of what the user is trying to achieve.
Surprising Insight: A compelling realization from your research that explains why the need exists or is important.

The typical format for a POV statement is:

[User... (descriptive)] needs [need... (verb)] because [insight... (compelling)]

Example: A financial advisor needs a way to have meaningful conversations with more clients because business grows through genuine conversation with clients –not through paperwork.

5.1 Steps for Creating a POV Statement

Identify Users, Needs & Insights: Synthesize your research to define your user(s), pinpoint their essential needs (using verbs to make them actionable), and uncover surprising insights.
Create Your Chart/Template: Use a template to structure your thoughts, ensuring all three components are addressed.
Form Your POV Statement: Combine your user, need, and insight into a concise, well-crafted statement. Condense and refine for clarity and impact.
Manageable Scope: Ensure the POV has enough guidance and constraints to make the project manageable. It should not be too narrowly focused on a specific solution nor too broadly focused to feel overwhelming.

6. Formulating How Might We (HMW) Questions

Once you have a well-defined POV statement, the next step is to reframe it into "How Might We…?" (HMW) questions. These are open-ended, actionable questions that challenge assumptions and inspire a wide range of potential solutions. HMW questions serve as a springboard for the Ideate stage.

Example (from the financial advisor POV):

How might we speed up the time the advisor spends with clients?
How might we increase the amount of meaningful conversations the advisor has?
In what ways might we reduce the time it takes to do paperwork?

6.1 Steps to Create HMW Questions

Clearly Define the Problem: Start with your finalized POV statement.
Break Down the Problem Statement: Identify the key components (user, need, insight) and consider different aspects to question.
Add a Provocative Element: Use words like "might," "could," "what if" to encourage creative and fresh thinking.
Generate Several HMW Questions: Vary the action verbs, subjects, and provocative elements to explore different angles.
Review and Prioritize: Assess HMW questions based on their relevance, potential impact, and breadth of solution space.
Test and Iterate: Share HMW questions with your design team or stakeholders for feedback. Refine them based on new insights. Explore variations like "In what ways might we..." or "What's stopping us from...".
Develop Follow-up Questions: Create secondary questions to deepen understanding and guide the ideation process further.
Iterative Process: Creating effective HMW questions is iterative; repeat steps as needed until you have a strong set.

Example: Rural Community Plastic Waste

Problem statement (from previous stage): A village community needs to decrease their use of single-use plastics and find better alternatives because it negatively impacts their environment.
HMW Questions:
- How might we encourage community members to adopt reusable alternatives for everyday items like bags and containers?
- How might we collaborate with local businesses to reduce the use of single-use plastic in packaging?
- How might we make sustainable alternatives more accessible and affordable for a diverse range of community members?
Variations of HMW Questions (exploring different angles):
- What's stopping us from implementing a community-wide education campaign on the environmental consequences of single-use plastic?
- What would happen if we introduced incentives for businesses and individuals to actively participate in plastic recycling initiatives?
- In what ways might community members be motivated to participate in a neighborhood clean-up event focused on plastic waste?

Summary

The Define stage is crucial for problem identification and framing in Design Thinking, providing focus and aligning teams.
Research Synthesis transforms raw data into learnings, themes, and actionable insights.
A Problem Statement defines the gap between the current and desired state, guiding design efforts.
Good problem statements are human-centered, broad, and manageable.
Techniques like Space Saturation, the Four Ws, and the Five Whys help deepen understanding of the problem's root causes.
Point-of-View (POV) Statements consolidate user, need, and insight into an actionable problem definition.
How Might We (HMW) Questions reframe POV statements into open-ended questions to spark ideation and encourage innovative solutions.

Assessed progress

Introduction to the Define Stage and Research Synthesis

Introduction to the Define Stage and Research Synthesis

1. The Role and Importance of the Define Stage

2. Understanding Research Synthesis

2.1 Tools for Organizing Research Findings

2.2 Illustrative C++ Example: Basic Data Categorization

3. Crafting a Meaningful Problem Statement

3.1 What Makes a Good Problem Statement?

3.2 Framing Your Design Problem

4. Techniques for Deeper Problem Understanding

4.1 Space Saturation and Grouping

4.2 The Four Ws (Who, What, Where, Why)

4.3 The Five Whys Technique

5. Developing Point-of-View (POV) Statements

5.1 Steps for Creating a POV Statement

6. Formulating How Might We (HMW) Questions

6.1 Steps to Create HMW Questions

Summary

Key Concepts

Define Stage

Research Synthesis

Problem Statement

Point-of-View (POV) Statement

How Might We (HMW) Questions

Quick Check

Design Thinking

Design Thinking