NEST Pensions — Digital Transformation
Designing a member-centred future for the UK's largest workplace pension scheme
The Problem
NEST was at an inflection point. Auto-enrolment staging had ended, and the scheme that had been built to onboard millions of employers and workers as quickly as possible now needed to become something different. A service capable of delivering meaningful, personalised outcomes to those members over the long term. The infrastructure that had got NEST this far was not the infrastructure that would take it to the next stage.
The scheme's existing administration platform, in place since launch in 2011, had been designed for volume and accessibility. It had done that job well. But as NEST looked ahead, to a membership expected to reach one in three UK workers by the late 2020s, and to assets under management projected at £100 billion by the end of the decade, the limitations were becoming structural. The service needed to be rebuilt around the member, not around the mechanics of enrolment.
In 2019, NEST launched a £1.5 billion competitive tender for a new scheme administration partner. The brief was explicit. Digital technology had to play a central role, and the new service had to be capable of using data analytics to deliver a genuinely personalised experience to a membership that had, in many cases, never actively chosen to engage with their pension in the first place.
My Role
As Design Director, I led a cross-functional team through the full research and design phase of the project. That meant setting the creative direction, making the calls that shaped the work, and making sure the decisions coming out of research translated into a design response that genuinely answered the brief. Not just on paper, but for the people who would actually use the service.
The team brought a wide range of disciplines together: UX research, service design, interaction design, visual design, and content strategy. My job was to hold all of that together, keep it pointed in the right direction, and push back when the work wasn't at the level it needed to be. A project of this scale and complexity produces a lot of competing ideas and a lot of pressure to move quickly. The most important thing I could do was make sure the decisions were the right ones, not just the fastest ones.
Alongside the design work, I was heavily involved in shaping the documentation that governed how the partnership with NEST would operate. That covered procedures, methodologies, and processes. The structural layer that sits beneath the design work and determines whether what gets built in the concept phase actually survives contact with delivery. Getting that documentation right was as important as getting the design right. A strong service vision with weak operational underpinning rarely makes it through a procurement of this scale intact.
The Core Challenge
The hardest design problem on this project wasn't technical. It was motivational. NEST's members are, almost by definition, people who didn't actively choose to save. They were enrolled automatically by their employer, and for many, particularly lower earners and people with limited prior experience of financial services, the pension exists somewhere on the periphery of their financial lives. They're not hostile to it. They're just not thinking about it.
Designing a digital service that changes that relationship, without being paternalistic or overwhelming, is genuinely difficult. The brief called for personalisation and data-driven engagement, but personalisation only works if the underlying experience is trustworthy and the communication is clear enough to land with someone who doesn't know, and doesn't particularly want to learn, the difference between a fund and a pot. Getting that balance right, useful without being intrusive, clear without being condescending, was the tension that ran through every design decision we made.
The procurement context made this more complex, not less. The design work had to be compelling to two different audiences simultaneously. The members who would eventually use the service, and the expert evaluation panel assessing the tender. Those two things aren't always in conflict, but they require a different kind of discipline. You can't just design something that looks good in a deck. It has to hold up under serious scrutiny.
The Decisions That Mattered
The first decision was to treat inclusion as a design constraint, not a compliance exercise. NEST's membership is one of the most demographically diverse of any financial service in the UK. Low-to-moderate earners, people with irregular employment histories, members with limited digital confidence, people for whom English is a second language. Designing for that breadth meant accessibility had to be foundational. WCAG standards embedded into every component, plain language standards applied rigorously across all content, and an interface that didn't assume prior knowledge of pensions or financial products. This wasn't a late-stage audit. It shaped the work from the start.
The second decision was about where to put the research effort. The instinct in a project like this, particularly under the time pressure of a tender, is to move quickly to design. I pushed back on that. Understanding who NEST's members actually were, not as a demographic abstraction but as people with specific financial situations, specific relationships with technology, and specific reasons for disengaging from their pension, was the foundation everything else stood on. The personas and journey maps that came out of that research weren't just outputs. They were the reference point for every design decision that followed.
The third decision was about tone. Pension communications have a long history of being either impenetrably technical or relentlessly cheerful in a way that nobody trusts. I made the case that NEST's service should be neither. The right tone was honest, direct, and specific. Giving members information they could actually act on, at the moment it was relevant to them, without hedging it into uselessness or dressing it up in language that felt disconnected from their real lives. That principle ran from the interface copy through to the structure of the member dashboard and the way the service surfaced personalised prompts and nudges.
Outcome
The design work and supporting documentation fed into the formal tender submission through NEST's competitive dialogue process. The submission set out a clear service vision, member-centred, accessibility-first, and grounded in research, alongside the operational framework that would govern how that vision was delivered in practice.
NEST appointed Atos as its future scheme administrator in February 2021. The procurement had been one of the most rigorous in the public sector that year, and the bar for what constituted a credible submission was high. What the process confirmed, more than anything else, was that the investment in research, documentation, and operational rigour at the front end of the project was the right call. The work that holds up under that level of scrutiny is the work that was built on something solid from the start.