WENDY REDSHAW - Chief Digital Information Officer, Retail, NatWest Group

Trust, Transformation, Technology & Beyond

Sponsored By

As she prepares to step down from one of the most demanding roles in banking, Wendy Redshaw reflects on eight years of transforming NatWest’s retail technology from the inside out.

There’s a version of this story that writes itself: a senior technology leader at one of the UK’s biggest banks; a decade of digital transformation; cloud migrations; legacy modernisation; 19 million customers; and 96% of their needs now met through digital channels. Tick, tick, tick.

Wendy Redshaw isn’t interested in that version. “What I’m most proud of isn’t any single piece of technology or programme,” she says. “It’s how we’ve brought everything together to create something that feels cohesive and genuinely impactful for our customers.” I interrupt briefly to add a line that is often true of these types of interviews: “The technology is often the easier part.” It’s a line we both return to more than once, not as a throwaway expression of humility, but as a conviction she has spent the better part of her career building evidence for. As CDIO of NatWest Retail Banking, Redshaw has led a wide-ranging transformation spanning the full customer and technology landscape, from the mobile app millions rely on for everyday banking to the evolution of the underlying platforms that now enable real-time, always-on, and increasingly personalised services.

She has navigated regulatory pressure, the seismic shift to public cloud, and the cultural change that all of the above requires. She has also consistently put people at the centre of it all. Leading by example, with a real openness that I have witnessed in person, she creates a sense of trust that can be felt throughout the room as she speaks: honestly, often excitedly, and always with an ability to convey her message to all levels of expertise, often through an analogy about gardening, cars, or some other laypersons terms.

That tension, between the relentless demands of enterprise technology and the fundamentally human work of leadership, is where this conversation keeps landing. And it’s what makes Redshaw’s perspective worth listening to, particularly now, as the industry grapples with AI’s arrival in the enterprise, the ongoing challenge of legacy modernisation, and the question of what kind of leaders the next era of banking technology actually needs.

“One of the biggest lessons in being a leader is that you don’t get to decide whether you’re a role model, or whether you influence or positively impact someone. Others make that decision about you for themselves, often when you’re not even aware of it.”

How You Show Up

Ask Wendy Redshaw about her leadership philosophy, and she doesn’t reach for a framework. She talks about behaviour. “Leadership is about how you show up,” she says, “and the behaviours you choose.” It sounds simple. It isn’t. Redshaw has been thinking about this since the early stages of her career, navigating an industry that, for much of its history, equated technical seniority with authority, and authority with the need to have all the answers. She rejected that model early, not as an ideological position, but because it didn’t work. “One of the biggest lessons in being a leader is that you don’t get to decide whether you’re a role model. You just are one. That changes how you think about every interaction.”

What followed from that realisation was a set of commitments that now define her leadership identity: radical candour, authenticity, and a genuine investment in the growth of the people around her. These aren’t soft concepts at Redshaw’s level. In an organisation as large and complex as NatWest, where decisions made in technology functions have direct consequences for millions of retail customers, how a leader behaves under pressure matters. How they communicate, how they handle failure, and how they respond when things go wrong shape organisational culture in ways that no strategy document can.

“Being open and clear really matters,” she says. “And authenticity is vital to building the trust you need to truly lead at this level.” She is careful to distinguish between growth and performance. Leadership, she argues, stretches you, but it shouldn’t require you to become someone you’re not. This isn’t abstract. For Redshaw, it has practical consequences for how NatWest Retail Banking recruits, develops, and retains technology talent. In a competitive market where experienced technologists have no shortage of options, culture is a real variable. The kind of environment you create, whether people feel safe to speak up, to fail, and to learn, determines who stays and who leaves, and, by extension, what you can build. “Some of the most formative experiences have come when things didn’t go smoothly. I’ve spent time challenging the status quo and surfacing assumptions that need to be addressed.”

Trust as Infrastructure

