Verizon Connect – 2024
Turning four legacy pages into one
I led the redesign of the vehicle area, the page that feeds data to the rest of Reveal. Card sorting gave us an architecture built around how people describe a vehicle, not how the database stores it. Four pages became one, so users find what they need where they expect it.
Problem
Vehicle information sat across four pages with inconsistent navigation. Edit fields showed to every user regardless of whether they could use them, and related data was split in ways nobody could predict.
Other teams could not even link to it reliably, because no single page was guaranteed to hold what they were sending users to see. People landed, found the wrong thing, and left.
Solution
One page, grouped the way users describe a vehicle rather than the way the database stores it. The card sorting did double duty. It gave us the grouping, and the same map told engineering which APIs they needed, which took the guesswork out of their estimates.
The page is built entirely from design system components and holds up across account types, so the team extends it now without redesigning it.
Results
One page instead of four. Everything about a vehicle now sits in one place, so answering a question no longer means checking four pages to find which one holds the field you need.
Users land where they meant to. Other teams now link straight to the vehicle page and people find what they came for. Before, those links dropped users on a page that often did not hold the answer, and they left.
Usage increased 2.5x more. Unique user sessions grew from roughly 36K to 89K per month, driven by a page people could finally rely on.