CarHubAutomotive · customer & merchant apps · 2022 · Product Designer
A service to book
A business to run
I helped redesign both CarHub apps: one for customers booking services, one for merchants managing the work.
One car
Both sides of the service
- Project length
- 3 months
- Team
- 2 designers, 1 product manager
- Across the experience
- Onboarding · booking · payments · loyalty
The project at a glance
- The problem
- Customers needed simpler service booking and payments; merchants needed tools to manage the corresponding work.
- My contribution
- One of two designers working with a product manager and client stakeholders over three months, from journey mapping to detailed design.
- The design decision
- We designed the customer and merchant apps as two sides of the same service, using shared priorities to guide the redesign.
- What this case shows
- Journey maps and an interactive customer prototype show the redesign. The original case study reports qualitative improvements, not measured results.
Every booking has someone on the other side
CarHub connects car owners with service providers through two apps. The brief called for easier onboarding, simpler payments and data entry, more online transactions, and reasons to return. We had three months.
Understand both sides first
We started with journey maps, usage data, and stakeholder workshops.
Map both journeys together
We mapped the driver’s and the merchant’s journeys to see where they met.
Find the right service
Compare what’s available for the car.
FindMake the service easy to find
Show the shop, its services, and offers.
Choose the car and time
Turn a service into a specific booking.
BookSame
bookingSee the work coming in
Know which service is scheduled and for whom.
Have a reason to come back
Keep upcoming services and loyalty points close.
ReturnBuild on the first visit
Keep the business visible through its services and offers.
Prioritize the wish list
In workshops, we used MoSCoW (must, should, could, won’t) to agree on what came first.
- Essential this round
- Could come later
- Outside this round
Design for both sides
Wireframes covered finding and paying for a service, plus merchant profiles, offers, sales, and schedules.
The same booking, read two ways
Customer: What does my car need?
Merchant: What work is coming in?
Customer: Which car am I booking for?
Merchant: Which car are we servicing?
Customer: When can I bring it in?
Merchant: When should we expect it?
Customer: How do I pay?
Merchant: How is the service being paid for?
Give people a reason to come back
Points, membership status, and rewards became visible, and merchants got space to promote offers.
- Use a service
- Earn points
- Redeem rewards
Take it for a spin
A service to book, a car to choose, and a time that works for you. Try the journey here.
Start with Car maintenance or Car care. Your wallet, loyalty points, and upcoming bookings are close by.
An updated presentation of the original customer flow. Account details, verification, prices, and appointments are simulated. No real bookings or payments.
Two redesigned apps and a customer journey to try
A high-fidelity prototype connects booking, car selection, payments, and loyalty.
Visit CarHubThe decision
We designed the customer and merchant apps as two sides of the same service, using shared priorities to guide the redesign.
What changed
- Mapping both journeys gave the team a shared view of the service and its priorities.
- The redesign covered customer booking and payments alongside merchant profiles, offers and schedules.
- A detailed customer prototype connected car selection, booking, payment and loyalty.
Abdul Latif Jameel · CarHub · 2022
My part in the work
I was one of two designers, working with a product manager and client stakeholders from journey mapping to detailed design.
Recommended next
A place to trade, a brokerage to run
CarHub connected a customer’s booking to a merchant’s work. At Invest.com, I designed the trading experience alongside the tools used by the brokerage team.
Read the Invest.com storyAbout this case study
Details come from my original case study, which reports qualitative improvements, not measured results.