Redesigning 'Ways to Save' product
An existing OPower product that helps utility customers learn how to save energy in their homes
Launched in April 2016
Get utility customers to do energy saving tips in real life, thus driving energy efficiency on the plant.
• Prove the product is sticky
• See an increase in digital engagement on Ways to Save
• Get users to commit to doing tips on the platform as a indirect correlation to the tips being completed in real life
Lift average time users spend on Ways to Save
Utility customers return
Ways to Save is one of OPower's core products that helps utility customers learn how to save energy in their homes either by changing their daily habits or making home investments like purchasing an energy efficient refrigerator.
Redesign the experience for logged-in utility customers, focusing on the way in which they save tips and mark tips they have already done to boost engagement on the platform. What we called "Tip actions."
Studies show that people only spend 9 minutes per year thinking about their energy use. Through our own research, we know utility customers browse an average of two "tips" on Ways to Save.
Kick off meeting: Before starting any design work we work closely with the product manager to make sure we are all aligned on the goals of the product, the timeline we are working with, what is within scope, and who is our target user.
Therefore, we always set up a kick off meeting between the product managers, designers, and content strategy teams. We find it helpful to map out the existing journey of the product and to overlay where we saw the opportunity areas.
Brainstorm: I ran a brainstorm amongst the design and research team to get out all of our ideas on a wall. Narrowing down on ideas by voting on our favorites.
Wireframing: From the brainstorm, I wireframed out different concepts across the entire journey. We had a review with design leads to gather feedback before refining my designs.
User testing: With two clear design directions in mind, we conducted remote user testing with a range of utility customers.
Debrief: After 3 full days of remote user testing, we debriefed on our findings, whiteboarded what is working in order to narrow down on what we need to iterate on next before finalizing the designs.