1.2 Define phase

The Define phase is a crucial step in design thinking that focuses on understanding the problem space and user needs. It involves gathering project requirements, conducting user research, and synthesizing findings to create a clear problem statement and project direction.

Key activities in this phase include identifying user needs, setting project goals, and establishing success metrics. User research methods like interviews and surveys are employed to gain insights, which are then synthesized using tools like affinity diagramming and empathy mapping to inform the design process.

Define phase overview

• The define phase is a crucial stage in the design thinking process that focuses on gaining a deep understanding of the problem space and user needs
• Key activities in this phase include gathering project requirements, conducting user research, synthesizing findings, defining the problem statement, and aligning stakeholders
• The define phase sets the foundation for the entire project by clearly articulating the design challenge and establishing the direction for the ideate phase

Key activities in define phase

Gathering project requirements

Top images from around the web for Gathering project requirements

• 

  9. Scope Planning – Project Management – 2nd Edition View original

  Is this image relevant?

• 

  A Principal's Reflections: July 2016 View original

  Is this image relevant?

• 

  Free 3-Year Strategic Plan PowerPoint Template - Free PowerPoint Templates - SlideHunter.com View original

  Is this image relevant?

• 

  9. Scope Planning – Project Management – 2nd Edition View original

  Is this image relevant?

• 

  A Principal's Reflections: July 2016 View original

  Is this image relevant?

1 of 3

Top images from around the web for Gathering project requirements

• 

  9. Scope Planning – Project Management – 2nd Edition View original

  Is this image relevant?

• 

  A Principal's Reflections: July 2016 View original

  Is this image relevant?

• 

  Free 3-Year Strategic Plan PowerPoint Template - Free PowerPoint Templates - SlideHunter.com View original

  Is this image relevant?

• 

  9. Scope Planning – Project Management – 2nd Edition View original

  Is this image relevant?

• 

  A Principal's Reflections: July 2016 View original

  Is this image relevant?

1 of 3

• Involves collecting and documenting the specific needs, goals, and constraints of the project from the client or stakeholders
• Includes understanding the business objectives, target audience, market landscape, and any technical or legal requirements
• Helps establish the project scope and ensures the design solution aligns with the client's expectations

Identifying user needs

• Focuses on gaining a deep empathy for the target users and uncovering their pain points, motivations, and behaviors
• Involves conducting user research through various methods such as interviews, surveys, and observations
• Aims to uncover latent needs and insights that can inform the design solution and ensure it addresses real user problems

Defining problem statement

• Synthesizes the key insights from user research and project requirements into a clear and concise statement that articulates the design challenge
• Frames the problem in a human-centered way, focusing on the user needs rather than jumping to solutions
• Serves as a guiding statement for the entire project and helps keep the team focused on solving the right problem

Setting project goals

• Involves establishing specific, measurable, achievable, relevant, and time-bound (SMART) goals for the project based on the problem statement and client requirements
• Includes defining the desired outcomes, success metrics, and any constraints or limitations that need to be considered
• Helps align the team and stakeholders around a shared vision and provides a clear direction for the design process

Establishing success metrics

• Defines the quantitative and qualitative measures that will be used to evaluate the success of the design solution
• Includes identifying key performance indicators (KPIs) such as user engagement, conversion rates, or customer satisfaction scores
• Helps ensure that the design solution is effective in meeting the project goals and user needs

User research methods

Interviews

• A qualitative research method that involves one-on-one conversations with target users to gain deep insights into their needs, behaviors, and motivations
• Can be conducted in-person, over the phone, or through video conferencing and typically follows a semi-structured format with open-ended questions
• Allows for probing and follow-up questions to uncover rich insights and stories that can inform the design process

Surveys

• A quantitative research method that involves collecting data from a large sample of users through a structured questionnaire
• Can be administered online, in-person, or through mobile devices and typically includes a mix of closed-ended and open-ended questions
• Provides a broad overview of user preferences, attitudes, and behaviors and can help validate or disprove hypotheses

Observations

• A qualitative research method that involves observing users in their natural context to gain insights into their behaviors and interactions
• Can be conducted in-person through field visits or remotely through video recordings or screen sharing
• Helps uncover tacit knowledge and identify pain points or opportunities for improvement that users may not be able to articulate verbally

Focus groups

• A qualitative research method that involves bringing together a small group of target users to discuss a specific topic or product
• Typically moderated by a skilled facilitator who guides the discussion and encourages participation from all members
• Provides a rich source of data on user attitudes, opinions, and reactions to concepts or prototypes and can help identify areas of consensus or disagreement

Synthesizing research findings

Affinity diagramming

• A collaborative process of organizing and clustering research data into themes or patterns to identify key insights and opportunities
• Involves writing individual observations or quotes on sticky notes and grouping them based on similarity or relationship
• Helps the team make sense of large amounts of qualitative data and identify areas for further exploration or ideation

Empathy mapping

• A visual tool for organizing and summarizing user insights into four quadrants: what the user says, thinks, does, and feels
• Helps the team develop a deeper understanding of the user's perspective and identify areas of opportunity or pain points
• Can be used to inform the creation of personas or customer journey maps

Personas

• Fictional characters that represent the key user segments or archetypes based on the research findings
• Typically includes demographic information, goals, motivations, pain points, and behaviors of each persona
• Helps the team keep the user at the center of the design process and make decisions based on their needs and preferences

Customer journey maps

• A visual representation of the user's experience with a product or service over time, from initial awareness to post-purchase evaluation
• Identifies the key touchpoints, actions, emotions, and pain points at each stage of the journey
• Helps the team identify opportunities for improvement and design solutions that address user needs at each stage

Defining design constraints

Technical limitations

