The situation
Vehicle maintenance is one of those things people know they should track and consistently don’t — until something breaks. Service dates get missed, fuel patterns go unnoticed, and owners managing more than one vehicle have no system at all. The problem isn’t awareness. It’s friction. Existing tools were either too complex or too generic to stick.
What I was hired to do
Own the product as Product Owner inside an Agile Scrum team. Define what gets built, in what order, and to what standard — four months, production ready.
What I actually built
Owned the backlog from day one — user stories, acceptance criteria, sprint prioritisation, continuous refinement.
The app shipped supporting up to five vehicles per user — maintenance reminders, mileage and fuel usage tracking, vehicle performance metrics, and a built-in traffic signs guide for safer driving awareness. Each feature was evaluated against one question: does this reduce friction for a vehicle owner, or does it add to it?
The multi-vehicle architecture required careful data design — users needed to switch between vehicles cleanly, with each vehicle’s history and reminders completely separate. That structure was defined in the backlog before any development started.
QA cycles ran against real usage scenarios — not just feature checklists.
The result
A production-ready vehicle management app delivered in four months. Users could manage multiple vehicles, track maintenance proactively, and stay ahead of service schedules without effort.