Approach

1

Understand

Mapped existing business processes and user roles.

2

Structure

Defined information architecture and relationships between modules.

3

Simplify

Reduced unnecessary steps and consolidated related information.

4

Systemize

Created reusable patterns that could work across the product.

5

Scale

Extended the system across 25+ modules while maintaining consistency.

[ Repair Orders]

Turning the repair order into the central workspace

The Repair Order is where most of the shop's work comes together.

Instead of separating vehicle information, services, labor, parts, inspections and approvals across different screens, I structured the experience around a single repair workflow.

The goal was to let service advisors understand the complete state of a repair without constantly jumping between modules.

[ Role-based workflows]

The same repair. Different perspectives.

R&M serves people across the entire shop, but they don't all need the same information.

Service advisors need to manage customers, estimates and repair progress.

Technicians need to focus on assigned jobs, inspections, notes and vehicle status.

I designed these experiences around each user's immediate tasks while maintaining a consistent visual language across the platform.

[Desin System]

Making 25+ modules feel like one product

The scale of R&M made consistency a product requirement, not just a visual preference.

I created reusable foundations, components and interaction patterns that could be applied across appointments, repair orders, inventory, customers, technicians and other modules.

The system allowed new features to build on existing patterns instead of starting from scratch every time.

[Outcome]

A scalable foundation for a complex automotive operation

The work resulted in a unified product experience covering the core operational needs of an automotive repair business.

[Impact]

Connected previously fragmented workflows into a single platform.
Established patterns that could be extended across new modules without reinventing the UI.
Created a product structure capable of supporting increasingly complex shop operations.

[Key Learnings]

Complexity doesn't have to feel complex

R&M reinforced something I find important in enterprise product design: the goal isn't always to remove complexity.

Iterative testing pays off

Regular testing uncovered hidden issues and ensured the design met user needs.

Details matter

Small improvements, like error validation and mobile optimization, had a significant impact.

From Evidence to a Decision

Create a free website with Framer, the website builder loved by startups, designers and agencies.