Feature Adoption Tracking

Clear adoption definitions, a dashboard per feature, regular post-launch checkpoints and the fix, promote or retire calls that follow when nobody is using what shipped.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Feature Adoption Tracking, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

🧩 Product Management

Feature Adoption Tracking

Measuring who discovers, tries and keeps using each feature after launch, and acting on features that nobody is adopting.

  1. Feature inventory with owners and launch dates
  2. Written definition of an adopted user per feature
  3. Eligible user base for each feature
  4. Adoption event coverage audit
  5. Discovered, tried and kept funnel stages
  6. Baseline adoption snapshot of the top 20 features
  7. Adoption targets written into every spec
  8. First feature adoption dashboard
  9. Adoption metric glossary for the product team
  10. Weekly adoption review of recent launches
  11. Thirty, sixty and ninety day adoption checkpoints
  12. Monthly feature adoption report for leadership
  13. Quarterly feature portfolio adoption review
  14. Weekly adoption tracking health check
  15. Low adoption watchlist with named owners
  16. Feature owner adoption scorecards
  17. Account-level adoption feed for customer success
  18. Annual feature adoption census
  19. Adoption drop alerts for key features
  20. Cohort analysis for feature retention
  21. Reading feature retention curves
  22. Path and funnel analysis in your analytics tool
  23. Correlation and causation in adoption claims
  24. Interviews with users who never adopted
  25. Session replay review of first use
  26. Writing adoption insights people act on
  27. Discoverability audit of feature entry points
  28. In-app guide for an under-adopted feature
  29. Fix, promote or retire decision for low adopters
  30. Choosing a feature adoption analytics tool
  31. First-use empty state redesign for one feature
  32. Holdout test for an adoption nudge
  33. Breadth versus depth as the headline measure
  34. Default on or opt in for new features
  35. Shorter time to first use of a key feature
  36. Adoption readiness check before a launch
  37. Ninety day adoption retrospective for a launch
  38. Adoption slides for a key account review
  39. Adoption readout at the planning offsite
  40. First 90 days inheriting a feature area
  41. Manager's adoption expectations for the team
  42. Spreadsheet adoption tracking for a small team
  43. Account versus user adoption in B2B products
  44. Adoption after a redesign or migration
  45. Adoption of features in paid plans
  46. Estimating the retention impact of a feature
  47. Feature co-adoption and sequence map
  48. Maintenance cost per adopted user
  49. Internal adoption benchmarks by feature type
  50. Feature adoption signals in churn and expansion

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Feature inventory with owners and launch dates

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most products have more features than anyone can list from memory, and adoption cannot be tracked for features nobody has written down. A single inventory with each feature's owner, launch date, plan availability and the event that shows it being used is the spine every later report hangs from.

First tasks

  • List the features in the main navigation and settings in a spreadsheet
  • Add owner, launch month and plan availability for each feature
  • Match each feature to the event that shows it being used
  • Add features shipped in the last month to the inventory @recurring(monthly:5)

Written definition of an adopted user per feature

Clicking a button once is not adoption, yet many dashboards count it that way and every feature looks like a success. Writing down, per feature, what counts as adopted (for example, used on three separate days within 30 days) turns arguments about whether a feature landed into a lookup.

First tasks

  • Draft a default rule such as three days of use within 30 days
  • Mark features whose natural frequency is monthly or rarer
  • Write a specific rule for each exception with its own window
  • Review the definitions with the product lead and record approval

Eligible user base for each feature

An adoption rate is only as honest as its denominator: dividing users of an admin-only feature by all users makes it look like a failure. Defining who could actually use each feature, by plan, role, platform and permission, keeps rates comparable and stops good features being cut for the wrong reason.

First tasks

  • Note which plans, roles and platforms can see each feature
  • Build a saved segment for the eligible users of the top ten features
  • Recalculate adoption for those features against the eligible base
  • Recheck eligibility rules when plans or permissions change @recurring(quarterly)

Make it yours.

Install Feature Adoption Tracking, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.