Forty-nine screens, one standard.
I'm a UX designer on an enterprise payments platform at U.S. Bank that serves 39,000 client organizations. My first big job: audit every component, rebuild what had drifted, and make sure the coded product matches what we designed.
This is current, confidential work, so there are no screenshots here. The drawings on this page are illustrations; the numbers are from my résumé.
Unglamorous work that every user feels.
Big platforms drift. Teams ship fast, components fork, and a screen that met the standard last year quietly stops meeting it. This project was about finding every one of those gaps and closing them, in a way engineers could act on.
A payments platform for 39,000 organizations can't be approximately accessible.
The platform handles payments for 39,000 client organizations and more than 150,000 unique users a month. At that scale, a contrast failure or a missing error state isn't an edge case. It's thousands of people stuck in the middle of moving money.
Over time, screens had drifted away from the bank's accessibility and design-system standards. Nobody could say exactly how far, because nobody had checked every component.
So I checked every component.
I audited every component across the affected screens against accessibility and design-system standards, and logged each gap with what it should be instead. That audit became the rebuild plan.
I presented the findings at two corporate UX forums, so other teams could check their own products for the same problems.
Every component, every screen. No sampling. Drift hides in the screens nobody opens in reviews.
One source of truth. Each finding pointed back to the accessibility rule or design-system component it broke.
Two UX forums. The findings went beyond my team so other teams could fix the same problems.
Rebuilding 49 screens, and the patterns under them.
I rebuilt 49 screens to accessibility and design-system standards. Fixing screens one by one would only last until the next release, so I also standardized the patterns underneath:
- Responsive patterns across 3 breakpoints for 2 end-to-end payment flows, documented so developers build them the same way every time.
- 3 error states that nobody had designed, closed by pulling together what peers had already documented into reusable patterns.
- Developer-ready documentation for all of it, so the standard lives in the handoff, not just in Figma.
Catching defects before users do.
The last mile matters most. Before each release, I compare the coded screens against the approved designs, find UI defects and annotate the fixes directly for engineering. It's the part of the job my engineering years prepared me for best: I know what a developer needs in a bug note to fix it in one pass.
What I'm learning so far.
At enterprise scale, consistency is a feature. Users move between many screens; every inconsistency is something they have to relearn.
An audit is a persuasion tool. A complete inventory turned "we should fix accessibility" into a plan people could approve and schedule.
