EO Cloud Redesign
Redesigning EO’s flagship fleet charging management system
EO Cloud is EO Charging’s cloud-based, vehicle-agnostic charging management platform built for fleet depots, offering real-time monitoring, remote diagnostics and automatic fault detection to ensure high charger uptime. It includes smart features like manual or automated scheduling, multi-level user access, and detailed reporting on energy usage, charger health and network status—all designed to minimize total cost of ownership.
When I joined EO Charging, I was the first and only product designer hire to redesign the outdated EO Cloud.
My role in this project
As the lead and sole product designer, I owned the entire design process for EO Cloud’s redesign. This encompassed:
Conducting UX research to pinpoint key usability pain points
Mapping user journeys and identifying where workflows broke down
Creating high-fidelity mocks and detailed design specifications
Collaborating with engineers through to implementation, ensuring design intent was faithfully translated into the live product
The problem we set out to solve
EO Cloud had long been flagged by both users and our engineering team for its outdated and inconsistent interface. Prior to my arrival, two different squads had built separate features using mismatched UI patterns. From my research, this has resulted in:
Inconsistency
Multiple parts of the app used different controls and visual styles, depending on the squad and timeline of development.
Redundant Screens
Two pages served nearly identical purposes, creating confusion and clutter.
Information Overload
Key data was crammed onto single screens, making it hard to scan or digest insights at a glance.
Poor Navigation
There was no clear way to backtrack or explore related views once a call-to-action was triggered.
Lack of Scalability
The existing layout had no room to accommodate future depot insights or expanded functionality.
My Approach
I started by seeking to understand how EO Cloud was currently being used, and what needed to change from a UX perspective. My goal was to identify user needs, pain points, and opportunities for improvement through qualitative research. These insights would ultimately guide and inform the direction of the redesign.
To do this, I took a multi-pronged research approach:
Heuristic UX Review
To evaluate the existing interface, I conducted a heuristic analysis to identify what was and wasn’t working in terms of usability, layout, and consistency.User Interviews
I spoke with depot managers and regional managers to understand their day-to-day workflows, needs, and frustrations with the platform.Internal Stakeholder Interviews
I interviewed account managers and internal support teams to get a broader perspective on client pain points and recurring feedback.Collaborative Workshops
I facilitated design workshops with both internal stakeholders and external clients to collaboratively surface insights, align priorities, and uncover hidden friction point
Depot page
These activities helped me identify key user groups, define their distinct journeys, and pinpoint their biggest frustrations—many of which are outlined in the problem statement above
Inconsistency
Multiple parts of the app used different controls and visual styles, depending on the squad and timeline of development.
Redundant Screens
Two pages served nearly identical purposes, creating confusion and clutter.
Network page
Information Overload
Key data was crammed onto single screens, making it hard to scan or digest insights at a glance.
Poor Navigation
There was no clear way to backtrack or explore related views once a call-to-action was triggered.
Lack of Scalability
The existing layout had no room to accommodate future depot insights or expanded functionality.
Findings - User problem
The three main problems users had were:
Will the fleet be charged in time to meet the customer and route demands?
Are my chargers working as expected across my network and depots? Are there any trends or issues that need to be brought to my attention?
Are my chargers being serviced, maintained and supported? What is the status and resolution time for known issues?
Findings - Key user group
There are three main user groups for EO Cloud.
DEPOT MANAGER
I'm a senior member of staff within the depot.
I’m responsible for the day-to-day operations of the depot.
I'm accountable for ensuring the fleet departs the depot at the correct time, with the correct State of Charge.
DEPOT OPERATIONS STAFF
I'm an operations specialist, within a team.
I'm responsible for supporting daily operations and vehicle movement within the depot, including coordinating vehicle arrivals, departures and allocating charge points.
NETWORK MANAGER
I'm a senior member of staff within the organisation.
I'm responsible for network wide operations, scalability and the wider electrification journey.
I need to see network insights, such as depot with faults and trends.
Findings - Key user journey
After an account is created, the EO Cloud user journey can be broken down into three core steps:
Network Overview
Users need to quickly view their entire network of depots across the country and identify any that require immediate attention—such as depots with offline or malfunctioning chargers.Depot Drill-down
From the network view, users can select a specific depot to explore in more detail, usually triggered by an alert or anomaly.EVSE (Charger) Details
Within a depot, users can inspect individual EVSEs (chargers) to understand their status, performance, and any associated issues.
Designs
Based on the research findings and the key user journey, I created the first draft of the redesigned EO Cloud interface. I prioritised screens that directly supported the critical user flow—from network overview to depot and charger-level insights.
My design goals were to:
Simplify navigation and make it easier to move between levels (network → depot → charger)
Introduce visual clarity and hierarchy to reduce information overload
Ensure consistency across the product by establishing a unified design language
Create space and structure for future features and insights, making the platform more scalable
Video of the designs
Network Overview page
This is the entry point to the EO Cloud experience. Users can view their entire depot network in either a map or list format, depending on their preference.
Faulty depots are clearly flagged for quick identification on the map and through the insights
Users can click into any depot to access more detailed information
Filters enable users to quickly sort and find depots based on criteria such as location, issue type, or charger status
To address previous scalability issues, the layout was redesigned with a map on the left and dynamic insights on the right. This structure allows us to surface critical data alongside spatial context—and gives us room to scale the interface as more features or data layers are introduced.
Depot drill down page
Once a user selects a depot, they’re taken to a detailed view showing all the chargers at that location.
Chargers are displayed in map or list view
Faulty chargers are clearly highlighted for fast triage through the map and the insights
Users can click on any charger to view in-depth status
Filters enable users to quickly sort and find chargers based on status
EVSE (Charger) details page
This page provides detailed information about an individual charger (EVSE).
Users can see key charger metadata and current session info (if a vehicle is plugged in)
Any incidents or errors related to the charger are clearly listed
Designed for quick troubleshooting and coordination with on-site teams
Feedback
We presented the redesigned EO Cloud to depot and regional managers from two of EO’s clients, including one of the UK’s largest bus operators and a major delivery corporation.
The feedback was overwhelmingly positive, especially around clarity, usability, and the ability to take quicker, more informed action:
“It’s so much easier to work with now. Being able to quickly understand the state of my overall network—and know exactly which depot needs attention and who to call—is a game changer.” (Regional manager, delivery corporation)
“When buses aren’t charged because of a faulty charger, it throws off the whole schedule for the day. Now, we can see every morning if there are any issues at a glance and plan accordingly.”(Bus depot manager)
There were also valuable suggestions for further improvements, especially around daily operational insights:
“It would be helpful to have a morning summary showing which chargers are in use, underused, or broken—so I can plan the day properly.”
These insights helped guide the next iteration of design, particularly in how we presented charger-level data and daily summaries for operations teams.
Implementation plans & challenges
One of the key challenges during implementation was that we couldn’t afford to pause the product or create a completely separate version. We needed to introduce the redesign gradually—without disrupting the user experience or overloading the engineering team.
To address this, I worked closely with our solutions architect to plan a phased rollout of the new design. Our goal was to:
Ensure no interruptions to the existing user workflows
Seamlessly integrate new components alongside legacy ones
Minimise technical debt and avoid duplicating design systems
Make the transitions feel intuitive and natural to users
We broke the redesign into manageable batches, prioritising high-impact screens tied to the key user journey. Each release was designed to work cohesively with existing UI elements until the full transition was complete.
