Why the delivery gap persists: it’s how teams interact, not how hard they work
One of the most striking statistics about the delivery gap comes from Bain research published in 2005: 80% of executives believed their organisation delivered a superior customer experience, yet only 8% of customers agreed.
Organisations genuinely believe they are customer-centric because their strategy starts with customers. But users experience the organisation from the outside-in, across multiple interactions and teams. Most organisations, however, are designed inside-out, around internal functions. The result is the delivery gap.
It’s worth acknowledging that this often-quoted Bain research on the delivery gap was published twenty years ago, so it might feel archaic, but the reality is that the gap it describes hasn’t disappeared; it has evolved. A later report from Capgemini found a similar disconnect: around 75 % of organisations believed they were customer-centric, while only about 30 % of consumers agreed.
And more recent research suggests the challenge is far from solved. Forrester’s CX Index shows customer experience quality among brands sitting at historically low levels, with declines in effectiveness, ease, and emotional connection.
So this difference in perception remains a feature in many organisations who sincerely believe they are creating value, but whose users still report experiences that fall short. And now, with the rapid rise of AI and digital acceleration, this disconnect can widen further, because powerful technology amplifies both clarity and confusion. Organisations with clear ownership, well-designed boundaries, and a shared understanding of user needs can use AI to reduce toil and improve outcomes. Organisations without that clarity risk scaling the very inefficiencies and misalignments that created the gap in the first place.
It’s not that teams don’t care; the system isn’t designed for alignment.
In every organisation I work with, I meet talented, motivated people who want to make an impact. The problem is not the effort; the problem is the shape of the work.
Three things routinely break alignment:
Teams own tasks, not outcomes
Capabilities are scattered across organisational islands
Dependencies multiply until autonomy disappears
Users don’t care how you’re organised internally, but the way your teams interact shapes everything they experience.
When you don’t start with users, you end up mapping systems
This is one of the most consistent anti-patterns I see. Companies believe they are user-centric, but the first time they try to map their world, what appears on the wall is:
features
components
tasks
workflows
systems
These aren’t needs; they’re internal representations of work and a clear signal of inside-out thinking. Inside-out thinking made sense in a world of slower change. But today market shifts are frequent, user expectations evolve faster than roadmaps, and AI is accelerating complexity, so organisations can’t rely on stable norms. Change is the new constant. A structure optimised for internal efficiency becomes the bottleneck for adaptation.
Closing the gap requires reframing the work, not pushing harder
This is where User Needs Mapping can be helpful: as a corrective lens. Without a clear, shared understanding of users and their needs, organisations will continue to overestimate the value they deliver — no matter how hard their teams work or how advanced their technology becomes. By explicitly starting with users and their needs, then mapping the capabilities required to meet those needs, organisations can finally see where their team interactions support value flow, and where they actively work against it. And once teams see how value flows (or doesn’t), alignment becomes much more achievable.
What tends to change first is the quality of conversations; teams stop debating priorities in abstract terms and start grounding decisions in user outcomes. Leaders gain a clearer line of sight between strategy and the work happening on the ground. Most importantly, teams begin to share a common reference point for why the work exists. This is the shift from coordinating activity to coordinating around value. And it’s why reframing the work around user needs so often unlocks progress where years of optimisation and transformation initiatives have stalled.
The delivery gap isn’t a people problem; it’s a sociotechnical architecture problem, and what’s encouraging about that is this: sociotechnical architecture is a design choice. It can be examined, discussed, and evolved. When organisations start with users, make needs explicit, and design team boundaries and interactions around real value flows, the gap between intent and experience finally begins to close.
If you’re noticing a gap between intent and experience in your organisation, and want to explore what’s behind it, feel free to reach out.
