Web App
UX Design
UI Design
EnergyBot
UI & UX Design, Prototyping, HTML, CSS
Design (Me), Head of Product (1), Head of Engineering (1), Engineers (5)
The prior version of the dashboard was intended to be experimental.
It's goal was to determine if users found value in our tools.
Despite receiving a decent amount of traffic, we hadn't been seeing users engage much with the tools available on our dashboard.
Most users came to this page after searching "ESID Lookup" in Google and entering their address on our ESID Lookup landing page.
Based on my analysis of user sessions in FullStory, there were 4 clear issues that stuck out to me while putting myself in the shoes of the user.
> 100 sessions
Scroll up and down, then bounce
4-8 seconds
Users were coming for one simple piece of information, but are immediately overwhelmed with multiple things they didn't ask for.
All of the widgets are roughly the same size and don't have any attention-grabbing CTAs.
We weren't communicating the important info to users intuitively.
While technically this iteration of the dashboard was mobile responsive and nothing broke, the experience still wasn't ideal.
The user's viewport fit 1-2 cards at a time, so it wasn't overwhelming, but navigating between features was cumbersome and frustrating.
We designed the dashboard this way to save time, so this finding wasn't exactly surprising, but still important.
When we introduced this version of our dashboard, our goal was to identify which of our tools users found interesting or useful to direct future product development.
By the nature of the beast, this meant that each tool was an MVP, and thus the experience was rather shallow and didn't provide much real value to the users that did decide to interact with one or more of our tools.
After discussing my findings with our Head of Product, I refined our product features based on their relevance to users.
This included sunsetting any features that were adding more confusion than value.
ESID Lookup
Login / Create Account
Shop
Tools
Emails
Guests
Logged in Users
Single Location
Multi-location
Residential, Business, or Both
I also needed to account for where users were coming from on our site, as well as how their experience may differ between different paths to our dashboard.
Property Details
Your Plans
Your Usage
Green Energy
Incentives
Bill Comparison
Shop for Plans
Shop for Solar
Shop for Equipment
Flatten Your Bill
Dashboard
Usage
Shop
Tools
Orders
Notifications
Settings
My next objective was to redesign our existing product features, as well as design any missing features that a user would expect to find on their dashboard.
Scalability
Maintainability
Improved Product Reception
Faster development speed
Shared Ownership
I created high fidelity prototypes of every possible dashboard scenario for both our smallest desktop and mobile screen sizes.
However, after an extensive series of review sessions with our dev team, we determined that we needed to de-scope the project to deliver an MVP within a reasonable amount of time.
Notifications
User Profile
Settings
Location Management
Shop Equipment
Tools
While increasing engagement with our tools was one of our initial goals, we decided to use the MVP as an opportunity to test if the redesign itself was enough to increase our click through rate.
Basically, were users more interested in the tools? Were they more willing to engage with us now that we refined the user experience?
With final approval from our dev team, I began building out styles and components for the dev team to use once they laid the foundation for the new dashboard.
Development of this new dashboard and its associated framework changes took about 2 months of focused effort from all team members to complete.
Bug fixes took about another 2 months in-between other projects following the completion of this MVP.
Now that we weren't bombarding users with information and simplified our approach, users were given the space to be curious and explore what we had to offer.
With what I consider key dashboard features missing, it was hard to be happy with the initial release.
But as they say, done is better than perfect. And with our initial goal accomplished, I'd call this a success!
