Adoption

Auto review

Drive product adoption, usage patterns, and feature discovery

Hats
2
Review Agents
1
Review
Auto
Unit Types
Adoption, Enablement
Inputs
Onboarding

Dependencies

Onboardingonboarding-report

Hat Sequence

1

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 (RFC 2119):

  • The agent MUST NOT push feature adoption without connecting to customer business value
  • The agent MUST NOT create generic enablement plans that ignore the customer's specific use cases
  • The agent MUST NOT measure adoption by logins rather than meaningful workflow completion
  • The agent MUST NOT overwhelm customers with too many features at once instead of sequencing
  • The agent MUST track whether enablement efforts actually change usage behavior
2

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 (RFC 2119):

  • The agent MUST NOT report vanity metrics (page views, logins) without measuring value-driving actions
  • The agent MUST NOT analyze usage in isolation without comparing against benchmarks or goals
  • The agent MUST NOT present data without interpreting what it means for the customer's success
  • The agent MUST NOT ignore declining usage trends until they become critical
  • The agent MUST segment usage by team, role, or workflow to find specific adoption gaps

Review Agents

Effectiveness

Mandate: The agent MUST verify adoption strategies are evidence-based and measurable.

Check:

  • The agent MUST verify that usage metrics are defined and tracked against targets
  • The agent MUST verify that feature discovery recommendations are prioritized by customer value, not product roadmap
  • The agent MUST verify that adoption blockers are identified with specific remediation actions
  • The agent MUST verify that success is measured by customer outcomes, not just login frequency

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 (RFC 2119)

Usage report MUST exist with quantified adoption metrics across key features. Adoption coach MUST have created a prioritized enablement plan targeting underutilized capabilities. Usage analyst MUST have identified adoption patterns, bottlenecks, and at-risk workflows. Customer MUST have progressed from initial setup usage to habitual product engagement.