If there’s a single concept that runs through everything Redshaw talks about, it’s trust. Not trust in the abstract, motivational-poster sense. Trust is something operational, as hard to build as a core banking system and far easier to destroy.

She means this at every level: the trust of customers, regulators, colleagues, and the trust that defines the relationship between NatWest and its technology partners. Each of these is distinct in its nature but connected in its consequence. Lose one, and the others weaken.

For retail banking, customer trust is existential. The relationship between a bank and its customers is built on a promise that is, at its core, a technology promise: your money will be where you expect it to be. The system will work. When you need access, you’ll have it. When something goes wrong, it will be fixed. The digital transformation of retail banking has raised the bar for what it takes to fulfil that promise, and the stakes for what it costs when itfalls short.

Redshaw describes trust as something you build through four things: “tending, consistency, clarity, and authenticity.” It’s a formulation worth unpacking. Tending suggests ongoing effort, and the recognition that trust doesn’t maintain itself. Consistency is the operational reality. You can’t be a different bank on different days. Clarity means people know what to expect from you. And authenticity is the thread that holds the rest together, because it is the quality that makes the other three credible.

In practical terms, trust is the foundation on which every other transformation initiative runs. NatWest serves 19 million customers. The decisions Redshaw and her teams make about system architecture, cloud migration, data governance, and AI deployment are not made in isolation. They are made with that number in mind, and with the understanding that each of those customers has, on some level, extended a form of trust that the bank must continuously earn.

“When you design and engineer things well, great experiences and strong security go hand in hand.”

That statement cuts against a persistent industry assumption: the idea that security and convenience are inherently in tension, and that you trade one for the other. Redshaw doesn’t accept the trade-off, and her teams have spent years working to solve for both.

“Ultimately, the biggest shift has been in mindset. There’s now a much stronger sense that everyone, wherever they sit, is connected to delivering value for customers.”

The Art of Doing Both

One of the most persistent myths in enterprise technology is that transformation and stability are opposing forces. You can either modernise aggressively or run a reliable operation, but not both simultaneously. This tension is not theoretical. It is a daily operational reality.

Redshaw has a clear view on it.

“Historically, organisations felt they had to choose between running the bank and transforming it. What we’ve leaned into is doing both - maintaining critical systems while continuously renewing and modernising them.”

This is harder than it sounds. Legacy modernisation in banking is genuinely one of the most complex challenges in enterprise technology. These aren’t outdated software packages you can swap out over a weekend. They are deeply embedded, often interdependent systems that carry the full weight of regulatory obligation, customer data, and operational continuity. Every change carries risk. Every migration requires sequencing. And the business needs to keep running and developing while you’re doing it. “Legacy platforms don’t disappear overnight,” she says. “So we carefully manage how services are transitioned and, ultimately, retired.” The approach she describes is methodical rather than transformational in the big-bang sense. The direction of travel is clear; the pace is deliberate. “You need a clear direction of travel, but you don’t want to lock yourself into the wrong solution too early.”

This is wisdom that is easy to state and genuinely difficult to operationalise amid heightened expectations for pace and vendors pitching “silver bullets”.

The discipline it requires, the ability to hold firm to a strategic direction while remaining genuinely flexible in execution, is a form of organisational maturity that many enterprises are still working towards.

What does that look like in practice? Redshaw points to NatWest’s decision to move the mobile middle tier to the public cloud as one of the defining moments of the retail technology transformation. At the time, it was a pioneering move for a bank of NatWest’s scale and regulatory profile. The mobile channel had become a primary touchpoint for customers: the place where the relationship happened, where trust was built or broken, and where the experience of digital-native challengers was increasingly setting expectations.

Moving that tier to public cloud was not simply a technical decision. It was a signal about the direction of travel, and it required building confidence within the team, with regulators, and across the most senior levels of the organisation.

It worked. And it set a template for how subsequent transformation decisions would be made: with technical rigour, commercial discipline, and a clear line back to the customer outcome that justified the risk.

