Feature Adoption Agent
Tracks uptake of new features and flags gaps.
- Industry
- Oil & Gas
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Investigator
- Approver
- Head of Digital Products
- Code
- PRD-10
It tracks uptake of new features, such as digital gas test records, mobile work order close-out or fleet spending controls in the card app, against targets by site or segment. When a feature lags it works out why: training, devices, connectivity, site procedures still on paper, or the design. **The problem it solves:** Why the feature lags its adoption target: which sites or segments, by how much, since go-live, and what differs there in training, devices, connectivity or procedures.
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 product analytics tool: eligible and active users by site or segment for the feature, with rollout and training dates..
- 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 Digital Products with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the product management tool: it files the adoption diagnosis and opens follow-up actions. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The adoption guide: adoption definitions and targets by feature, site rollout dates and training records, device and connectivity status by site, and the sunset rules.
Reads from
the product analytics tool: eligible and active users by site or segment for the feature, with rollout and training dates.
Acts in
the product management tool: it files the adoption diagnosis and opens follow-up actions.
Hands back
An object with by_site (a list, each with site_or_segment, adoption_percent, target_percent and lag), causes (a ranked list with cause, sites, evidence and confidence), actions (a list with action, owner and site) and sunset_review (true or false).
Asks a person when
The diagnosis proposes removing or sunsetting a feature, changing what a fuel card tier includes, or asking a site to change its procedure.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default adoption target (%) | 70 | Used when a feature has no target. |
| Days before judging | 45 | A feature is judged after this many days at a site. |
| Lag that needs explaining (points) | 15 | A site this far below target is explained. |
| Smallest population judged | 15 | Smaller site populations are not judged. |
| Sunset review after (days) | 180 | A feature below half its target after this is reviewed. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Judge each site after 45 days against its target, or 70 percent; populations below 15 are not judged.
- Explain a lag of 15 points, weighing training, devices, connectivity, procedures still requiring paper and the design.
- When the site procedure still requires paper, the cause is the procedure, not the users.
- Review for sunset after 180 days below half target.
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.