Navigate, without compromise
DISCIPLINES
Product Design · UX Research · Product Strategy
METHODOLOGY
Job to be done · Lean UX How · Might We...
PROJECT TYPE
B2C · B2B · Native app
Non-disclosure agreement - This project is covered by a non-disclosure agreement. The full product name, client, and UI are not shown publicly. The case study - including design decisions, research findings, and process artefacts - is available to discuss in detail during an interview or upon request.
REDUCED RANGE ANXIETY
of enterprise customers rated cross-instance collaboration a top investment priority - ranked among the highest of 15 areas surveyed (EES, n=102 Cloud Enterprise customers)
RESERVATION-FIRST
of Jira Cloud users are non-technical business roles - the segment most likely to abandon the platform when hybrid friction makes it unworkable
MULTI-MARKET
of existing Atlassian research reframed - from infrastructure connectivity to human workflow, establishing The Process Creator as a primary underserved archetype
● CONTEXT
Designed for combustion. Inherited by electric.
Standard navigation apps were designed for combustion engines. They optimise for time and distance. For EV drivers, those aren't the only variables.
Range, charging speed, charger availability, wait times, real-time network status - all of these shape a journey in ways existing tools didn't account for. Drivers were making decisions based on incomplete information, arriving at chargers to find them occupied or broken, and replanning routes on the fly.
The goal was a navigation experience that treats charging as a first-class part of the journey - not an obstacle to route around, but a variable to plan with from the start
Navigation platform designed for EV drivers making journeys beyond their single-charge range - daily commuters, long-distance travellers, and fleet operators who need confidence in their route before they leave, not problem-solving once already on the road.
PROBLEM
What was broken?
Navigation tools gave EV drivers a combustion-engine experience in a charging-dependent world. Route planning ignored charger availability, speed, and reliability. Drivers arrived to find chargers occupied or broken - adding uncertainty to every long journey.
PERSONA
Who did we design for?
EV drivers making journeys beyond their single-charge range - daily commuters, long-distance travellers, and fleet operators. People who needed confidence in their route before they left, not problem-solving once already on the road.
HYPOTHESIS
What did we believe?
If drivers could see charging stops as part of the route - not additions to it - and reserve a charger before departing, range anxiety would decrease and journey confidence would increase. Certainty before the trip changes the experience of the trip itself.
How EV drivers plan trips today vs. the ideal state - mapping the gap between available tools and actual decision-making.
Reframing range anxiety as a planning and certainty problem, not a distance problem.
The full charging reservation flow - from route planning to confirmed charger slot, across all user types.
Interaction flows for the core journey planning and reservation experience - without UI.
What drivers, fleet operators, and city planners actually need from an EV navigation system - beyond getting from A to B.
Moderated sessions with EV drivers testing route planning and charger reservation flows against real-world trip scenarios.
● APPROACH
Range anxiety is a certainty
problem, not a distance problem.
The project started with one reframe: range anxiety is not a distance problem. It is a certainty problem. Drivers are not afraid of running out of battery - they are afraid of not knowing whether they will.
That reframe changed what the product needed to do. The navigation layer became secondary to the reservation layer. Getting to a charger on time mattered less than knowing the charger would be there.
Learnings & Challenges
How deeply entangled reservation and navigation logic would become. These are typically separate products built by separate teams. Treating them as one continuous flow required rethinking both the service blueprint and the product architecture at the same time.
Real-time charger data is unreliable across networks. Availability status is often stale. Rather than designing around perfect data, we designed for uncertainty - the system communicates confidence levels, not just binary available/unavailable states.
The reframe. Range anxiety is not a distance problem - it is a certainty problem. Once that shifted, every product decision followed logically: reservation before departure, confidence levels over binary status, charging surfaced as part of the journey rather than an interruption to it.
● LET'S WORK TOGETHER
Got a project?
Let's talk.
andpon - Andrzej Poniatowski
© 2026