“I’m most proud that we’ve made meaningful progress across multiple dimensions: technology, operations, customer experience, and culture. We’ve brought them together in a way that delivers at scale, safely and consistently.”

What Customers Actually Want

Serving retail customers at NatWest’s scale is no one-size-fits-all task. The range in demographics alone means that what is useful or convenient for one customer may not be right for another. That said, the majority of the customer base has now adapted well to the new, technology-based future of banking, with expectations rising all the time.

“Customer expectations have absolutely moved on, and rightly so.”

The arrival and rapid growth of challenger banks, nimble, digital-native, and unburdened by legacy infrastructure, has done something important to the market, not just by taking share, but by shifting the reference point for what “good” means. When a customer can open an account in minutes, receive real-time spending notifications, and get instant customer service via in-app chat, the experience of a traditional bank that requires them to visit a branch to update their address starts to feel like a deliberate inconvenience.

I don’t pretend otherwise. A NatWest customer myself since childhood, I interject briefly with a reminder of the importance of the trust and security that a traditional bank like NatWest exudes. I then share a more pointed and personal recent interaction with a well-known challenger bank I had been recommended for my business banking, only for it to freeze my account after receiving an international transaction, leaving me unable to access my funds for days. In short, when I needed the security and support of a traditional bank, it just wasn’t there. To compound matters, the only route to resolving the issue was via an AI chatbot. Not a human in sight.

It’s an anecdote that illustrates a real dynamic: challenger banks have raised the bar on digital experience while sometimes under-delivering on the trust, resilience, and customer service that established institutions, with all their regulatory weight and operational complexity, are built to provide. The future of retail banking isn’t challenger versus incumbent. It’s a hybrid, where seamless digital experience and the backstop of institutional trust coexist in the same product.

For NatWest, that hybrid is what the transformation is pointing towards.

“Customer expectations now demand a balance of seamless digital experiences with the security of traditional banking.”

This is not marketing language. It is an architectural constraint. Building an experience that feels as frictionless as a fintech experience, while maintaining the operational resilience, data governance, and fraud protection of a regulated institution, requires the entire technology stack to work in the same direction.

The numbers tell part of the story: 96% of customer needs are now met through digital channels. That is a fundamental shift in how millions of people interact with their bank, and it has happened over a relatively short timeframe. Behind that number is a redesign of the digital estate, a rethinking of how products are presented and accessed, and a cultural shift in how NatWest thinks about the customer experience.

“What I’ve tried to do is reframe that, moving from ‘we can’t do this’ to ‘how might we?’”

That reframing is deceptively powerful. In large organisations, “we can’t” is often a category error. It conflates genuine technical or regulatory constraints with institutional inertia, risk aversion, or a simple lack of imagination. By insisting on “how might we?” as the default question, Redshaw has pushed her teams to distinguish between the two and to spend their energy on the latter, rather than treating it as the former.

Operational Resilience, Rebuilt

There’s a version of “operational resilience” that reads like a compliance checklist: incident response plans, recovery time objectives, and business continuity documentation. Wendy Redshaw recognises the need for those things, but is less interested in that version.

“Operational resilience is about being relentlessly focused on the detail while never losing sight of the customer impact.”

The two things are in productive tension. Detail without customer impact produces technically correct decisions that miss the point. Customer impact without detail produces ambition that collapses on contact with operational reality. The skill, the thing Redshaw has spent years building into the culture of her teams, is holding both simultaneously.

One of the most significant cultural shifts she describes is the move away from a blame culture. In financial services, where regulatory scrutiny is intense and the consequences of failure can be severe, blame cultures emerge naturally. They are, in one sense, rational: accountability matters, and in a regulated environment, being able to demonstrate that accountability is a real requirement.

But blame cultures have a cost that is not always visible on the balance sheet. They suppress information. They create incentives to hide problems rather than surface them. They punish the candour that makes organisations resilient.

“One of the most important shifts we’ve made is moving away from a blame culture.”

