Redesigning authentication for Visa's global platform

The challenge seemed straightforward: create one consistent authentication flow across all Visa regions. In practice, it revealed deep fragmentation in Visa's digital experience.

Each regional site followed its own step order. Some demanded PAN (Primary Account Number) entry immediately; others deferred it. Mobile keyboard layouts were unoptimized. Microcopy tone shifted between properties. What should feel like a quick, reassuring sign-up came across as bureaucratic and inconsistent.

I audited every regional flow, annotating unnecessary steps, confusing language, and implementation-driven friction. One flow required PAN entry before the account object even existed -- a pattern that broke entirely if the user closed the browser.

Another locked users out until email verification, even after they had submitted personal data. The pattern was clear: inconsistency was the rule, not the exception.

To align stakeholders, I mapped and prototyped three flow families -- each representing a distinct philosophy toward the friction-versus-data trade-off.

Stakeholders needed to feel the extremes, not just read about them. I built detailed mobile-first prototypes, then adapted each for desktop to demonstrate how the approaches would behave in practice.

This was the heart of the design leadership challenge. Each stakeholder group brought valid, competing concerns.

To make trade-offs tangible, I modeled conversion funnels using industry benchmarks and internal data from comparable flows.

I created two rigid flow prototypes exploring different approaches to the same constraints. Both required email verification and PAN entry, but sequenced them differently to test user experience impact.

I prepared two handoff flows for final review: my recommended less rigid approach where users could log in without a card, and the business-preferred rigid approach requiring both email verification and card entry upfront.

The rigid version was chosen. It guaranteed data integrity and aligned with Visa's business goals, despite the projected conversion impact.

With the structural decision made, I focused on craft -- softening the rigid experience through details that reduced perceived friction without changing the flow itself.

The rigid flow launched as Visa's harmonized onboarding journey across all regions, delivering on business objectives while maintaining user experience quality through careful craft.

Three lessons from this project shape how I approach every design challenge:

I recommended evolving toward a hybrid model that preserves data integrity while respecting user motivation. This became a roadmap item for future backend evolution.

This project was not about designing a single flow. It demonstrated how a lead product designer navigates global-scale complexity -- balancing user empathy, business needs, and technical constraints while guiding stakeholders through data-informed decisions.

The rigid flow was not my ideal outcome, but I ensured it was crafted with care, empathy, and mobile-first detail. I established a clear path for future improvement and left the organization better equipped to navigate these trade-offs.