Product sense & design · Medium
Design a digital payments experience for first-time smartphone users over 60.
Short answer
Start by narrowing the user and their riskiest moments: sending money to family, paying a local shop and spotting fraud. Then design for confidence rather than speed, with large tap targets, plain-language confirmations, a trusted-contact safety net and voice support. Prioritise one or two solutions, define success as repeat unassisted payments and name the safety-versus-convenience trade-off.
Detailed answer
A framework that works
- Clarify the goal (adoption, safety, frequency?), platform and constraints.
- Segment users and pick one, e.g. a retired person living alone versus one whose children set up the phone.
- Map pain points across the journey: setup, first payment, routine payments, something going wrong.
- Generate solutions, then prioritise by impact and effort.
- Define success and name the main risks.
Worked example
Choose a 65-year-old who receives a pension and wants to pay the local grocer and send money to grandchildren. The biggest pains are fear of paying the wrong person, anxiety about PINs and difficulty telling genuine requests from scams.
- Saved, photo-labelled payees so routine payments never need typed numbers.
- Read-back confirmation ("You are paying ₹500 to Sharma General Store") in large text with optional audio.
- Trusted contact who is alerted to unusual payments or new payees above a threshold the user chooses.
- Scam interruption: a calm warning when a collect request arrives from an unknown payee.
Prioritise read-back confirmation and saved payees first: high impact on confidence, modest effort. The trusted-contact feature needs careful consent design so it does not become surveillance.
Metrics to propose: share of new users completing a second payment without help within a week, payment errors reported, and support contacts per active user.
Common pitfalls
- Treating "older people" as one group instead of designing for a specific person.
- Jumping to features before naming pain points.
- Ignoring the friction trade-off: every extra confirmation step slows routine payments for confident users.