Case Study
Progressive Registration: Redefining Onboarding for Millions at MoneyGram
Modernizing onboarding to build trust and accessibility for users across the U.S. and Mexico. I led the UX redesign that transformed a compliance-heavy flow into a simple, confidence-building, compliant digital experience.
Reading time: 5–6 minutes
Role: Senior Product Designer
Year: 2024
Platform: Enterprise Fintech (MoneyGram Global)
The Challenge
MoneyGram’s online registration flow was a critical entry point, but it was also a major source of friction.
Users were required to complete a long, compliance-heavy onboarding process before experiencing any product value. The flow combined identity verification, regulatory requirements, and security steps into a single, overwhelming experience.
As a result, many users abandoned registration early, often before fully understanding why certain information was required or how far they were in the process. This directly impacted conversion, trust, and accessibility, especially across different markets and user profiles in the U.S. and Mexico.
User feedback highlighting confusion, trust concerns, and rigidity in the legacy onboarding flow.
Constraints & Requirements
Improving the onboarding experience required navigating a complex set of regulatory, technical, and organizational constraints.
MoneyGram operates in a highly regulated financial environment, which meant identity verification, security, and compliance requirements could not be removed, only redesigned. The onboarding flow also needed to support multiple markets and languages while maintaining a consistent, accessible experience.
Additional constraints included legacy systems, shared design patterns across products, and close collaboration with engineering, legal, and compliance partners. Any design change had to be scalable, compliant, and feasible to implement across regions.
Design decisions balanced user needs, technical feasibility, and regulatory requirements.
Design Insight
When I joined the onboarding team, MoneyGram faced a quiet but costly issue: thousands of users started registration but never finished. What looked like a usability gap revealed a deeper challenge of trust and accessibility.
That realization led me to reimagine onboarding around a simple design principle:
“Earn trust progressively, not demand it upfront.”
Design Strategy
To translate this principle into a scalable solution, I focused on restructuring onboarding around progressive disclosure, early value exposure, and clear expectation-setting.
Progressive disclosure: Reduced upfront cognitive load by deferring verification steps until users understood the value.
Early value exposure: Allowed users to explore key features before completing full registration.
Expectation setting: Clearly communicated why information was required and when it would be used.
Key Flow Changes
Based on the design strategy, the onboarding flow was restructured to reduce friction, build trust progressively, and expose value earlier without compromising regulatory requirements.
Progressive Registration
Instead of requiring full identity verification upfront, the flow was redesigned to collect information incrementally. Users could move forward with lighter inputs first, with verification steps introduced only when necessary.
Early Value Exposure
Users were given the ability to explore key product features before completing full registration. This helped establish relevance and confidence early in the experience, reducing hesitation during later verification steps.
Clear Expectations and Trust Signals
Each request for sensitive information was paired with clear explanations about why it was needed and how it would be used. This reduced uncertainty and helped users feel more comfortable progressing through verification steps.
Outcomes & Impact
The redesigned onboarding experience improved completion rates and reduced early drop-off by making the process feel more approachable and transparent. By aligning compliance requirements with progressive disclosure and clearer communication, users were more willing to continue through verification steps.
Internally, the new flow established a scalable onboarding model that could be adapted across markets while maintaining regulatory integrity.
Key Learnings
This project reinforced the importance of designing for trust in regulated environments. Constraints are not blockers, they are design materials. By collaborating closely with engineering and compliance partners, I learned how to translate rigid requirements into human-centered experiences without compromising scale or security.
This project focused on onboarding trust. The next case study shifts to system-scale design and governance.