A national financial services provider was out of compliance with the Zelle network, quietly losing members before the first payment screen ever loaded. I led the redesign that restored compliance and rebuilt enrollment as a trustworthy journey.
Zelle is a payment network with strict requirements about how banks introduce, disclose, and enroll members. The existing flow had drifted out of compliance, and the same places that created regulatory risk were also where members were abandoning the product. A redesign had to fix both problems without shipping two different experiences.
The stakes were real on both sides. Out of compliance, the bank risked formal action from the network. In the flow, members were dropping out before they ever sent a payment, so the product was failing to deliver on a service they had come to it for.
I started where the risk lived, not where the screens did. With legal, compliance, and product partners, I built a shared reading of what the Zelle network actually required, and translated those requirements into a set of design constraints a team could hold in its head.
From there I mapped the real enrollment journey, not the idealized one. Where members were reading, hesitating, re-reading, and leaving. Where disclosures were being skipped or mis-attributed to the bank rather than to Zelle. Where the flow silently assumed knowledge most members didn't have.
Only then did the visual design begin, and it was mostly a subtraction exercise: fewer steps, fewer decisions per step, clearer ownership of each disclosure.
Compliance is a design problem. If the rules aren't legible, the product isn't trustworthy.
The new flow restructures enrollment around three plain questions: who the member is, what Zelle does, and what the bank and the network each own. Disclosures appear where the decision happens, not in a wall at the end. Progress is visible so members can gauge whether to finish now or come back.
Beyond the ship. Each engagement produces a set of durable internal tools a team can keep using after the project closes. For Zelle, that was five.
A team-facing translation of the Zelle network requirements into a one-page set of design constraints. Now the reference for new flow work.
The real journey, not the idealized one. Member state, decisions, disclosures, and drop-off points annotated at each step.
Which disclosure belongs to the bank, which to the Zelle network, and where in the flow each one has to appear.
Prototyped, tested, shipped. Fewer steps, progressive disclosure, error states pinned to the specific requirement the member hit.
The process legal, compliance, product, and design now share for interpreting new network requirements as they land.
Enrollment completion rose about 20% across cohorts. Member satisfaction in the flow rose a comparable amount. Network compliance was restored and held through subsequent audits. Internally, the cross-functional reading of Zelle requirements became the reference the broader payments practice now works from.
Best for project inquiries, scoping conversations, and workshop requests. I answer within two business days.
A low-pressure intro call. Bring the system you're stuck on; I'll bring questions.