• Identifying the technical capabilities and limitations of the platform, system, or technology that the design solution will be built on
• Includes considerations such as device compatibility, performance requirements, security protocols, and integration with existing systems
• Helps ensure that the design solution is feasible and can be implemented within the given technical constraints

Budget considerations

• Determining the available financial resources for the project and how they will be allocated across different phases or deliverables
• Includes identifying any cost constraints or trade-offs that need to be made in order to stay within budget
• Helps ensure that the design solution is economically viable and aligns with the client's financial goals and expectations

Timeline restrictions

• Establishing the overall project timeline and identifying any key milestones, deadlines, or dependencies that need to be considered
• Includes determining the amount of time available for each phase of the design process and any external factors that may impact the schedule
• Helps ensure that the project stays on track and that the design solution can be delivered within the given timeframe

Stakeholder alignment

Identifying key stakeholders

• Determining the individuals or groups who have a vested interest in the project and who will be impacted by the design solution
• Includes both internal stakeholders (project team, executives, other departments) and external stakeholders (users, customers, partners)
• Helps ensure that all relevant perspectives are considered and that the design solution meets the needs and expectations of all stakeholders

Facilitating collaborative workshops

• Bringing together key stakeholders to actively participate in the design process and provide input and feedback at key milestones
• Includes activities such as brainstorming sessions, co-creation workshops, and design reviews
• Helps build consensus and alignment among stakeholders and ensures that the design solution is informed by diverse perspectives and expertise

Gaining consensus on direction

• Facilitating discussions and decision-making processes to ensure that all stakeholders are aligned on the project goals, priorities, and design direction
• Includes presenting research findings, design concepts, and prototypes to stakeholders and incorporating their feedback and input
• Helps ensure that the project moves forward smoothly and that the final design solution has the support and buy-in of all key stakeholders

Design brief creation

Documenting project scope

• Clearly defining the boundaries and limitations of the project, including what is in-scope and out-of-scope
• Includes specifying the target users, use cases, features, and functionality that will be included in the design solution
• Helps ensure that the project stays focused and manageable and that the design team has a clear understanding of what needs to be delivered

Outlining design objectives

• Defining the specific goals and desired outcomes of the design solution, based on the project requirements and user needs
• Includes specifying the key performance indicators (KPIs) and success metrics that will be used to evaluate the effectiveness of the design
• Helps ensure that the design solution is aligned with the project objectives and that the team has a clear target to work towards

Defining deliverables

• Specifying the tangible outputs and artifacts that will be produced as part of the design process, such as wireframes, prototypes, design specifications, and user testing reports
• Includes defining the format, fidelity, and timeline for each deliverable and any dependencies or approvals required
• Helps ensure that the project team and stakeholders have a clear understanding of what will be delivered and when, and that the design process is well-organized and efficient

Best practices for define phase

Asking open-ended questions

• Using open-ended questions in user research and stakeholder interviews to encourage participants to share their thoughts, feelings, and experiences in their own words
• Avoids leading or biased questions that may influence the participant's response or limit the scope of the conversation
• Helps uncover deeper insights and unexpected perspectives that can inform the design process and lead to more innovative solutions

Embracing ambiguity

• Being comfortable with uncertainty and incomplete information, especially in the early stages of the design process
• Avoiding the temptation to jump to conclusions or solutions too quickly, and instead staying open to new ideas and possibilities
• Helps foster a culture of exploration and experimentation, and allows the team to consider a wider range of options and approaches before narrowing down to a specific direction

Iterating problem statement

• Continuously refining and evolving the problem statement based on new insights and feedback gathered throughout the define phase
• Treating the problem statement as a living document that can be updated and improved as the team's understanding of the problem space deepens
• Helps ensure that the design solution remains aligned with the most current and accurate understanding of the user needs and project goals

Common pitfalls to avoid

Jumping to solutions prematurely

• Rushing to generate and evaluate design solutions before fully understanding the problem space and user needs
• Can lead to suboptimal or ineffective solutions that fail to address the root causes or underlying issues
• Emphasizes the importance of spending sufficient time in the define phase to gather and synthesize insights before moving on to ideation and prototyping

Neglecting user perspective

• Failing to prioritize the needs, preferences, and experiences of the target users in the design process
• Can result in solutions that are driven by business goals or technical constraints rather than user-centered insights
• Highlights the importance of conducting thorough user research and keeping the user at the center of all design decisions and trade-offs

Scope creep

• Allowing the project scope to expand beyond the original boundaries and objectives, often due to unmanaged stakeholder requests or shifting priorities
• Can lead to delays, budget overruns, and a loss of focus on the core problem and user needs
• Emphasizes the importance of clearly defining and communicating the project scope upfront, and having a process for managing and prioritizing changes or additions to the scope

Transitioning to ideate phase

Summarizing key insights

• Synthesizing the most important findings and learnings from the define phase into a concise and actionable summary
• Includes highlighting the key user needs, pain points, and opportunities that will inform the ideation process
• Helps ensure that the team has a shared understanding of the problem space and a clear direction for generating and evaluating ideas

Framing design opportunities

• Reframing the problem statement and user needs as opportunities for innovation and value creation
• Includes identifying the key areas where the design solution can make a meaningful impact and differentiate from existing alternatives
• Helps inspire and guide the ideation process by providing a positive and aspirational vision for what the design solution could achieve

Setting stage for brainstorming

• Preparing the team and environment for effective and productive brainstorming sessions in the ideate phase
• Includes selecting appropriate brainstorming techniques, defining the session objectives and ground rules, and gathering any necessary materials or resources
• Helps ensure that the team is ready to generate a wide range of creative and diverse ideas and build on the insights and opportunities identified in the define phase