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)