What replaced it? A culture built on shared ownership: the idea that outcomes belong to the organisation, not to individuals, and that the job of leadership is to create the conditions under which problems get surfaced, addressed, and learned from rather than concealed and repeated.

“We design our platforms to be highly monitored and, increasingly, self-healing.”

This is a technical statement with a cultural dimension. Self-healing systems require teams that are willing to build and share the feedback loops that make them work. In a blame culture, those feedback loops get suppressed. People don’t instrument things they’re afraid to see fail. The move to self-healing architecture is, at one level, a cloud-era engineering approach. At another, it’s a cultural declaration: we expect things to go wrong, we design for it, and we use every incident as data rather than as a verdict.

The regulatory dimension matters here too. NatWest operates under some of the most demanding technology resilience requirements in the industry, and the regulatory environment has continued to intensify. Operational resilience is not a nice-to-have. It is a condition of operating. Redshaw’s approach has been to treat that constraint not as a ceiling but as a design parameter, building resilience into the architecture from the start rather than retrofitting it as an afterthought.

“It’s clarity of intent, flexibility in execution, and a relentless focus on delivering value safely.”

That formulation — clarity of intent and flexibility of execution — comes up more than once. It’s a principle that applies from system architecture to team culture to partner relationships. The intent is fixed: serve customers well, maintain their trust, and keep the bank running. How you get there needs to adapt constantly.

“Operational resilience, for me, is about being relentlessly focused on the detail while never losing sight of the customer impact.”

The Partner Question

NatWest doesn’t build everything itself. No bank at this scale does. The technology ecosystem is a network of strategic partnerships: cloud providers, software vendors, system integrators, and specialised technology firms whose capabilities are woven into the architecture of the bank’s operations.

Redshaw is precise about what she is looking for in those relationships, and it starts with a concept that might surprise people more accustomed to thinking about technology procurement in transactional terms.

“The first quality I look for, both in internal teams and strategic partners, is shared

ownership.”

Not delivery capability. Not price. Not features. Shared ownership. The willingness to be invested in the outcome, not just the contract. This distinction matters more than it might appear to. In complex technology transformations, multi-year, multi-system, multi-partner programmes, the moments of greatest risk are rarely the ones that appear on the project plan. They are the edge cases, the unexpected dependencies, the regulatory questions that emerge halfway through a migration, and the incidents that require everyone in the room to think rather than contract-manage. In those moments, the quality of the partnership is revealed.

“You need partners who are genuinely invested in the outcomes you’re trying to achieve, and who are on the journeywith you.”

This is a deliberate move away from the transactional model that has dominated enterprise technology procurement for decades, in which the statement of work, the milestones, and the exit clause define the relationship. Redshaw’s model is relational rather than transactional, and it requires something from NatWest as much as from the partner: clarity of intent, openness about challenges, and a willingness to share the context that makes partnership meaningful.

It also changes how performance is measured. In a transactional model, success is delivery against specification. In a shared-ownership model, success is measured by outcomes: customer experience, system resilience, and cultural impact. The specification is a means, not an end.

“For me, one of the biggest shifts has been moving away from viewing technology providers as suppliers, and instead building true partnerships. In a banking environment, where scale, security, and trust are critical, success can’t be driven by contracts alone.”

The Mindset Shift ThatActually Mattered

Ask most CIOs what drove their digital transformation, and you’ll hear about technology: cloud platforms, API architecture, microservices, DevOps. The tools are real, and the decisions matter. But Redshaw is unusually consistent in pointing elsewhere.

“Yes, digital transformation includes these things, but the biggest shift has been in mindset. There’s now a much stronger sense that everyone, wherever they sit, is connected to delivering value for customers.”

That sentence is worth pausing on. In a large enterprise, the psychological distance between an engineer building a microservice and the customer whose money is moving through that service is considerable. The meetings, the layers of management, and the abstraction of technology work from its human consequences are structural features of large organisations. Over time, they tend to produce people who optimise for their local objective rather than thesystemic one.

