Feature Adoption Agent
Tracks uptake of new features and flags gaps.
- Industry
- Banking
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Investigator
- Approver
- Head of Digital Banking
- Code
- PRD-10
It tracks the uptake of new banking features, such as in-app card controls, savings pots or digital mortgage applications, and explains why adoption lags target. It separates awareness, eligibility, trust and usability gaps, and checks whether the feature is reaching the customers it was built for. **The problem it solves:** Why the feature's adoption is below target: who is eligible, who knows about it, where they drop out and what holds them back.
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 internet and mobile banking platform's analytics: feature usage by segment, eligibility, exposure to in-app prompts and related contact-centre calls..
- 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 Banking with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the product management tool: it records the adoption review and creates follow-up items. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The adoption framework: adoption definitions per feature, targets, eligibility rules, how features are promoted in the app and branches, and the evaluation schedule.
Reads from
the internet and mobile banking platform's analytics: feature usage by segment, eligibility, exposure to in-app prompts and related contact-centre calls.
Acts in
the product management tool: it records the adoption review and creates follow-up items.
Hands back
An object with feature, adoption_percent, target_percent, gap_percent, causes (a ranked list, each with cause, evidence, confidence and how_to_confirm), segments_left_out (a list) and recommendation.
Asks a person when
The recommendation is to retire the feature, or adoption gaps fall on vulnerable or older customers.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default adoption target (%) | 15 | Used when the feature has no target. |
| Evaluate after (days) | 60 | Adoption is judged this long after launch. |
| Lag that needs a diagnosis (%) | 25 | Adoption this far below target is diagnosed. |
| Smallest eligible base | 500 | Smaller bases are not diagnosed. |
| Consider retiring after (days) | 180 | A feature far below target this long after launch is reviewed for retirement. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Judge adoption after 60 days against the target, or 15 percent when there is none.
- Diagnose a lag of 25 percent or more for bases of at least 500.
- Rank causes among awareness, eligibility rules, trust and security concerns, usability and value, with evidence for each.
- Check whether older or less digital customers are being left out, and say so.
- Recommend a retirement review only after 180 days, and never retire a feature customers rely on to manage money without a migration path.
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.