Loading case study…
Loading case study…
01Case study
FIVE Petroleum
Transforming a counter-based refuelling process into a connected mobile journey, from station discovery to digital payment and receipt.



Designing a mobile-first refuelling journey that brings station discovery, pump selection, payment, and digital receipts into one connected experience.
02The Challenge
The project presented an opportunity to simplify the experience by allowing customers to manage payment directly through a mobile application.
Design questionHow might we make the refuelling journey more convenient by reducing the need for customers to visit the counter to complete payment?
Conceptual reconstruction of the journey, not a research artefact. Highlighted steps happen away from the vehicle.
03UX Discovery
I participated in a collaborative UX discovery workshop with the Product Manager, stakeholders, and technical lead.
Understand the existing refuelling process.
Conceptual reconstruction of the workshop themes, the original workshop materials aren’t shown.
04Before vs After
Key design decisionMove the standard payment interaction from the physical counter into the mobile application.
Refuelling still happens at the pump. What changes is where payment happens: on the phone, from the vehicle, instead of at the counter.
05End-to-End Mobile UI
Following discovery and experience definition, I designed the core mobile journey from station discovery through to the digital transaction receipt.
The experience was designed to guide customers through the essential steps of a refuelling transaction.
Step 1 of 4
The nearest FIVE station is surfaced on the map with its distance, alongside the fuel price and wallet balance, one tap from Purchase fuel.
These are the published FIVE App designs, shown as designed. The in-app payment step sits between choosing an amount and refuelling; it isn’t shown as a separate screen here.
06Collaboration
After developing the proposed user flows and mobile interfaces, I participated in design walkthroughs with stakeholders, the Product Manager, and the development team.
These walkthroughs provided opportunities to review the proposed experience, explain design decisions, and discuss product and technical considerations.
In the walkthroughs
Conceptual diagram of how the walkthroughs connected design and delivery.
07Development & UAT
Stage 7 of 7
Reviewed the implemented app against the intended designs.
Design QA focus
Project statusThe application was developed and undergoing UAT when my involvement ended.
08Outcome
A cohesive mobile experience covering the core refuelling transaction.
Design work progressed through collaboration with product stakeholders and engineering.
Design involvement continued through development and UAT.
These are delivery outcomes, not measured customer or business impact.
09Reflection
FIVE App reinforced the importance of understanding the physical customer journey before introducing a digital solution.
By mapping the existing experience, collaborating with product and technical stakeholders, and remaining involved through UAT, I contributed to both defining the intended experience and reviewing its implementation.
The project demonstrated how product design connects customer needs, operational processes, interface design, and technical delivery.