Structuring the EV Charging Management System for Efficiency and Scalability

Uncovering Issues and Enhancing UX

Role

System analysis,UX Documentation, IA,UX Strategy,Usability testing

Software used

Notion, Figma, Jira

Duration

6 months

Overview

Our customer,GOEC aimed to transition from third-party CMS(Charging Management System) dependency to an in-house system tailored to their workflow. However, before development could begin, the system lacked:

- Lack of structured navigation – Users struggled with an intuitive workflow.
- Usability issues – The system had significant UI/UX flaws that affected efficiency.
- Scalability concerns – It lacked a framework that could accommodate future growth.
- No documentation – The absence of structured references made development challenging

Overview

My Role

With the Charging Management System still in the pre-development phase, my role was to ensure a structured and development-ready system. This involved extensive documentation, restructuring information architecture, refining UI inconsistencies, and setting a UX strategy for future scalability.

My First Challenge – Understanding the System

Before jumping into solutions, I needed to understand the system from the ground up.
Since there was no existing documentation, I took a reverse-engineering approach, breaking down every entity, function, and interdependency to visualize how the system worked.

How the system works?

Deep-dive into the process

By doing this exercise, i was able to identify gaps and errors in the current system which was either corrected or planned as upcoming upgrades.

Click to view the process

Here is the preview of the Web-app

Documentation

Due to its complex terminology, a detailed description of the design was necessary to communicate with the developers and the team. Every screen and its flow was explained in detail. Below are the snippets of the complete documentation of the project done in notion.

Transitioning to Development – Testing, Fixes & UX Strategy

With development underway, my role shifted to ensuring that the system functioned as expected. This involved:

- Conducting usability testing to uncover friction points.
- Fixing UI/UX inconsistencies to enhance user interactions.
- Developing a UX strategy to future-proof the system.
- Collaborating with developers to implement key UX improvements effectively.

Usability testing helped uncover unexpected friction points—small UI inconsistencies, unclear interactions, and moments where users hesitated. Addressing these early saved costly redesign efforts later.

Testing

The testing process was conducted using Jira to track issues and manage the workflow. I was responsible for:

Identifying Bugs: Systematically identifying and documenting bugs in every section of the product. this was done by using JAM for bug reporting.
Issue Tracking: Follow up on bug fixes, ensuring that all identified issues were resolved before the system's release.
Regression Testing: Conducting regression tests to verify that recent updates and bug fixes did not negatively impact existing functionalities.
User Acceptance Testing (UAT): Collaborating with stakeholders to conduct UAT, ensuring the system met user requirements and was ready for deployment.

Results

Through systematic testing and detailed issue tracking, we were able to identify and resolve key bugs in the CMS. The result was a robust system ready for deployment, with improved reliability and user satisfaction.

Reflection

Participating in the testing of the CMS provided invaluable insights into the importance of thorough validation in system development. The experience reinforced my belief in the necessity of iterative testing and close collaboration with developers to deliver a high-quality product.