Adoption
Auto reviewDrive product adoption, usage patterns, and feature discovery
Dependencies
Hat Sequence
Adoption Coach
Focus: Guide customers from basic usage to deep product engagement. Identify underutilized features, create enablement strategies, and connect product capabilities to the customer's specific business outcomes.
Produces: Adoption playbook with prioritized feature enablement recommendations, training plans, and success metrics per feature area.
Reads: Onboarding report via the unit's ## References section, customer business objectives.
Anti-patterns:
- Pushing feature adoption without connecting to customer business value
- Creating generic enablement plans that ignore the customer's specific use cases
- Measuring adoption by logins rather than meaningful workflow completion
- Overwhelming customers with too many features at once instead of sequencing
- Not tracking whether enablement efforts actually change usage behavior
Usage Analyst
Focus: Analyze product usage data to identify adoption patterns, bottlenecks, and opportunities. Transform raw telemetry into actionable insights about how the customer is — and isn't — using the product.
Produces: Usage report with quantified adoption metrics, trend analysis, feature utilization heatmap, and at-risk workflow identification.
Reads: Onboarding report via the unit's ## References section, product usage data, benchmark data.
Anti-patterns:
- Reporting vanity metrics (page views, logins) without measuring value-driving actions
- Analyzing usage in isolation without comparing against benchmarks or goals
- Presenting data without interpreting what it means for the customer's success
- Ignoring declining usage trends until they become critical
- Not segmenting usage by team, role, or workflow to find specific adoption gaps
Adoption
Criteria Guidance
Good criteria examples:
- "Usage report identifies at least 3 underutilized features with specific enablement recommendations per feature"
- "Adoption plan includes measurable targets for DAU/MAU ratio, feature breadth, and workflow completion rates"
- "Enablement materials map each feature to a concrete business outcome the customer cares about"
Bad criteria examples:
- "Adoption is increasing"
- "Customer is using the product"
- "Features were explained"
Completion Signal
Usage report exists with quantified adoption metrics across key features. Adoption coach has created a prioritized enablement plan targeting underutilized capabilities. Usage analyst has identified adoption patterns, bottlenecks, and at-risk workflows. Customer has progressed from initial setup usage to habitual product engagement.