Company Context
You’re the PM for NovaPay, a Series D consumer fintech app (neobank + P2P payments) with 18M MAUs and 6.5M DAUs across the US, Canada, and the UK. NovaPay’s revenue comes from interchange, premium subscriptions ($9.99/mo), and partner offers (cashback). Mobile is the core surface: 92% of sessions are on iOS/Android, and the app supports 12 languages.
NovaPay competes with Cash App, Revolut, Monzo, and Chime. Competitors have recently improved perceived quality with smoother onboarding, faster app start times, and more consistent UI patterns. NovaPay’s brand promise is “money movement you can trust,” so user perception of reliability and polish is directly tied to retention and conversion.
User / Market Scenario
NovaPay serves three primary personas:
| Persona | Share of DAUs | Primary Jobs-to-be-Done | Quality Sensitivities |
|---|
| Gig Worker “Maya” | 38% | Get paid fast, move money, avoid fees | App speed, reliability on low-end Android, clear error recovery |
| International Student “Arjun” | 34% | Set up account quickly, receive money from family, manage FX | Onboarding clarity, localization, trust cues, KYC transparency |
| Young Professional “Sofia” | 28% | Budgeting, premium features, card controls | UI consistency, discoverability, perceived polish |
Device mix is skewed toward mid/low-tier Android: 55% Android, and within Android, 40% are devices with <4GB RAM. Roughly 18% of sessions occur on “poor” networks (high latency / packet loss).
The Problem / Opportunity
Over the last two quarters, NovaPay’s growth has slowed. A cross-functional review suggests the product’s in-product experience quality is hurting both acquisition and engagement.
Key signals:
- Onboarding completion (install → first successful KYC submission) dropped from 71% to 62% in 6 months.
- Time-to-first-value (install → first successful action: add money, receive money, or activate card) is median 19 minutes; top competitors benchmark at <10 minutes.
- App start time (p95) is 4.8s on Android (goal is <3.0s). iOS p95 is 3.2s.
- Crash-free sessions are 98.6% iOS and 97.1% Android; support tickets spike when Android drops below 97.0%.
- Store ratings declined from 4.6 → 4.2; review themes: “confusing verification,” “buttons don’t respond,” “too many steps,” “random logouts.”
Recent user research (n=24 interviews + 1,200 survey responses) highlights:
- Users interpret slow screens and ambiguous errors as “my money isn’t safe.”
- KYC steps feel like a “black box” (no progress, unclear why rejected).
- Users on poor networks see repeated retries and duplicate taps; some accidentally submit forms multiple times.
Leadership asks you to propose a plan to ensure consistently high-quality in-product experiences for mobile users—not just for one feature, but as an ongoing product capability.
Your Task (Deliverables)
Prepare a structured response that covers:
- Define “high-quality in-product experience” for NovaPay mobile (dimensions, user outcomes, and how you’d measure it).
- Identify the highest-impact user journeys to focus on first (e.g., onboarding/KYC, P2P send, add money, card controls), and justify your choice using data and user needs.
- Propose 3–5 concrete product/UX/platform initiatives that would measurably improve quality (e.g., error recovery patterns, performance work, progressive disclosure, offline/poor-network handling, instrumentation).
- Prioritize your initiatives for an MVP/Phase 1 (next 8–10 weeks) and a Phase 2 (next 2 quarters), using a clear prioritization method.
- Define success metrics and an experiment/validation plan, including guardrails (e.g., fraud, compliance, revenue).
Constraints
- Timeline: Phase 1 must ship within 8–10 weeks.
- Team: 8 mobile engineers (5 Android, 3 iOS), 2 backend engineers, 1 data analyst, 1 designer. No additional headcount this quarter.
- Compliance: KYC/AML flows must meet regulatory requirements; copy and UI changes in KYC require compliance review with a 2-week SLA.
- Risk: Fraud team warns that reducing friction can increase account takeovers; any onboarding changes must not increase fraud loss rate.
- Technical: App has accumulated design inconsistencies across 6 squads; there is no single design system on Android, and analytics events are inconsistent across platforms.
You do not need to write PRDs, but your answer should be specific enough that an engineering/design team could start execution.
