Rebuilding how millions of drivers pay a toll.
- Pay types
- Dashboards
- Login
- Personal plans
- Support
- Correspondence
- Role
- Senior product designer
- Team
- Led a team of three designers, then was the only designer on E-ZPass in 2026. Worked with 5 PMs and 40+ engineers.
- Timeline
- June 2023 to June 2026
- Tools
- Figma, Claude Code and Cursor for coded prototypes and the entry alternatives, Maze with Respondent for testing, Power BI and Storybook.
- Platforms
- Web and native mobile, NY and NJApp StoreGoogle Play
Mine: the design and the Apollo design system. Not mine: the build, the follow-up test round and the support data.
How these were measured
Percentages: baseline and follow-up usability testing in Maze, 50 people per round; another group ran the follow-up round. Support contacts: post-launch data shared by the E-ZPass program team, 90 days before and after launch. Tolls NY, the app this shipped in, has 3M+ downloads; that is the product’s reach, not a result of my work.
The short version
I design what a product does when it isn’t sure.
On E-ZPass, that moment came right after Pay: did it go through, and is it safe to pay again? Every chapter designs for it: payment status, guided billing, which shipped, and two AI assistant concepts that didn’t ship.
The rule behind every screen: data that isn’t confirmed must never look like a fact. See it in three states
Who made which call
- Starting with payments
- Status at the center, one decision per screen
- Layout of the fixed legal text
- Testing guided billing against open chat
- Task-based entry, with engineering
- Version 1 status, with the backend lead
- New components, with the frontend lead
- Bank authorization wording
- The bank’s nightly confirmation file
- Final sign-off, by MTA leadership
A service people can’t avoid, with an interface that hadn’t kept up.
E-ZPass isn’t optional for most Northeast drivers, so when it’s confusing, they’re stuck.
- Hard to find. Balance and payment methods were buried.
- Hard to read. Plans were codes like MCC and NRC.
- Hard to trust. After paying, people had to guess whether it went through.
Paying wasn’t the hard part.
People could find Pay. They couldn’t tell what happened after they pressed it, so the redesign centers on what people see after they pay.
At baseline, only 62% correctly understood their payment status.
Three decisions that shaped it.
-
- Situation
- The account area covered sign-up, payments, statements, plans and profile. We couldn’t do it all at once.
- Call
- Start with payments and statements, where the analytics showed the clearest drop-off and failures cost the most.
- Cost
- Sign-up, plans and profile waited, even though plan names confused people too.
- Result
- The data decided the order of the work.
-
- Situation
- It looked like people couldn’t find things. Research showed a trust problem: they couldn’t tell what happened to their money.
- Call
- Status, balance change, next steps and recovery go at the center. One decision per screen on the phone.
- Cost
- More screens.
- Result
- Understanding of payment status rose from 62% to 94% in usability testing.
-
- Situation
- The bank authorization wording couldn’t change.
- Call
- Same words, new layout: a plain summary first, full terms below, consent next to what it authorizes.
- Cost
- The full legal text stayed on the page.
- Result
- Approved with the wording unchanged, and without the wall of text.
Guided billing over open chat.
Guided billing beat open chat in prototype tests, so guided shipped. It shows whether the payment went through and what to do next, without people needing to know what to ask.
What the AI does
- People askin their own words, or by picking a choice
- The model structures itinto choices: which bill, which payment, what they want to know
- People confirmor adjust the choices
- The records answerpayment match and bank status come from the account’s records, not the model
Same tasks, rebuilt.
These are just a sample of the full redesign.
Screen by screen
A handful of the roughly 3,000 screens in the redesign, across web, native and responsive. Pick a task to see the legacy screen and the redesign together.
-
The four main tasks are up front, and alerts got their own spot.
-
The coded rows became cards with a real plan name, what it covers and the price.
-
Saved methods show first with the primary one marked, and there’s one way to add a bank or card.
-
Status comes first, there’s one main action, and the controls are big enough to tap.
Before: the legacy website, and the same page squeezed onto a phone, tables and tiny actions included.
After: the redesigned website, with a phone layout designed from the start.
-
Every step follows the same pattern.
Amount due up top, payment methods below.
One field per line, with a check diagram where people need it.
Statements are searchable, and any period is one tap away.
The Apollo design system, rebuilt.
I rebuilt Conduent’s Apollo design system myself. For the first two to three months it took about half my time.
Payment status needs to be more than one screen.
What didn’t work
Moving the Pay button and making it more visible. Nothing really changed, because people could already find Pay. That pointed us to what happened after they pressed it.
What I’d change
Test rough end-to-end flows in week one. The problems were in the handoffs between steps, not the screens.
What I’d do next
Payment status as a full system. Seven states, each saying what it means for the balance and whether it’s safe to try again.
What I’d measure next
- How often Processing ends in rejected or returned, and whether people found out in time.
- How often guided billing hands off to a person, and whether the agent has to ask again.
- Whether people still come back within a day to check.
From people I worked with.

“He approached problems thoughtfully, collaborated effectively with colleagues, and communicated design decisions with clarity. I valued his ownership of projects…”


