diverge · Ideation · 30–60 min · 3-12 people · medium energy
Hypothesis Generation
Hypothesis Generation is a collaborative exercise to surface and document existing assumptions and insights about user needs and behaviors. It helps teams align on a shared understanding and generate initial ideas for service improvements or new features.
When to use Hypothesis Generation
Use this method at the beginning of a project or design sprint to leverage existing knowledge, identify knowledge gaps, and create a foundation for further research and ideation.
What it solves
Lack of shared understanding among team members regarding user needs and potential solutions; jumping to solutions without a solid foundation of knowledge.
How to run Hypothesis Generation, step by step
- (5 min) Briefly introduce the concept of hypothesis generation and its purpose in the project.
- (15 min) Individually, have each participant write down their assumptions and insights related to user needs and behaviors on sticky notes (one idea per note).
- (20 min) Facilitate a group discussion where participants share their hypotheses, clustering similar ideas and identifying any conflicting viewpoints.
- (10 min) As a group, refine and prioritize the hypotheses, focusing on those that are most critical to the project's success.
Materials needed
- Sticky notes
- Markers
- Whiteboard or large paper
- Timer
- Optional: Pre-printed hypothesis template
Facilitator tips
- Encourage participants to be specific and avoid vague statements.
- Create a safe space for sharing ideas, emphasizing that there are no wrong answers.
- Actively listen and summarize key points to ensure everyone is on the same page.
Common pitfalls
- Participants may be hesitant to share their assumptions due to fear of being wrong. Emphasize that the goal is to learn and improve.
- The discussion may become dominated by a few individuals. Actively solicit input from quieter participants.
Variations
- Use a 'How Might We' format to frame the hypotheses as opportunities for innovation.
- Conduct a 'Fact vs. Assumption' exercise to differentiate between verified information and educated guesses.
Running it online or hybrid
Use a shared digital whiteboard like Miro or Mural to capture hypotheses. Encourage participants to use virtual sticky notes.
What it produces
A collection of documented hypotheses about user needs, behaviors, and potential service solutions.
Origin
Adapted from Service Design Tools — source
Build a session around Hypothesis Generation
METODIC places Hypothesis Generation inside a complete, timed session plan — agenda, worksheets, facilitator guide and slides — matched to your group and goal.
Generate a session with Hypothesis Generation · Try METODIC free