Problem - Household users
Households did not have the same equipment, goals or level of energy understanding.
A personalized dashboard by household profile
We were offering the same dashboard to all households, whether they had a solar panel, a battery or just a socket.
I built an experience that adapted to each household's profile: equipment, goals and level of understanding, so that the displayed data would make sense to the person reading it.
Context
I led
DiscoveryProblem framingPrototypingUX flowsCross-team alignmentTests & impact
Team
Product - Engineering - Grand compte clients - Sales
Challenge
Make energy data useful to every household, whatever their equipment or level of understanding.
Year
2018
Timeline
4 months
Tools
Figma, Notion, Storybook, Zeplin, Illustrator
Result
Frame the problem
Exploration and Solution
Organize by need
Create dedicated sections: save, understand consumption and track production
Promise
User language and goals more visible
Reasons for dropping
Some intentions were still not resolved
Personalize by profile
Generate a dashboard adapted to the household's equipment, goals and level of understanding
Promise
Response adapted to every household
Accepted risk
A more rigorous onboarding to design
Progressive reveal
Keep a single view, but progressively reveal useful explanations and indicators
Promise
Quick to set up and non-invasive
Reasons for dropping
It solves comprehension levels but not setup differences
Key decisions
Adapt the dashboard to the household
Because the same dashboard could not be useful to households with different equipment, motivations and levels of understanding.
Avoided cost
A view that was too generic
Avoided cost
Modules that were not very useful
A profile to explain
Accepted cost
Variants to maintain
Accepted cost
Let users adjust it
Because an initial profile could help at the start, but should not lock users into a frozen configuration.
Avoided cost
Frozen personalization
Avoided cost
Needs poorly covered
More interface states
Accepted cost
More complex logic
Accepted cost
Translate energy data
Because households were not looking for raw data, but for a clear explanation of their consumption and savings.
Avoided cost
Data that was not understood
Avoided cost
Value that was not visible enough
More UX writing
Accepted cost
Levels to manage
Accepted cost
The impacts
Personalization improved the dashboard's key signals: initial attention, retention and understanding of value.
The first visit became more relevant
with lower bounce and more time spent on the dashboard
Interest held better after discovery
with D7 and D30 retention increasing on personalized profiles
Value was better perceived
with savings-related modules consulted more often
Temps nécessaire pour obtenir une réponse
The dashboard held attention better from the first visit.
Bounce rate
48%
36%
Time on dashboard
41 sec
54 sec
D7 retention
More users came back after the first week.
26%
34%
D7 retention
D30 retention
Personalized profiles maintained interest better after one month.
09%
14%
D30 retention
Module interactions
Modules useful to the profile were consulted more often.
22%
34%
Module interactions
Retrospective
Design one view for everyone
Adapt the visible value to the user's context
Organize the interface around the product
Organize it around what the user is trying to understand
Measure only global engagement
Compare signals by profile, module and usage moment
