We tend to think of “service” as something that came later.

Customer service. Service design. Service economies.

As if it were an extra layer that appeared once products matured and companies needed differentiation. But that framing is already wrong.

Service is not a stage of the economy.
It is a condition of human coordination.

Long before products, platforms, or even formal markets, economic life was not organised around isolated transactions. It was organised around dependency. People didn’t just exchange goods. They relied on each other to produce outcomes over time.

A harvest was not just a result. It required timing, labour, knowledge, storage, and coordination across people. The value was never just in the output, it was in whether the system held together long enough to deliver it.

That is the beginning of service.

Even the simplest exchange carries this logic. A tool is not just an object. Its value depends on whether it works when needed, whether it fits into a larger activity, and whether it can be relied upon at the critical moment.

Which means the value is not fully contained in the thing itself, but in the conditions that make it useful. That is already a service relationship.

This becomes even clearer at the level of institutions. Healthcare, banking, and government are not just sectors, they are large-scale service systems designed to guarantee outcomes individuals cannot produce alone.

And this is where a critical distinction appears.

A product can exist in isolation.
A service cannot.

Once you understand that a service can’t be in isolation, it becomes easier to define it as everything that must happen before, during, and after a product for an outcome to be delivered.

A book that captures this shift well is This Is Service Design Doing, particularly in how it reframes design beyond deliverables and into coordination across people, processes, and infrastructure.

Great! So, we’ve established that service is the full system around an outcome. The problem now is that most of digital design stopped at the smallest visible part of that system.

If service has always been the structure behind outcomes, then the obvious question is: How did we end up designing everything except the service?

The answer sits in how digital work evolved.

When digital products first emerged, they introduced something new into organisations: a visible layer of interaction. For the first time, companies could directly shape how people experienced a service through a screen.

And that changed where attention went.

Design moved toward what could be seen, tested, and improved quickly. Interfaces became the centre of gravity, not because they were the most important part of the system, but because they were the most accessible.

You could redesign a screen.
You could measure usability.
You could run tests and show improvement.

Compared to that, everything underneath felt slower, messier, and harder to influence and understand.

So, what happened next wasn’t accidental.

As digital products emerged, they introduced something organisations had never really had before: a visible, controllable layer of experience. For the first time, companies could shape how a service felt through an interface, and more importantly, they could measure it.

So over time, a pattern emerged.

Digital teams began to invest heavily in what they could see, test, and improve quickly, while everything else remained harder to access, slower to change, and often outside their control.

A lot of what we now recognise as “good UX” comes from this shift into clean interfaces, smooth journeys, reduced friction. And to be fair, that work mattered. It raised expectations and improved the quality of digital interactions across the board.

But it also created a blind spot.

Because it allowed organisations to believe they were improving services, when in many cases they were only improving how those services looked.

This is something that The Design of Everyday Things hints at, even if indirectly. The focus on usability and interaction brought rigour to design, but it also reinforced the idea that problems live at the interface.

In reality, the interface is often where problems become visible, not where they are created.

If you map where effort typically goes in digital teams, the imbalance becomes difficult to ignore.

If most of our effort has been concentrated on the surface, then AI is about to put that entire approach under pressure.

AI is often framed as disruption. In reality, it’s something more precise. It is a structural correction.

For years, digital work has been anchored in execution:

Work that was valuable largely because it required time, effort, and specialised skill.

AI changes that equation.

This is the shift.

If interfaces can be generated, they are no longer the main source of value.
If tasks can be automated, execution is no longer differentiation.

But the system underneath, the service, remains complex, messy, and unresolved. And this is where the direction of value becomes clear.

As execution becomes cheaper, value moves toward:

As execution becomes cheaper, understanding service becomes the new form of expertise.

If AI is shifting value away from execution and toward systems, then the job market should already reflect that shift.

It does, but not in the way most people expect.

At first glance, the UK UX market still looks strong.

Demand for UX/UI roles remains high across industries, with salaries typically ranging from ~£48k to £85k+, and even higher at senior levels. In London alone, median salaries sit around £57k–£75k, depending on role and seniority. (Source)

On paper, this looks like a healthy, growing field.

But underneath that surface, the structure tells a different story.

The UK design market has experienced 38 consecutive months of declining vacancies, while at the same time 65% of roles are reported as hard to fill due to skills gaps. (Source)

At the same time, UX research roles and entry-level positions have seen significant contraction, with fewer openings and increased competition.

This creates a paradox:

⬆ demand remains high
⬇ opportunities feel scarce
⬆ competition is increasing
⬇ hiring is becoming more selective

Which suggests the issue is not simply “more or fewer jobs”. It is what kind of work the market is willing to pay for.

And we end up with roles that operate closer to systems becoming harder to fill. Not because there are no candidates. But because fewer people are trained to operate at that level.

This gap is already being reflected in broader labour trends. The UK’s design economy is increasingly shifting toward strategic and cross-functional roles, with the Design Council highlighting a growing demand for capabilities that combine design with systems thinking, policy understanding, and organisational impact. At the same time, reports from McKinsey & Company and World Economic Forum consistently rank complex problem-solving, systems thinking, and analytical reasoning among the fastest-growing skills for the next decade.

The direction is clear. As services become more complex and AI accelerates execution, the market is not just asking for better designers. It is asking for people who can understand and shape systems. And companies who don’t comply will most likely fail.

If AI is reshaping where value sits, then the question is no longer what tools we use, but what remains uniquely human in the system.

For a long time, design has leaned on empathy as its defining trait. But empathy alone is not enough to operate in complex services. What matters now is the ability to interpret, decide, and take responsibility within systems that do not behave predictably.

AI can generate outputs, accelerate workflows, and replicate patterns. What it cannot do, at least not in any meaningful way, is understand consequence in context.

This is where human value consolidates. Not in execution, but in:

This perspective is explored deeply in Thinking in Systems, which reframes how complex systems behave and why interventions at the surface rarely solve underlying problems. It’s a useful lens for understanding why design must move beyond interfaces and into structure.

To be “human” in this context is not to compete with AI. It is to operate at a level where AI becomes infrastructure, not identity.

Understanding this shift is one thing. Applying it to your own work, your portfolio, and your career is where most people get stuck. Because the gap is not knowledge, it’s translation.

How do you move from:

If you want to go deeper into the thinking behind this volume, these are the references that shaped it. Each of them connects to a different layer of the argument, from interaction, to service, to systems.

This is not a collection of prompts or tools. It’s a structured way to rethink how research, AI, and decision-making fit together in real work.

It focuses on:

If the previous sections helped you understand what is changing, this is designed to help you act on it.

This volume was not about tools. It was about reframing the field. We started with service as the structure behind outcomes, and followed how digital design narrowed itself to interfaces, optimising what was visible, while leaving the system underneath largely unchanged.

AI is now exposing that limitation. As execution becomes cheaper, value moves toward systems, not screens.

The future of design will not be defined by how well we shape interfaces,
but by how well we understand and organise the systems behind them.

Next, we move from theory to reality, exploring how service systems behave differently across public, private, and market models, and why context fundamentally changes how outcomes are designed and delivered.