Feature Adoption Agent
Tracks uptake of new features and flags gaps.
- Industry
- Retail
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Investigator
- Approver
- E-commerce Director
- Code
- PRD-10
It tracks uptake of new online store and app features (saved baskets, scan-and-go, in-app loyalty wallet, reserve in store) against their adoption targets and, where a feature lags, finds the stage where shoppers drop (discovery, first use, repeat use) and explains why. It ranks the causes, proposes the fix most likely to close the gap, and opens a follow-up on each lagging feature in the issue tracker. **The problem it solves:** Why a newly released online store or app feature is not being adopted: at which stage shoppers drop and what is stopping them.
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 e-commerce platform: feature usage analytics by stage, device and app version, and eligible shopper counts..
- 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 E-commerce Director with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the issue tracker: it opens a follow-up on each lagging feature with the proposed fix. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The adoption standard: targets per feature, the adoption definition, discovery placements, store-colleague promotion of app features, the release log and the sunset rules.
Reads from
the e-commerce platform: feature usage analytics by stage, device and app version, and eligible shopper counts.
Acts in
the issue tracker: it opens a follow-up on each lagging feature with the proposed fix.
Hands back
A list with one entry per feature, each with feature, adoption_percent, target_percent, lagging (true or false), drop_stage, causes (a ranked list, each with cause, evidence and confidence), fix and sunset_review (true or false).
Asks a person when
A sunset review is proposed, or the fix needs store colleagues to change what they do.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default adoption target (%) | 15 | Target share of eligible shoppers using the feature when none is set. |
| Evaluate after (days) | 30 | Adoption is judged this long after release. |
| Lagging at (% below target) | 25 | Adoption this far below target is lagging. |
| Counts as adopted when | used on 2 separate shopping trips in 30 days | The definition of an adopted shopper. |
| Sunset review after (days) | 120 | A feature still lagging this long after release gets a sunset review. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Judge adoption 30 days after release against the target, or 15 percent when none is set, using 'used on 2 separate shopping trips in 30 days'.
- A feature 25 percent below target is lagging; find the stage (discovery, first use, repeat use) where shoppers drop.
- Weigh competing causes: poor discoverability, app version uptake, a broken step on one device, store colleagues not promoting it, the feature not suiting the shopping trip, or a tracking gap.
- Propose the fix most likely to close the gap, with its evidence.
- A feature still lagging 120 days after release gets a sunset review, which goes to the E-commerce Director.
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.