When O2 becomes one

The challenge

In 2011, smartphones were reshaping what customers expected from their mobile provider. Customers wanted to check usage, understand bills and make changes immediately, but O2's digital products did not yet behave as one service. A journey could cross retail, My O2, identity, billing and customer service, each owned and delivered separately.

O2 Refresh raised the stakes by separating the cost of the phone from airtime. Once the phone was paid off, customers could upgrade, leave or continue with airtime without continuing to pay for the device. The promise was fairness and flexibility, but one familiar contract became two linked plans, two agreements and, initially, two payments.

I led the design of My O2 and O2 Refresh across web and mobile. The briefs arrived as separate projects, but together required a coherent customer relationship spanning access, purchase, billing, payments and upgrades.

What I uncovered

Even a simple task depended on identity, account, usage, billing and payment services working together. I mapped customer states across channels and underlying systems, including missing information and service failures. What someone needed to see or do next depended on their account, connection and stage in the relationship.

Working with another UX consultant, we mapped and prototyped O2 Refresh across the customer lifecycle, from understanding the two plans and accepting the credit agreement to managing payments, settling the device and deciding what to do next.

This exposed a critical launch gap. Customers would encounter Refresh in retail before My O2 could show and support the new plans. The existing dashboard still reflected the old contract model: customers could buy the proposition without a clear way to understand or manage it afterwards.

Testing with pay-monthly customers showed that most understood there were two payment streams, but not always how they worked together. Revealing the full phone cost could cause concern, while language intended to reassure could create suspicion.

The reframing

This was systems and service design: connecting the commercial proposition to the customer relationship before and after purchase. Clearer screens or tariff explanations could not resolve gaps between channels, systems and the capabilities customers needed.

My O2 and O2 Refresh needed one service model that made the customer's situation, commitments and next actions intelligible at every touchpoint.

That changed the design question from explaining every rule to understanding what the customer needed to know at that moment, and what would help them trust it. The same model could guide each platform while respecting the customer's context.

What I changed

Reducing effort through account context

On the O2 network, the SIM and device already provided an identity signal, so the service only asked for the additional proof it needed. Wi-Fi access required conventional credentials, while a security PIN simplified repeat visits.

The principle was minimum necessary effort: ask for information or action only when essential, and never request something the service already knows. My O2 prioritised allowances, recent charges, bills and next actions according to each customer's situation.

Karen was a pleasure to have on the My O2 App project team; Her attention to detail and determination to deliver an excellent customer experience shone through during the various tasks undertaken.

Making O2 Refresh understandable and manageable

We redesigned My O2 to show the total monthly commitment, distinguish airtime from device payments and connect the remaining balance to settlement and upgrade options. The proposition became something customers could manage over time.

Clearer definitions, worked examples and visible monthly breakdowns addressed the comprehension findings. I also designed an interactive calculator so customers could explore how upfront payments affected monthly costs. The launch proposition was not configurable enough to deliver the full experience; O2's later configurable plans offered that kind of flexibility.

Carrying one service across platforms and teams

I retained the service model across responsive web, iOS, Android and Windows Phone while adapting navigation and interactions to each platform. Web prioritised allowances, charges, bills and next actions; native apps offered deeper usage and billing views; Windows Phone used panoramas and pivots.

Working across product, research, design, technology, legal and operations, I translated account, payment and upgrade behaviour into journeys and interactive prototypes teams could test and improve together. This exposed missing capabilities and difficult hand-offs while giving delivery teams a shared model to carry across web and mobile.

She has a rare ability to accommodate various perspectives and help the teams to find simple and clear information architecture and user experience solutions in a very collaborative manner.

Outcomes

Customers responded strongly to O2 Refresh. In its first month, nine out of ten eligible retail customers chose it. By its second anniversary, 1.5 million customers were using the proposition, with estimated collective savings of up to £324 million as device payments ended.

My O2 also reached significant scale. More than one million people used the redesigned service in its first week. By the end of 2014, it had 3.6 million active users and had contributed to a 20% reduction in customer-service calls.

These were collective programme outcomes. My contribution was to help the teams see and design the customer relationship as one service, connecting the commercial model to an experience customers could understand and manage.