Energy industry
Redesigning data workflow that helped win a customer contract
Notes: Please be aware that some parts of this project have been modified or omitted to respect a non-disclosure agreement.
Project overview
Phasor analytics is a Windows-native data visualization software that helps scientists and engineers who work in the power grid by analyzing existing data and predicting future trends.
This project focuses on establishing a smoother way to upload, compare, and predict future energy data.
Impact
Faster data workflow. By understanding and breaking down complex engineering processes, my design improved data workflow efficiency by 50%+, helping users spend less time on manual processes and more time on meaningful work and future planning.
Won the bid and secured a customer contract. The product successfully secured a customer contract, with the design being highlighted as a key factor in the decision.
Timeline
About 2 weeks
Role
Working closely with product owner, research, design new workflow, prototyping and presenting.
Team
Product owner, UX manager and me
Before
Pain points
1
The existing flow only supported one file upload, slowing users down.
2
Creating or modifying data wasn't supported, users had to switch to a separate process entirely.
3
The data matching process lacked clarity, leaving users uncertain whether they had selected the right data sets.
After
Improvements
4
The new flow supports uploading multiple files at once, significantly speeding up the process.
5
Users can now add and modify datasets directly, with a more detailed preview.
Understanding the background
On day one of the kick-off meeting, I met the product owner and spent almost an hour discussing the product and the project needs. I created a few artifacts as a summary and guide for my design process.
Design iterations
On day one of the kick-off meeting, I met the product owner and spent almost an hour discussing the product and the project needs. I created a few artifacts as a summary and guide for my design process.
Iteration 1
Allow updating multiple data, edit and create new model
1
File locator: Provide four slots for a user to upload data sets.
2
Edit/New model: To edit existing file, create new model (data sets).
3
4
5
Process for edit/new: A series of actions needed when creating a new model or editing existing model
1
Save: save a new document for editing process
Iteration 2
After completing iteration 1, I presented it to the product owner. I incorporated his feedback into the updates.
7
Edit/New function: Separate edit and new into two paths, no confusion for users.
8
New model: Title to show user where they are, which process they’re in.
9
Instruction: Explanation text for users who aren’t familiar with the process.
10
Save: Move it to the bottom area of the screen, as this is the last step.
Prototype
Visual concept
One of the next steps I see is that this legacy app can benefit from a visual redesign.
Result & Retrospective
The product successfully secured a customer contract, with the design being highlighted as a pivotal feature.
Communicate early and often. I send out multiple updates and hold meetings during the two weeks working with the stakeholders. Initially, I was a bit unsure if it was too much. Later, I asked for specific feedback and reflected on it. Those short and sometimes brief sync ups helped me stay on the same page with everyone and ensure that the design is delivered on time.
