Less friction upfront. More support afterwards.
The experience adapts as the driver’s needs change.
Explore the case study:
https://t.co/s3c7gm0JG3
What would you remove from an emergency flow?
When you’re stranded, every unnecessary question feels like friction.
For Mobile Mechanic, I designed the core journey around one principle:
Get help moving first. Collect secondary information later.
Here’s how that shaped the experience 🧵
#ProductDesign#UXDesign
A key design principle:
Ask for information when it becomes useful.
Before dispatch, request only what is needed to send help.
After dispatch, progressively introduce tracking, messaging, optional AI assistance and payment.
Progressive disclosure keeps the urgent path clear.
The result: an experience designed to provide reassurance from request to repair.
Good UX doesn’t always remove the wait. Sometimes it makes the wait understandable.
Full case study: https://t.co/s3c7gm0JG3
What frustrates you more: a delay, or not knowing what’s happening?
The biggest roadside-assistance problem isn’t always the breakdown itself.
It’s uncertainty.
While designing Mobile Mechanic, I asked:
How might we reduce uncertainty for drivers when they’re already under pressure?
Here’s how that shaped the product 🧵
That led to 4 design priorities:
01 Clear status
02 Visible ETA
03 Mechanic visibility
04 Continuous communication
The opportunity wasn’t just to make assistance faster. It was to make the journey more predictable.
Mobile Mechanic challenged me to think beyond polished screens and design the complete service experience.
Explore the full case study:
https://t.co/lRpBUjG92e
Research → Strategy → UX/UI → Prototype
What would you improve about roadside assistance?
#UIUX#ProductDesign
The problem
Breaking down is stressful enough. Uncertainty makes it worse:
• Long call-centre queues
• Little visibility of who’s coming
• Uncertain arrival times
The design challenge: How might we reduce uncertainty when drivers are already under pressure?
Why “Help first. AI second”?
I didn’t want AI diagnosis to delay roadside help.
Assistance is dispatched first. AI is optional, helping identify a possible issue and share useful context with the mechanic.
AI supports the service. It doesn’t control access to it.
That thinking translated into an experience centred around three things:
Fast dispatch. Live tracking. Repair visibility.
Instead of making users repeatedly ask “what happens next?”, the interface continuously communicates status and the next action.
The core journey
I deliberately kept the critical path focused:
Request Help → Confirm & Dispatch → Mechanic Assigned → Live Tracking → Repair & Pay
The priority is getting assistance moving quickly, then keeping the driver informed throughout the journey.
@GhanaianMuseum Flooding in Ghana is ultimately a leadership problem. For over 50 years, the country has experienced recurring floods, yet successive governments have failed to implement a lasting, effective solution.
@ChristDeKing@i_Folivi Flooding in Ghana is a leadership failure. After more than 50 years of recurring floods, it is no longer enough to blame the rain. The real issue is the failure to implement and sustain lasting solutions