Case Study · AutoZone
ALLDATA
Mobile Diagnostic Tool
Defining requirements and designing the iOS and Android diagnostic application used by over 300,000 professional automotive technicians worldwide.
300K+
PROFESSIONAL TECHNICIANS
iOS + Android
DUAL PLATFORM
$39/mo
SUBSCRIPTION LAUNCH PRICE
OBD-II
HARDWARE INTERGRATION
Client
ALLDATA — AutoZone Technology Division
Sector
Automotive Technology / SaaS
The Challenge
Putting OEM Diagnostic Data in Every Mechanic’s Pocket
ALLDATA is the automotive industry’s leading source of OEM repair and diagnostic information, trusted by professional technicians at shops across the globe. Their existing tools were desktop-bound — mechanics had to leave a vehicle mid-repair to look up information at a workstation, creating costly delays and workflow inefficiencies across service bays.
“The opportunity was to take ALLDATA’s deep OEM data library and make it instantly accessible at the point of repair — hands-on, vehicle-connected, and built around how mechanics actually work.”
As lead requirements analyst and UX designer, I worked directly with mechanics, manufacturers, and development teams to define what this product needed to be — from initial discovery through launch on both iOS and Android.
My Approach
Designing for the Shop Floor, Not the Boardroom
- Field & stakeholder interviews — Conducted in-depth interviews with professional mechanics, shop managers, and manufacturer representatives to map real workflows, identify pain points, and define success criteria for a mobile-first tool.
- Requirements documentation — Translated research into user requirement specifications, functional requirements, and 100+ user stories across diagnostic lookup, OBD-II hardware integration, and repair history workflows.
- Information architecture — Designed the application hierarchy to surface critical diagnostic data in the fewest possible taps — optimized for mechanics wearing gloves, working in low light, under time pressure.
- Cross-platform design system — Collaborated with UI developers on a unified style guide in Axure, ensuring a consistent interaction model across iOS, Android, and a subsequent consumer-facing AutoZone version.
- Field usability testing & iteration — Developed functional prototypes tested with mechanics in real shop environments, iterating on interaction patterns based on hands-on findings before development handoff.
Key Deliverables
What I Produced
- User requirement specifications and functional requirements
- 100+ user stories across diagnostic, repair, and OBD-II integration epics
- Information architecture and user flow documentation
- Annotated wireframes, storyboards, and interaction specifications
- Functional prototypes for field usability testing



