Nate DouglasSenior Product Designer, home

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
62% → 94%correctly understood payment statusMaze tests, 50 people per round
68% → 92%found their balance and chose a payment method without helpThe same two test rounds
36 → 14payment-status support contacts per 1,000 paymentsPower BI, 90 days before and after launch

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 redesigned Tolls NY home page: Pay Toll Bill, Log in, Open an account and E-ZPass On-the-Go over a bridge photo

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

My calls
  • Starting with payments
  • Status at the center, one decision per screen
  • Layout of the fixed legal text
  • Testing guided billing against open chat
Made together
  • Task-based entry, with engineering
  • Version 1 status, with the backend lead
  • New components, with the frontend lead
Not mine to make
  • Bank authorization wording
  • The bank’s nightly confirmation file
  • Final sign-off, by MTA leadership
Problem

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.

  1. Hard to find. Balance and payment methods were buried.
  2. Hard to read. Plans were codes like MCC and NRC.
  3. Hard to trust. After paying, people had to guess whether it went through.
The legacy E-ZPass payment flow in five screens: account overview, plan selection, payment setup, review and payment history
Where it started: the legacy payment flow, five screens from account overview to payment history.
What I found
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.

Decisions

Three decisions that shaped it.

  1. Account analytics by area, with payments and statements flagged
    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.
  2. Three payment status screens: Posted with nothing else to do, Processing with a warning not to pay again, and Action required after a bank return, with Pay another way and Talk to support
    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.
  3. Auto-replenishment authorization, legacy beside the approved redesign
    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

  1. People askin their own words, or by picking a choice
  2. The model structures itinto choices: which bill, which payment, what they want to know
  3. People confirmor adjust the choices
  4. The records answerpayment match and bank status come from the account’s records, not the model
Guided billing help: the $161.50 bill and three choices, did my payment go through, what amount is on my bill, I can’t find my payment
Guided billing starts by asking what to check.
Side by side: the guided result saying the payment is processing and not posted, and Dara’s chat panel giving the same answer
Left: guided billing, which shipped. Right: Dara, the open chat version I designed and tested against it. Guided won, so Dara didn’t ship.
Before and after

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.

  1. Before: the legacy home page After: the redesigned home page with four entry points

    The four main tasks are up front, and alerts got their own spot.

  2. Before: a coded plan table After: plans as plain-language cards

    The coded rows became cards with a real plan name, what it covers and the price.

  3. Before: raw bank fields under legal text After: saved payment methods listed up front

    Saved methods show first with the primary one marked, and there’s one way to add a bank or card.

  4. A dense legacy E-ZPass dashboard on desktop and squeezed into a mobile viewport The redesigned E-ZPass dashboard on desktop and intentionally responsive mobile

    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.

  5. Pay Toll Bill, amount due Add Checking Account, filled Statements on mobile

    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.

Design system

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.

The Apollo UI guide, a clickable Figma prototype
The Apollo UI guide, live. Flip the icons to dark mode, change a button’s theme and style, or open Form to see every field state.
The 12 documentation pages
Looking back

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.
Unshipped concept: designing trust controls for an E-ZPass AI assistant
What people said

From people I worked with.

Saurabh Prabhat
“He approached problems thoughtfully, collaborated effectively with colleagues, and communicated design decisions with clarity. I valued his ownership of projects…”
Saurabh Prabhat, Senior Global Director of AI and UX at Conduent · my manager Read the recommendation ↗