GE Energy Data Cleaning Web Application
Prototype
https://xd.adobe.com/view/4083fe00-f193-4d8b-77ab-85fb2c6aae2b-36b2/
Before we embark on the journey....
Overview
EverComm is a B2B startup that provide end-to-end energy managemnet solutions for enterprise. These solutions include energy data collection, data migration, data analysis and insight reporting.
Role
My role for this project is a UX/UI designer. This includes User Research, Visual Design and Prototyping.
Goal
The goal of this project is to improve on the usability and intuitiveness of the Web Application for a better user experience.
Alright! Let's get going!
Process
The workflow of this project is as follows:
Stage 1: Discover Painpoints
In the Discover stage, I came up with a problem statement that this project will be addressing and uncovered the potential painpoints that the users might be facing.
Stage 2: Define Requirements
With the help of my software developer, we came up with a user interface that is aligned to both functional and application requirements as well as maximising the usability of the project.
Stage 3: Develop Mockups and Prototype
After finalising the requirements, I commenced the generation of mockups, starting from sketches to high fidelity mockups and finally a prototype.
Stage 4: Testing and Feedback
Once the design is approved, feedback was gathered from my software developer to see what can be improved.
Defining the Problem Statement
We want our users to conduct their research work with full confidence in their data processing tools without a single ounce of doubt.
Clients have large amounts of raw data to process. Processing raw data into useful information takes a considerable amount of time and effort. Ignoring this problem will be detrimental to our company's goal which is to provide energy management tools for our users.
Uncovering Users' Painpoints
I utilised the user flowchart to unearth painpoints that the users might face and also consulted my supervisor and software developer to gain more insights of our target users.
I studied the User Flowchart above and derived 5 pain points that the user might face when using the Web Application.
Table of Findings
Defining Application Requirements
My software developer had defined the application requirements and handed over to me a crude version of the Web Application. I have to centralise my design based on this crude design.
Crude Version of Web Application
Here comes the fun part! Designing Mockups!
I started off with rough sketches of the whole Web Application. These sketches went through several revisions which is based of feedback from my software developer.
After finalising on the design on paper, I utilised Adobe XD to create a High Fidelity version of the Web Application.
A prototype is then created from this mockup and sent to the developmental team for development.
On to the next iteration!
My software developer came back to me with more features to be added into the existing web application. Here are the features and my brainstorming process. I consulted my software developer on the design of the new features.
Once approved, I started designing the new features into the existing design. I added the new features into the existing Adobe Xd file.
In Conclusion
Unfortunately, the project was not rolled out because the client did not see the need to use this web application. Here are some lessons I learnt throughout this whole project.
1) More preliminary user research have to be done to really dial down on what issues the end users are facing so that we can address them. Research such as competitors analysis and qualitative surveys can be done.
2) More user testing should be done to gather more insightful feedback on the usability of the project.
3) Several iterations are needed before a project is considered fully functional and bug-free.
