3.2 Define
This is where you make sense of what you've learned and pinpoint the real problem you want to solve. You'll challenge your assumptions and set a clear direction for your project.
Take your time with this phase. A well-defined problem makes it much easier to find good solutions.
tip
Try using diagrams or mind maps to organize your thoughts. It can help you see connections and explain your ideas to others.
Key activities:
- Synthesize research
- Collate and analyze all data and insights from the Explore phase
- Identify key themes, patterns, and contradictions in your findings
- Define the problem statement
- Articulate the core problem clearly and concisely
- Ensure the problem statement reflects user needs and community context
- Challenge assumptions
- Critically examine existing beliefs about the problem and potential solutions
- Encourage diverse perspectives to uncover hidden biases or oversights
- Identify success criteria
- Define what success looks like for your project
- Establish measurable goals and outcomes
- Prioritize focus areas
- Determine which aspects of the problem to address first
- Consider factors like impact, feasibility, and resource availability
- Create a design brief
- Document your problem statement, target users, goals, and constraints
- Use this brief to guide your team in the subsequent Create phase
- Align stakeholders
- Present your reframed problem and approach to key stakeholders
- Ensure buy-in and shared understanding before moving forward
Resources to help:
- "How to Define a Problem Statement": https://www.nngroup.com/articles/problem-statements/
- https://www.gov.uk/service-manual/agile-delivery/how-the-alpha-phase-works
- https://www.ontario.ca/page/service-design-playbook#section-2
- https://www.designcouncil.org.uk/our-resources/archive/articles/design-methods-step-2-define
- An example design brief?
- OKRs