Feature Usage Report Template for PMs

It depends on the feature's scope. Core features that every user needs should target 70%+ adoption within 90 days. Growth features targeted at a specific segment should target 30-50% of that segment. Niche features (API access, advanced automations) may only need 10-20% adoption to justify their investment, if those adopters are high-value.

If a feature is always on (like a redesigned navigation), measure engagement with the outcome the feature enables rather than the feature itself. For example, if you redesigned search, measure "search queries resulting in a click" rather than "used search." If there is truly no measurable event, the feature may be too subtle to track individually.

Low adoption alone is not a sufficient reason to sunset. Check three things: (1) Do the users who adopt it have high retention and ARPU? If yes, it is a niche feature worth keeping. (2) Does it add complexity that slows development? If yes, the maintenance cost may outweigh the value. (3) Could better discoverability increase adoption? If you have never promoted or onboarded users into the feature, low adoption may reflect awareness, not value.

Monthly for fast-moving products with frequent releases. Quarterly for mature products with less frequent changes. After every major feature launch, produce a focused report for that feature's first 30 and 90 days regardless of the regular cadence.

Create persona-specific views of the feature usage table. A feature like "reporting" might be used weekly by managers and never by individual contributors. Aggregate adoption rates hide this. Segment by role and plan tier at minimum. The [glossary entry on user segmentation](/glossary/prioritization) explains common segmentation approaches. ---