§ 01 · Overview
A full rebuild, not a facelift, of the fragmented internal and partner platform used by Tag It DMV, a private company that intermediates DMV services across 8 states (with plans to expand nationwide). Dealers, title clerks, sales teams, and accounting were juggling state portals, emails, PDFs, and spreadsheets. I gave them one system for all of it, plus a design system that scales across states. Several NJ state departments now reference parts of it.
§ 02 · Goals
Drastically reduce user error and abandonment
Over 40% of support tickets stemmed from interface-induced mistakes and unclear steps. The goal: make task flows clear, predictable, and resilient, especially for high-volume dealers, title clerks, and accounting teams.Simplify key DMV workflows without breaking policy
Every improvement had to respect strict legal/compliance constraints across states. We simplified complex processes (e.g., Real ID, vehicle registration, plate transfers) without removing required steps or wording.Build a system other teams could adopt
Deliver a scalable, WCAG-compliant design system and patterns that other internal departments and partner states could adopt quickly.Simplify complex, rule-bound systems
Optimize multi-conditional flows under strict constraints (similar to versioned APIs or compliance docs).Design scalable, reusable UX patterns
Create modular design tokens and patterns that other teams can implement with minimal rework.Increase reliability and reduce friction through clarity
Improve predictability, validation, and user confidence in data-heavy flows.
§ 03 · My role
I worked closely with operations, compliance, and engineering teams to turn fragmented workflows into clear, structured user flows. My main goal was to make complex tasks easier to follow and reduce errors by improving consistency, validation, and overall usability. I also built a modular design system that met WCAG 2.2 AA accessibility standards and made it easier to scale the platform across states.
§ 04 · Team
2 front-end devs, 1 content strategist, Tag It DMV ops lead + compliance reviewer. I owned UX, IA, and accessibility outcomes; devs implemented the design system + flows; content strategist handled policy-sensitive microcopy with legal review.
§ 05 · Problem
Problem
NJ Official DMV Website (Vehicle Registration)

Tag It DMV was growing fast across 8 states but lacked a centralized system. Staff and partner dealers bounced between state portals, spreadsheets, email threads, and legacy tools, leading to duplicate data entry, missed steps, and inconsistent outcomes.
Core issues
Fragmented workflows across states (different rules, names, and exception paths).
Inconsistent UI and unstructured forms caused avoidable errors and rework.
Compliance risk: mandatory language and document checks were easy to miss.
Operational drag: high support volume; title clerks escalated routine edge cases; accounting reconciled by hand.
Business impact
Task abandonment and "phone-a-human" behavior from dealers under time pressure.
Over 40% of tickets tied to interface issues (unclear next steps, ambiguous language).
Slow onboarding of new states due to one-off UI patterns and lack of a reusable system.
This case study focuses on one challenge:
Redesign key DMV workflows (e.g., registration, Real ID document handling, transfers) to reduce user error and increase completion rates, while staying within state-by-state legal and accessibility constraints.

§ 06 · Research
Research
I led a dual-track effort balancing internal constraints and field usability across states.
Stakeholder Discovery
8 interviews with Tag It DMV operations, compliance, and support leads.
Mapped state-by-state requirements, portal dependencies, and policy wording that could not be changed.
Identified conflict hotspots where legal phrasing blocked clarity; defined safe microcopy patterns with legal sign-off.
Prioritized dealer workflows and title-clerk tasks with the highest error and ticket rates.
User Research
12 dealer/title-clerk interviews across high-volume partners; 50 surveys across 8 states.
Top pain points: unclear required documents, inconsistent naming across states, and non-responsive layouts under real-world desk setups.
72% reported abandoning or deferring mid-process to call support when unsure of the next step.
Personas (Internal & Partner Users)
| Persona | Goals | Frustrations | Behavior |
|---|---|---|---|
| Marta (Title Clerk, 41) | Get plates/registration submitted on first pass | Document rules differ by state; unclear error states | Desktop, batch processing 30+ tasks/day |
| Kevin (Dealer Manager, 34) | Register multiple vehicles quickly & correctly | Inconsistent steps across states; slow exception handling | Desktop, expects speed & predictability |
| Renee (Accounting, 29) | Reconcile fees & submissions with minimal back-and-forth | Missing fields cause rework; unclear audit trails | Uses exports; needs reliable system statuses |
Preview Of Google Drive File System


§ 07 · Design + Development
Design + development
Early System Build (Design 1.0)

Information Architecture + Task Flows
Reduced IA depth by ~30% to surface the top actions immediately.
Built structured flows for Register a Vehicle, Plate Transfer, Real ID doc handling, and Out-of-State transfers.
Introduced state-aware branching so steps and language adjust automatically to local rules.
Partnered with compliance to transform policy-heavy content into plain-language microcopy with inline citations for auditors.
Increased comprehension scores by 42% in validation rounds, measured with a Cloze test, where people fill in words removed from a passage.
Wireframes + Validation
Produced 60+ low-fi wireframes; tested over 3 rounds with dealers/title clerks.
Tree testing + heatmaps to locate flow bottlenecks; simplified or reordered steps accordingly.
Simulated edge cases with live data (e.g., VIN mismatches, multi-owner vehicles, out-of-state records not found).
Established a "stoplight" next-step model (clear "ready to proceed" vs. "needs document x" states).
High-Fidelity UI + Accessibility
Built a responsive, WCAG 2.2 compliant design system from scratch.
Key features:
Real-time form validation with localized, actionable errors.
Progressive disclosure for complex steps (ID uploads, multiple owners).
Dynamic checklists tied to state, vehicle type, and ownership scenario.
Sticky status + audit trail for accounting and compliance review.
Solved critical edge cases:
Multi-state rules changing field requirements mid-flow.
VIN not found / database mismatch recovery paths.
Document mismatches during Real ID verification.

§ 08 · Results
Results
Within 1 month of soft launch, the consolidated platform delivered measurable improvements:
Key Metrics:
- Task success rate +36 pts
- Average completion time −35%
- System usability score +28 pts
- Support tickets −40%
Preparation For Ongoing Maintenance
I organized the Figma files and design system for long-term use.
Each component included usage notes, responsive behavior, and accessibility guidance directly in Figma.
Design tokens and component names matched the codebase to simplify development and prevent inconsistencies.
A dedicated overview page documented structure, hierarchy, and updates, allowing new designers and developers to onboard quickly and maintain the system without guesswork.
