Product adoption hypothesis tree
A product adoption hypothesis tree gives a team a structured way to investigate why a feature is not being used. The root is the observed adoption gap. The next branches separate awareness, access, setup and ongoing value so that each can be tested with a suitable source of evidence. Product managers can attach event data, interviews and session recordings to the leaves. This keeps the team focused on learning before committing to redesign, messaging or new functionality.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
A product team investigates low adoption of a newly released feature.
Key decisions
- Check the metric: Confirm the eligible cohort and event definition.
- Test awareness: Measure whether intended users encounter the feature.
- Observe activation: Watch users complete the first setup.
- Test value: Look for repeat use in the target workflow.
When to reuse this
Use during discovery when adoption is low but the cause is not yet established.
Frequently asked questions
What is a product adoption hypothesis?
Which evidence should I use?
When should the tree change?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.