Over the last decade a phrase has quietly taken over the transformation world. Walk into almost any programme, any design workshop, any leadership offsite, and you will hear it spoken with confidence and conviction: human-centred. Human-centred design. Human-centred services. Human-centred leadership. The language has become so common that it almost feels unquestionable, as if by simply saying it we have solved something important.

And in many ways we have made progress. For years organisations designed systems around efficiency, scale and technical possibility. The technology came first, the people came later, and the result was often clumsy, frustrating experiences that required patience and workarounds just to get through a normal day. The rise of service design, user research and experience thinking helped rebalance that equation. Designers began asking different questions. What does the journey feel like? Where is the friction? What would make this simpler for the person using it?

Those questions have improved many of the digital tools we now rely on. The interfaces are cleaner. The steps are fewer. The journeys are easier to navigate. From a design perspective, human-centred thinking has been an important shift.

But every now and again, standing inside a large transformation programme, I find myself asking a slightly uncomfortable question. If transformation is now so human-centred, why does it still feel… meh?

Not terrible. Not catastrophic. Just quietly underwhelming. Good enough to run, perhaps, but rarely the kind of change that people talk about with enthusiasm. The new system arrives. People adapt. The organisation carries on. And somewhere between the project closing celebration and the next round of improvements, the energy fades.

Part of the answer, I suspect, is that we have become quite good at designing for humans, but we are still learning how to transform the human system itself.

Every organisation has a human system, although you will not find it documented in the architecture repository or mapped neatly into the programme plan. It exists in the relationships between teams, in the trust or tension between business and technology groups, in the informal conversations that happen long after a steering committee meeting has ended. It lives in habits that people have developed over years of working in a certain way, and in the small workarounds colleagues quietly share with one another when the official process does not quite work.

Two organisations can implement the same technology and have entirely different outcomes because the human system surrounding that technology is different. In one place the change takes root. In another it settles into a pattern of polite tolerance.

A while ago I ran a simple experiment with a group of technology leaders that made this dynamic visible in a way none of us expected. I asked them to rate how satisfied they believed colleagues and customers were with their IT services. Most answers clustered comfortably between three and four out of five, which happened to match the official metrics reported on their dashboards.

Then I asked a second question. How do you think people feel about those services when they actually use them?

The answers softened slightly. Still positive, but less confident.

Then came the final question. What do you think people are saying about those same services around the dinner table or the water cooler?

One word appeared again and again.

“Meh.”

It was not a disaster verdict. Nobody was describing chaos. But it revealed a quiet gap between the measured experience of technology and the lived experience of it. I call it the human gap: the distance between the plan and what people actually believe, experience and do. And that gap matters. Because if you believe the starting point of transformation is three or four out of five, you will design for incremental improvement. If the real starting point is “meh,” you are solving a very different problem.

This is where the conversation about human-centred thinking may need to evolve. Human-centred design asks an important question: how do we create better experiences for people? But transformation asks something deeper: what has to change in the human dynamics of this organisation for the future we are designing to actually work?

That question moves the focus away from individual services and towards the wider environment in which those services exist. It asks us to consider how people collaborate, how trust is built between teams, how assumptions about work are formed and how they shift over time. In other words, it asks us to think about the human state of the organisation.

Architects and technologists spend a great deal of time looking at diagrams of systems and structures. Capabilities, data flows, operating models and integration points all deserve attention. But every now and then it helps to step away from the diagram and look up. Walk across the office floor. Watch how someone begins their day. Notice the small pause before a laptop opens or the expression when a system takes longer than expected to load.

Listen to the conversations that happen when people step away from their screens. The jokes, the sighs, the shared shortcuts. Those moments reveal more about the real state of transformation than many carefully prepared reports ever will.

As organisations move into another wave of technological change, shaped by artificial intelligence, data ecosystems and increasingly complex digital platforms, the temptation will be the same as it has always been. Focus on the technology first. Solve the architecture. Build the roadmap. Deliver the programme.

But the organisations that succeed in making transformation stick will likely do something slightly different. They will recognise that transformation is not simply a redesign of systems or services. It is a shift in how the human system of the organisation behaves. It is a change in patterns, relationships and expectations about how work gets done.

When that human state begins to shift, something subtle but powerful happens. The quiet “meh” that often follows transformation begins to disappear. Conversations change. Energy returns. The technology finally starts to feel like it belongs.

And that is when transformation stops being something people tolerate and starts becoming something they believe in.

Whatever next?