1.2 Define phase
9 min read•august 20, 2024
The is a crucial step in design thinking that focuses on understanding the problem space and user needs. It involves gathering project requirements, conducting , and synthesizing findings to create a clear and project direction.
Key activities in this phase include identifying user needs, setting , and establishing . User research methods like and are employed to gain insights, which are then synthesized using tools like and 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
- 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
- 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
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
Key Terms to Review (29)
Affinity Diagramming: Affinity diagramming is a collaborative visual technique used to organize and categorize ideas or data based on their natural relationships. It helps teams synthesize large amounts of information, facilitating better understanding and decision-making in the early stages of design processes.
Budget considerations: Budget considerations refer to the financial planning and evaluation process that takes into account the costs associated with a project or initiative. This involves assessing available resources, estimating expenses, and ensuring that expenditures align with the overall financial goals and constraints of an organization. Effective budget considerations are crucial for informed decision-making and resource allocation throughout various phases of a project.
Collaborative Workshops: Collaborative workshops are structured group sessions where participants come together to brainstorm, share ideas, and solve problems collaboratively. These workshops facilitate engagement, allowing diverse perspectives to merge, leading to innovative solutions and stronger team dynamics. This approach is essential in the Define phase, where understanding user needs and defining the problem is crucial for effective design strategy.
Customer Journey Maps: Customer journey maps are visual representations that outline the steps and interactions a customer experiences while engaging with a product or service. These maps help businesses understand customer needs, emotions, and pain points throughout their journey, providing insights for improving overall customer experience and identifying opportunities for enhancement.
Define Phase: The Define Phase is a crucial part of the design thinking process where problems are clearly articulated, and the needs of users are identified. It serves as the foundation for developing insights into user experiences, ensuring that the design solutions created address real issues and fulfill user expectations. This phase emphasizes collaboration among team members to refine ideas and create a shared understanding of the problem space before moving on to ideation and prototyping.
Defining Deliverables: Defining deliverables involves clearly outlining the specific outcomes or outputs that are expected from a project or phase within a process. It sets the expectations for what needs to be produced, ensuring all stakeholders have a common understanding of the objectives and requirements. This clarity helps guide the team throughout the project and serves as a basis for measuring success upon completion.
Design Brief: A design brief is a written document that outlines the objectives, scope, and constraints of a design project. It serves as a roadmap for designers, providing essential information that guides the creative process and ensures that the project aligns with the client's needs and expectations. A well-crafted design brief facilitates communication between stakeholders and sets clear goals for what the project aims to achieve.
Documenting Project Scope: Documenting project scope is the process of clearly defining and recording the boundaries, objectives, deliverables, and constraints of a project. This documentation serves as a foundation for planning and execution, ensuring that all stakeholders have a shared understanding of what the project entails and what it aims to achieve.
Embracing Ambiguity: Embracing ambiguity is the practice of accepting uncertainty and complexity in situations, especially when designing or strategizing. This approach allows individuals to remain open-minded, fostering creativity and innovation while navigating through unclear or unpredictable scenarios. It encourages flexibility in thinking, enabling one to explore multiple perspectives and solutions without the pressure of needing immediate clarity or definitive answers.
Empathy Mapping: Empathy mapping is a visual tool used to gain deeper insights into users by capturing their thoughts, feelings, behaviors, and needs. This tool helps teams align their understanding of users and their experiences, making it easier to create solutions that resonate with them. By synthesizing user research, empathy mapping connects various aspects of the design process, fostering a more user-centered approach in creating effective products or services.
Focus Groups: Focus groups are structured discussions involving a small group of participants, guided by a facilitator, aimed at gathering insights and opinions about a specific topic, product, or service. These sessions help designers and researchers understand user needs, preferences, and attitudes, which are crucial for informing design decisions and strategies. By encouraging dialogue among participants, focus groups can reveal nuanced insights that may not surface in individual interviews.
Interviews: Interviews are a qualitative research method used to gather in-depth insights from individuals through direct conversation. This method allows for exploring user experiences, preferences, and motivations, making it an essential tool during various stages of design processes like defining user needs, understanding personas, and obtaining feedback.
Iterating Problem Statement: Iterating problem statement refers to the process of refining and revising a problem statement through multiple cycles of feedback and analysis. This practice is essential for ensuring that the defined problem accurately reflects the users' needs and the context in which it exists, leading to more effective solutions. Iteration allows teams to adjust their focus based on insights gained during exploration, fostering a deeper understanding of the issue at hand.
Jumping to Solutions Prematurely: Jumping to solutions prematurely refers to the tendency to hastily propose answers or fixes before fully understanding the problem at hand. This approach often leads to ineffective solutions because critical insights and context may be overlooked during the problem-solving process, which can hinder creativity and lead to wasted resources.
Neglecting user perspective: Neglecting user perspective refers to the failure to consider the needs, experiences, and viewpoints of users during the design and development process. This oversight can lead to products or services that do not meet user expectations, ultimately impacting usability and satisfaction. Prioritizing user feedback is essential for creating solutions that truly resonate with the intended audience, as understanding their context can drive better outcomes.
Observations: Observations are the act of carefully watching and noting behaviors, actions, and interactions in a specific environment. This process is essential for gathering insights and understanding user experiences or needs, often leading to the identification of problems or opportunities for design solutions.
Open-ended questions: Open-ended questions are inquiries that cannot be answered with a simple 'yes' or 'no'; instead, they encourage detailed responses and allow for a wide range of answers. This type of questioning is especially useful for gathering qualitative data, as it promotes deeper understanding and insight into the thoughts and feelings of respondents. By using open-ended questions, researchers can uncover new ideas, perspectives, and complex opinions that might be missed with closed-ended questions.
Outlining Design Objectives: Outlining design objectives involves clearly defining the goals and purposes that a design project aims to achieve. This process helps in establishing a direction for the design efforts, ensuring that all stakeholders have a shared understanding of what needs to be accomplished. It sets the foundation for evaluating the success of the design and guides decision-making throughout the project lifecycle.
Problem Statement: A problem statement is a clear and concise description of an issue that needs to be addressed. It articulates the gap between the current situation and the desired outcome, guiding the design process by focusing on the core challenges faced. This statement helps to ensure that all stakeholders have a common understanding of the problem at hand, and it serves as a foundation for generating ideas and solutions.
Project goals: Project goals are specific, measurable objectives that a project aims to achieve within a defined timeframe. These goals guide the project team in their decision-making and help ensure that everyone is aligned on the desired outcomes, providing a clear focus for their efforts and resources.
Scope Creep: Scope creep refers to the gradual expansion or change of a project's scope, often without proper approval or adjustments to resources, timelines, and budgets. It commonly occurs when new features, tasks, or requirements are added after the project has already started, leading to potential delays and increased costs. Understanding scope creep is crucial for maintaining project integrity and ensuring successful collaboration between teams throughout the design and development process.
Stakeholder Alignment: Stakeholder alignment refers to the process of ensuring that all parties involved in a project, including users, clients, team members, and other relevant stakeholders, share a common understanding and agreement on project goals, expectations, and roles. This alignment is crucial for facilitating effective communication, reducing conflicts, and enhancing collaboration throughout the project lifecycle.
Success metrics: Success metrics are specific measures used to evaluate the effectiveness of a product, service, or design in meeting predetermined goals. They help teams determine whether they are achieving their objectives and provide insight into areas for improvement. By aligning these metrics with business goals, organizations can ensure that their design strategies are not only user-centered but also contribute to overall success and sustainability.
Surveys: Surveys are systematic methods of gathering information from individuals, often through questionnaires or interviews, to understand their opinions, behaviors, or experiences. They serve as a critical tool for collecting data during various phases of design and research processes, enabling teams to make informed decisions based on user insights.
Technical Limitations: Technical limitations refer to the constraints or restrictions that arise from the capabilities and performance of technology, tools, or systems. These limitations can affect the design, functionality, and implementation of solutions, influencing decision-making and problem-solving processes. Understanding these constraints is crucial for identifying feasible solutions and ensuring successful outcomes in various projects.
Timeline restrictions: Timeline restrictions refer to the limitations placed on the duration and scheduling of activities or projects during the design and development process. These restrictions often dictate when specific tasks must be completed, influencing project milestones, deadlines, and resource allocation, thereby impacting overall workflow and project success.
Transitioning to Ideate Phase: Transitioning to the ideate phase refers to the shift in a design process where teams move from defining the problem and understanding user needs to generating ideas and potential solutions. This phase emphasizes creative thinking, brainstorming, and exploring various concepts without immediate judgment, enabling innovative solutions to emerge. The transition is crucial as it sets the stage for idea development, ensuring that insights gained during the define phase inform and inspire the ideation efforts.
User Personas: User personas are fictional, detailed representations of target users based on research and data, created to help designers and teams understand their audience's needs, behaviors, and motivations. These personas synthesize user insights gathered through interviews, surveys, and observations, serving as a reference throughout the design process to ensure that products meet the specific requirements of different user segments.
User Research: User research is the systematic process of gathering insights and understanding the needs, behaviors, and motivations of users through various methods. It helps in identifying pain points and opportunities for design improvements, ensuring that products or services are developed with the user in mind. By incorporating user feedback, this process directly influences design decisions, leading to more effective and user-centered solutions.