Getting everyone in a technology organisation genuinely connected to customer outcomes is harder than any cloud migration. It requires a consistent narrative, repeated in every context. It requires leadership behaviour that models the connection: leaders who talk about customers in technical meetings, who use customer data to orient technology decisions, and who refuse to accept “we can’t” as a response without first asking what the customer impact of that constraint actually is.

It also required the shift in ways of working that NatWest undertook over the past several years: the move to agile, design thinking, and cross-functional teams that brought business and technology closer together. This wasn’t just a process change. It was an identity change, a renegotiation of what it means to be a technology professional in a bank.

“The shift to agile ways of working and design thinking brought about a much stronger integration of the business and technology functions.”

That integration is still in progress, as it is in most large enterprises. But the trajectory is clear: the old model, in which technology was a service function responding to business requirements, is giving way to a model in which technology and business are co-creators, jointly accountable for outcomes. For that to work, technologists need to understand the business deeply, and the business needs to understand technology well enough to make meaningful decisions about it.

Redshaw has invested in building that mutual fluency, partly through hiring and team design, and partly through the culture of continuous learning she has embedded in the team’s development.

“We’ve made a deliberate investment in continuous learning, so development becomes part of everyday work rather than something separate.”

The emphasis on “part of everyday work” is key. In an organisation moving as fast as NatWest’s retail technology function, separate learning programmes struggle to compete with the urgency of the work. The only learning that sticks is the kind that is integrated, happens in the context of the challenge, is applied immediately, and is supported by a culture that encourages experimentation rather than penalises it.

“We want learning to feel encouraged, not mandated, a place where people feel safe to experiment.”

That phrase, “safe to experiment”, lands differently in a regulated bank than it might in a software start-up. Safety to experiment is not the same as permission to fail recklessly. It means creating the conditions in which people are willing to try things, challenge assumptions, and bring their best thinking to hard problems, without the constant fear that a mistake will define them.

“People want banking to be seamless, intuitive, and increasingly personalised, but they also expect it to be safe and trustworthy. For us, the key is recognising that these aren’t competing priorities.”

AI, Ethics, and the Question You Have to Ask

No conversation about enterprise technology leadership in 2026 gets to avoid the subject of AI. Redshawdoesn’t try.

She approaches it with the same combination of intellectual seriousness and practical caution that characterises her leadership more broadly. She is not sceptical of AI’s potential. She is sceptical of the shortcuts: the adoption of capability without the critical thinking that should precede it.

“The biggest piece of advice I’d give is to really hold on to critical thinking.”

In the context of AI, this means something specific. The arrival of generative AI and increasingly capable AI systems in the enterprise has created commercial, competitive, and reputational pressure to deploy quickly and demonstrate relevance. That pressure is real. But it can shortcut the questions that matter most: not what this technology can do, but what it should do, for whom, under what conditions, and with what safeguards.

“Effective technology leadership isn’t about doing something simply because you can. It’s about asking whether you should, and how you should.”

For a retail bank, this question has immediate practical weight. AI in financial services touches things that matter deeply: fraud detection, customer communication, and data analysis, to name a few. The difference between AI that serves customers well and AI that introduces systemic bias, creates opacity in consequential decisions, or erodes the trust the bank has spent years building is, in many cases, the quality of the questions asked before deployment.

Preparing teams for an AI-driven future, Redshaw argues, requires focusing on three things: critical thinking, ethics, and the responsible use of technology. The first is the capacity to evaluate AI outputs rather than simply accepting them. The second is the framework that makes evaluation meaningful: the values and principles against which you assess what responsible use looks like. The third is the operational practice that connects principle to execution.

“Preparing for the future requires continuous curiosity, learning, and critical thought.”

This is not a conservative position. It is a responsible one. Redshaw’s enthusiasm for what AI can do in retail banking is genuine: the potential to personalise at scale, detect fraud more effectively, and remove friction from customer experiences. But enthusiasm deployed without rigour produces regret. The organisations that will do AI well in banking are the ones that combine genuine capability with genuine discipline. Wendy Redshaw is building both.

