DT Session 3 - Define Design Thinking PDF

Module 1: Design Thinking – Session 3 September 25, 2024 – October 16, 2024 Rama Maher  Session 3 Agenda Phase 2: Define - Activities of the Conducting Quiz Roses and thorns Introduction Day - Overview Phase 2...

Module 1: Design Thinking – Session 3 September 25, 2024 – October 16, 2024 Rama Maher  Session 3 Agenda Phase 2: Define - Activities of the Conducting Quiz Roses and thorns Introduction Day - Overview Phase 2 Activities: POV/Problem statement 5 Whys How Might We Statement Design thinking is a human- centered approach to problem-solving that involves understanding user User Interviews Empathy Maps needs, redefining problems, and Understand creating innovative solutions through users and their Personas iterative processes. needs through Journey Maps observation, 1 interaction, and immersion Empathize POV Statements 5 Whys Synthesize the 2 5 Test prototypes with Observational studies HMW statement findings from the Define Test users, gather Interviews empathize phase feedback, and into a clear problem Surveys and Questionnaires refine the statement solution Usability Testing 3 4 Ideate Prototype Generate a wide Brainstorming range of ideas Mind Mapping and potential Dot Voting solutions SCAMPER Create tangible Paper Prototyping Impact Effort Matrix representations of Wireframes ideas to explore and evaluate them 3D Prototyping Interactive prototypes Phase 2: Define - Introduction Define Phase - Introduction The Define phase involves synthesizing the information generated from the empathize phase into a clear and actionable problem statement or Point of View (POV) and guide the ideation process. It sets the foundation and defines the focus for the subsequent stages, while ensuring that the solutions generated later are based on real user needs rather than assumptions. It guides creativity by clearly defining the problem, as it provides a launch pad for brainstorming and creative thinking during the Ideate phase. Activities of the Day Define Phase Activities - Overview Point of View (POV) statement: a Affinity Diagrams: are used to sort user-centered problem statement and organize the large amounts of that captures the essence of who qualitative data gathered during the the user is, their core need, and the Empathize phase into meaningful insights derived about their categories or themes, to uncover challenges or frustrations, to patterns and relationships between humanize the problem and put the user insights. focus 0n their perspective. 5 Whys analysis: a tool used to How Might We (HMW) questions: deeply understand the root cause of are used to reframe the problem a problem by repeatedly asking into a challenge that opens the door "why" about the issue or challenge to brainstorming solutions, through to be solved, to uncover the short, actionable prompts that underlying reasons behind a user’s encourage creativity and needs, frustrations, or behaviors, to exploration of possibilities without address the core problem rather being too prescriptive. than just its symptoms. Tool 1: Point of View (POV) statement Purpose: POV statements help frame the problem from the user's perspective, focusing on who they are and what they need, ensuring the design process remains user-centered and focused on addressing real challenges. POV Structure: User: Describe the specific user (e.g., "Busy college students..."). Need: Highlight the user’s key need or problem (e.g., "...need a way to manage their time effectively..."). Insight: Provide an insight that explains the deeper motivation or context behind the need (e.g., "...because they are overwhelmed by balancing academics and social life, which leads to stress and missed deadlines"). Example: "Busy college students (user) need a way to manage their time more effectively (need) because they feel overwhelmed by the number of assignments and extracurricular activities, leading to burnout and missed deadlines (insight)." Tool 1: Point of View (POV) statement Components of a Strong Problem Statement: Specificity: It addresses a specific user group and problem, not a vague or overly general issue. Actionability: It is framed in a way that invites possible solutions. User-Centered: The problem statement should be focused on what the user needs, not what the design team wants to achieve. Context: It should provide enough background to understand the user’s context and why this is a pressing issue.  Tool 2: 5 Whys Analysis The 5 Whys analysis helps the design team refine their Point of View (POV) statement, ensuring it’s based on the actual root of the user's problem. This prevents teams from jumping to conclusions or addressing symptoms. Steps for Conducting the 5 Whys Analysis: Start with a Problem Statement: Begin by identifying the initial problem or challenge. This should be a specific issue or observation that was uncovered during the Empathize phase. Ex: students are having difficulty managing their academic workload. Ask "Why": Ask why this problem occurs, and for each answer, ask "why" again. This continues until you reach the root cause, usually after asking "why" five times, though it can be more or less depending on the complexity of the problem. Repeat Until You Reach the Root Cause: Each "why" question helps dig deeper into the issue, leading to more insights about the problem’s real causes.  5 Whys Analysis - Example Problem: Students are struggling to submit assignments on time. 1. Why are students struggling to submit assignments on time? - Because they are overwhelmed by the number of assignments and deadlines. 2. Why are they overwhelmed by the number of assignments and deadlines? - Because they don’t have an effective way to manage their time and prioritize tasks. 3. Why don’t they have an effective way to manage their time? - Because they aren’t using tools or methods that help them track and organize their workload efficiently. 4. Why aren’t they using effective tools or methods? - Because the current tools available are either too complex, not user-friendly, or they are unaware of better options. 5. Why are the current tools too complex or not user-friendly? - Because many time-management tools are designed with professionals in mind, not tailored to the specific needs of students. Outcome: By going through this process, the design team realizes that the root cause of the problem isn’t just time management, but rather that students don’t have access to simple, student-friendly tools that help them manage their workload effectively. Instead of just addressing surface issues like deadlines, the team can focus on designing a more intuitive tool tailored to student needs. Activity 1: Conduct your 5 Whys Analysis 1 2 3 Take 5 minutes to Use your problem Hand it in in paper come up with a statement to form with your POV statement conduct the 5 name, ID and Whys analysis in 10 section number minutes Tool 3: How Might We Questions How Might We (HMW) questions transform challenges and insights from the empathize phase into opportunities for ideation. These questions are designed to spark creativity and guide the brainstorming process, encouraging the team to think of potential solutions without being too restrictive or prescriptive. Purpose of "How Might We" Questions: Frame the Problem as an Opportunity: Instead of focusing on the constraints or limitations of a problem, HMW questions focus on how to solve it creatively and innovatively. Inspire Ideation: HMW questions serve as prompts that open up multiple possibilities for solutions, rather than leading to a single "correct" answer. Encourage Collaboration: These questions create a sense of shared exploration among team members, fostering collaboration and open dialogue. Tool 3: How Might We Questions How to Create Effective "How Might We" Questions, with reference to the problem statement: Ensure the Question is Broad, Yet Focused: A good HMW question is broad enough to allow for diverse solutions but focused enough to remain relevant to the user’s needs. For example, "How might we improve student learning?" is too broad, while "How might we create an app that helps students remember deadlines?" may be too specific. Encourage Exploration of Multiple Solutions: The wording should encourage teams to consider different approaches and solutions. It should be open-ended, allowing for a variety of creative responses. Balance Constraints and Opportunities: An HMW question should acknowledge the challenge but focus on the opportunity for improvement or innovation. Tool 3: How Might We Questions Example: In the context of students struggling to meet assignment deadlines, a possible HMW question could be: "How might we help students stay on top of their deadlines in a way that feels manageable and stress-free?“ This question frames the problem (students missing deadlines) in a way that focuses on the user’s emotional experience (feeling overwhelmed), while also hinting at the kind of solution (manageable and stress-free). Questions?