Feature Adoption Agent
Tracks uptake of new features and flags gaps.
- Industry
- IT Company
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Investigator
- Approver
- Head of Product
- Code
- PRD-10
It tracks uptake of new features across client tenants and explains where adoption falls short: admins not enabling it, users not finding it, a permission or integration blocker, or a value gap. It records the finding against the feature and proposes the fix, from in-app guidance to a change in default settings. **The problem it solves:** Why a new feature is not being adopted: by how much it is short, in which segments, and whether enablement, discovery, blockers, value or a defect explains it.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the subscription billing system: tenants and eligible users by plan, with feature enablement and usage events from the cloud monitoring and observability stack..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Head of Product with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it records the adoption finding on the feature and opens the follow-up tasks. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The feature adoption standard: adoption metrics, targets by feature type, the release notes, enablement settings by tenant and the customer success playbooks.
Reads from
the subscription billing system: tenants and eligible users by plan, with feature enablement and usage events from the cloud monitoring and observability stack.
Acts in
the project management tool: it records the adoption finding on the feature and opens the follow-up tasks.
Hands back
An object with feature, adoption_percent, target_percent, gap_by_segment (a list), causes (a ranked list with cause, evidence, confidence and how_to_confirm) and fixes (a list with fix, owner and expected_effect).
Asks a person when
The cause is a defect, or the fix changes default settings for client tenants.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Adoption target at 60 days (%) | 30 | Share of eligible active users using the feature. |
| Days before judging adoption | 30 | Adoption is not judged before this. |
| Feature needs an admin to enable | On | When on, enablement by tenant admins is checked first. |
| Fewest eligible users to judge | 300 | Below this, findings are noted but not called a trend. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Judge adoption only after 30 days and with at least 300 eligible users.
- Compare against 30 percent adoption at 60 days.
- When on is true, separate tenants that have not enabled it from users who have it but do not use it.
- Weigh the competing causes: not enabled, not discovered, blocked by permissions or integrations, not valuable for the segment, or a bug; say what would confirm each.
- Never contact clients; the fix goes to customer success or product.
See the Feature Adoption Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.