“For me, preparing for the future is as much about people as it is about platforms, if not more so. Technology will continue to evolve rapidly, but it’s the skills, mindset, and leadership of our teams that determine whether we can use it effectively and responsibly.”

What Legacy Actually Means

As Redshaw prepares to step down from her role, the question of legacy is not abstract. She has been at NatWest long enough to have shaped the culture in ways that will outlast her tenure.

“If an organisation becomes dependent on one individual, then something hasn’t quite worked.”

It is a pointed self-assessment from someone who has spent eight years in a role of considerable individual influence. The test of leadership, in her view, is not what you built while you were there. It is what continues to grow after you leave.

“I’ve always believed my role is to create the conditions for others to flourish.”

This is her fundamental operating principle, the thing she describes as her purpose, not just as a leader but as a human being. It shapes how she thinks about team development, succession, partnership, and the culture she has tried to create.

The legacy she is working to leave is structural: platforms that are resilient and capable of continuing to evolve; teams with the skills, mindset, and confidence to navigate what comes next; partnerships built on shared ownership rather than transactional delivery; and a culture that knows how to learn, how to fail well, and how to keep the customer at the centre of every decision.

“Transformation is as much about people and culture as it is about platforms and architecture.”

She says this not as a closing sentiment, but as a practical conclusion drawn from eight years of experience. The platforms she has helped build are impressive. The architecture decisions have been consequential. But at the core of NatWest’s progress is its culture. Built deliberately over years by Redshaw and her colleagues, it underwrites everything from AI adoption to regulatory change, and the trust of 19 million customers.

“Staying grounded in purpose, why you’re doing something and who it’s for, really helps teams navigate change and stay connected to outcomes that matter.”

Purpose, in this context, is not a values statement on a wall. It is the daily practice of asking whether the decisions being made, about technology, people, and priorities, are the ones that serve the customer and earn their trust. It is the question at the beginning of every meeting, and the check at the end of every sprint.

And it is a harder discipline to maintain than any cloud architecture.

The Advice That Matters

What does Wendy Redshaw tell the next generation of technology leaders?

She doesn’t tell them to learn the most cutting-edge tools, though she would expect that as table stakes. She doesn’t tell them to network aggressively or build their personal brands, though these things matter. She tells them to think.

“Ask, ‘What might we be missing?’ and ‘What assumptions are we making?’ Really hold on to critical thinking.”

In a world that rewards speed, values decisiveness, and increasingly augments human judgement with machine capabilities, the discipline of stopping to ask hard questions is becoming a distinguishing skill. Not the absence of action, but the quality of thought that precedes it.

She tells them to embrace small, diverse teams. “The power of small, collaborative, diverse teams” is something she returns to with conviction, as a practical observation about where the best thinking tends to come from. Large, homogeneous teams optimise for agreement. Small, diverse teams generate friction, surface assumptions, and produce better decisions.

She tells them to stay curious. The rate of technology change is not slowing, and the leaders who will navigate the next decade are not necessarily the ones most expert in the current toolkit. They are the ones who have built the habit of learning, and who find the arrival of the unfamiliar energising rather than threatening.

And she tells them that the human dimension is not optional. It is not a soft skill that rounds out a technical profile. The central challenge of technology leadership, now and for the foreseeable future, is not technical. It is human: building trust, culture, relationships, and a shared purpose that allow organisations to do hard things together — even if that hard thing is, in fact, building and leading a “digital human” workforce.

That, in the end, is what a legacylooks like.

“I am being very thoughtful about where my skills and experience can make the biggest difference next. This may be the end of a chapter at NatWest, but it’s certainly not the end of the book.”

Wendy Redshaw has served as CDIO of NatWest Retail Banking since 2017. She was named the leading CIO in banking and financial services in the UK and Europe by Digital Edge Magazine in 2026.