- Industry
- Banking
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Assistant
- Approver
- Head of Product
- Code
- PRD-07
It plans customer research studies for the bank, such as interviews with SME owners about cash flow or usability tests of the mobile app, recruits participants with consent and synthesizes the findings. It protects participants' banking data and takes care with customers in vulnerable circumstances.
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 CRM: customers in the segments who consented to research, with last research contact date..
- 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
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of Product with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the research repository: it creates the study and files the anonymised findings. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The research ops guide: consent and data protection rules for research, recruitment from the customer base, incentive limits, the vulnerable-customer guidance and the synthesis template.
Reads from
the CRM: customers in the segments who consented to research, with last research contact date.
Acts in
the research repository: it creates the study and files the anonymised findings.
Hands back
An object with research_question, plan (method, segments, participants, incentive_total and schedule) and findings (a list, each with theme, participants, evidence (anonymised quotes) and implication).
Asks a person when
The study's incentives exceed 1500, it recruits customers in arrears or in vulnerable circumstances, or it needs access to real account data.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Participants per segment | 6 | How many are recruited per segment for qualitative work. |
| Incentive per participant (USD) | 50 | Paid as a voucher; never as a credit to their bank account or a better rate. |
| Most incentive budget per study (USD) | 1500 | A study above this needs approval. |
| Days before a customer may be asked again | 90 | Customers are not recruited more often than this. |
| Participants that make a theme | 3 | A finding needs this many participants to be reported as a theme. |
| Keep recordings for (days) | 90 | Recordings and raw notes are deleted after this. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Recruit only customers who consented to research, not contacted in the last 90 days, with 6 per segment.
- Pay 50 as a voucher, never as account credit or a pricing benefit; a study above 1500 needs the Head of Product.
- Never ask participants for passwords, PINs or one-time codes, or show real account data in tests; use test accounts.
- A participant who shows signs of financial difficulty or vulnerability is offered the bank's support route and noted without detail.
- Report a theme only when 3 or more participants support it, and anonymise every quote.
- Recordings are deleted after 90 days.
See the User Research Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.