The request
“Create a product adoption hypothesis tree that tests feature awareness, setup friction, recurring workflow value, and the adoption metric.”
Then tryAdd a branch for permission errors.Change setup to an import workflow.
What is in this drawing
Read the decisions behind it.
01Check the metric
Confirm the eligible cohort and event definition.
02Test awareness
Measure whether intended users encounter the feature.
03Observe activation
Watch users complete the first setup.
04Test value
Look for repeat use in the target workflow.
Use during discovery when adoption is low but the cause is not yet established.
More like this
Other examples in this family.
FAQ
Common questions
What is a product adoption hypothesis?
It is a testable explanation for why eligible users do or do not use a feature.
Which evidence should I use?
Combine product events with interviews or observation so behavior and motivation are both covered.
When should the tree change?
Update it whenever evidence rules out a branch or reveals a more precise explanation.