Discover
Why: The progress bar request is an assumption, not evidence of the cause.
Deliverable: Stakeholder map, research questions and event-data audit.
PRACTICE PROJECT / PROJECT FROM SCRATCH
Investigate why applicants leave before account creation, then define a safe, measurable improvement.
Read the brief and work through the deliverables before opening the reference approach. Your notes stay in this browser only.
Northbank is a fictional retail bank with mobile account opening. Identity checks use an external provider; support and compliance teams review exceptions.
35% of applicants abandon digital onboarding before account creation. A sponsor asks for a new progress bar, but no root cause has been established.
The identity API returns a provider session ID, status and error code. Callbacks can be delayed; timeout is currently shown as a generic failure.
Draft an approach here, or work offline. Notes are stored locally in your browser—not sent to a server.
This is one defensible approach, not the only correct answer. Compare the reasoning and trade-offs with your own work.
Why: The progress bar request is an assumption, not evidence of the cause.
Deliverable: Stakeholder map, research questions and event-data audit.
Why: Separate customer choice, copy confusion and technical failure before prioritising.
Deliverable: AS-IS journey with error paths and segmented drop-off.
Why: The smallest safe improvement should be testable.
Deliverable: Resumable-upload and error-recovery stories with security criteria.
Why: A conversion lift cannot come at the cost of fraud or privacy.
Deliverable: UAT matrix and cohort experiment with control metrics.
Why: Success requires a precise denominator and guardrails.
Deliverable: Seven-day completion, step-level failures, support contacts and fraud exceptions.