Turning around a poorly performing customer experience for turning on and off service.
|
My Role
Senior UX Designer
Deliverables
Flows, Wires, Mockups, Prototypes
In the beginning, transactions for turning on/off or transferring service were not so great, to say the least.
The timing also allowed Move Center to be the first release with their new, responsive site design.
SCE had performed user testing on the existing Move Center (turn on, turn off, transfer service processes), which revealed several critical usability issues, the largest of which was a high rate of abandonment. People found it easier to just pick up the phone, which is a far more expensive channel. Customers often followed the wrong path, e.g., residential customers were using the different business channel to turn on or off service.
In reality, as a government regulated utility, SCE was responsible for accommodating almost everyone. But we had to narrow it down to a manageable number, so we developed four which represented different ages, socio-economic groups, and levels of engagement:
For each persona, customer journeys were expanded upon to show what each persona could go through to achieve their goal.
To develop the requirements, we employed several resources:
Basic flows were developed for each of the residential and business processes.
In the beginning stages, in addition to a single turn on/off/transfer service, SCE was contemplating Lifestyle Packages (bundles) for Move Center, where customers would choose a package that fit their lifestyle (Cost Cutter, Go Green, Quick Start, & Compare Plans). These packages bundled services, which the user would subsequently setup.
After consulting with developers, it was apparent bundles would present complications. So we created basic flows for discussions with dev.
Below are various flows that illustrate how this could be accomplished both with a single product or service, and then within a bundle:
It was important for SCE's digital team to develop consensus among the players. We went through several cycles of refinement in workshops, using our flows (and later, wires) as talking points.
To get everyone on the same page at the workshops, we used more detailed flows, in addition to as well a wires/flow combination that helps those less experienced with complex flows understand the process a bit easier. See the following examples, or view entire document.
After receiving feedback from each workshop, we refined wires and flows through many iterations. After each, we presented to the workshops.
Below is an evolution of the wires as requirements were refined.
A prototype that looked and felt like the final, built version was constructed, and both customers and employees were tested.
Most participants went through the process easily. No major problems.
42%
Increase in daily transactions within the first two weeks
Michael Blaser
User Experience
mike@mikeblaser.com