Almir Atlic

Senior UX/UI Product Designer · UX Design Lead · 20+ Years of Experience · AI-enabled product delivery

Bosch

Grade X Vehicle Diagnostic Tool

Redesigning high-stakes industrial software. This project streamlined browser-based diagnostics for Bosch workshops, helping technicians complete key tasks faster and with significantly fewer errors.

Legacy Project Note: This work represents an earlier stage of my UX/UI practice. It is included to demonstrate how my process and craft in complex enterprise systems have evolved.
Bosch Grade X diagnostic tool overview

Role

Lead UX and UI Designer

Timeline

2018 to 2019

Industry

Automotive / Enterprise

The Challenge

Bosch's Grade X software was a friction point in certified workshops across Europe. Cluttered and slow, the tool forced experienced technicians and apprentices to jump between screens and misread critical data. Slow diagnostics meant higher labor costs and reduced throughput, threatening Bosch's market position against more modern competing tools.

Verified Outcomes

*Results based on Comparative Task Analysis of legacy vs. new tool.

30% Faster

Average diagnostic sessions dropped from 15 minutes to 10.5 minutes.

88% Success

Apprentice success rates rose from 25% to 88% due to improved information hierarchy.

20% Higher Adoption

Workshop adoption grew from 60% to 80% following the interface overhaul.

The Math

Beyond speed, the error rate in data entry fell from 12% to 7%. This precision is vital in vehicle safety, where misreading a single diagnostic value can lead to incorrect mechanical repairs.

1. Research & Synthesis

Field Observations & Alignment

I believe in starting in the workshop, not the studio. By observing technicians in busy service stations, I identified the hesitation and "software fighting" that slowed down their throughput.

User needs vs business needs
Goal Alignment: Finding the overlap between Bosch's business goals and technician needs.

Auditing the Legacy UI

The old UI mixed navigation and content in a dense, overwhelming layout. We recruited 16 technicians of varying ages and experience levels to establish a baseline for our redesign.

Old vehicle specification screen
Legacy: Cluttered vehicle specification screen.
Old symptom selector screen
Legacy: Overloaded symptom selector screen.

Baseline Usability Testing

We ran four core tasks on the old software. Senior technicians succeeded 68% of the time, while apprentices struggled significantly with a 25% success rate.

Defining Archetypes

I plotted participants on two axes: experience and tech familiarity. This gave us our "Senior Pro" and "Young Tech" personas, allowing us to design one tool for two speeds of user.

Persona plot
Clustering: Experience vs. Technology familiarity plot.
Final Personas
Synthesis: Personas created from field research data.

Why?

Watching real technicians work revealed that "Senior Pros" needed less visual noise, while "Young Techs" wanted shortcuts. A mixed group made our findings more reliable.

2. Strategy & Architecture

Journey Mapping & Red Routes

I mapped the journey from login to final report to identify where users broke their flow. We defined one core Red Route: Identify vehicle, run network check, carry out task, then exit.

User journey map
Journey Map: Visualizing high-risk steps in the diagnostic path.

Card Sorting & IA

Through card sorting workshops, we grouped tools into logical categories. We used heatmaps to see which tools were "Always Used" versus "Rarely Used," allowing us to clean up the interface and finalise the system map.

Why?

Getting agreement on the basic diagnostic steps early prevented confusion later. Strategy is about finding the shortest path to value, ensuring the most used tools were always "one click" away.

3. Visual Design & Interface

Wireframing & Layout Systems

I created over forty low-fidelity wireframes to test task flows from the system map without the distraction of branding. This led to a vertical menu system that can expand for labels or collapse to save screen real estate.

Vehicle wireframe
Wireframe: Vehicle connection logic.
Network wireframe
Wireframe: Network view and error identification.

High Fidelity & Visual Hierarchy

Using Bosch guidelines, I designed a high-contrast interface. We prioritized large, readable data blocks to prevent misreads in the high-glare environment of a service station.

UI connection
Final UI: Vehicle connection and status.
UI overview
Final UI: Diagnostic overview with clear data blocks.

Mobile & Tablet Adaptations

Technicians often move around the vehicle. We adapted the flows for tablets, moving primary actions to the bottom for thumb reach and using drawers for secondary controls.

Mobile views
Responsiveness: Mobile and tablet views optimized for movement in the workshop.

Why?

Visual clarity was non-negotiable. Large touch targets and high-contrast tables ensured the tool remained usable for a technician working under a car with a tablet in hand.

4. Evaluating Grade X

Final Usability Testing

We repeated the baseline tasks with the same group. The results were dramatic: apprentices improved their success rate from 25% to 87.5%, actually completing tasks faster than some seniors.

New success senior
Post-Design: Task success for experienced technicians.
New success apprentices
Post-Design: Task success for students and apprentices.
New success senior
Post-Design: Efficiency for experienced technicians.
New success apprentices
Post-Design: Efficiency for students and apprentices.

The Results

Apprentices completed tasks faster than seniors because the new hierarchy removed the need for deep domain knowledge to navigate the UI. Seniors became more accurate, accepting a slight time trade-off for higher confidence in their results.

Lessons Learned

Designing for Two Speeds

Giving technicians a stable Red Route with optional shortcuts worked better than designing separate interfaces. It supported both the cautious senior and the fast-moving apprentice.

Navigation over Features

Most of our gains came from clearer labels and better grouping, not new features. Simplifying how people reach existing tools provided the most significant business impact.

Scalability (The Ford Project)

The success of Grade X led Bosch to apply this same design system to the Ford Diagnostic Tool. By reusing our Red Route thinking and IA patterns, we reduced the risk and timeline of the Ford project significantly.

Ford tool 1
Scaling: Applying patterns to the Ford diagnostic tool.
Ford tool 4
Scaling: Measurement view reused from the Grade X system.