In our first volume, we established something that fundamentally changes the way you see digital work once you truly understand it: services do not exist in isolation. A service is never simply the interface people interact with. It is the invisible structure that makes an outcome possible in the first place.

The product was never the whole story.

The interface was never the service.

And once you begin seeing services as systems rather than screens, another realisation appears almost immediately afterwards: not all systems behave the same way.

This is where a lot of modern design conversations begin to fall apart.

Because much of the digital industry spent years speaking about “users”, “journeys”, and “friction” as though all services could be approached through the same lens. As though redesigning a food delivery application was structurally comparable to redesigning a healthcare service, a banking infrastructure, or a national welfare system.

They are not remotely the same problem.

A startup platform, a government department, and a banking ecosystem may all deliver “services”, but they operate under completely different realities.

This is the point where service stops being primarily a design discipline and starts becoming an organisational discipline.

And organisational complexity is where reality begins.

This transition is explored further in ”System Thinking in Service Design Workbook”, focused on how services operate. Rather than treating service as isolated UX activity, it examines the operational, organisational, and structural realities that shape how outcomes are actually delivered at scale.

Once service expands beyond a single interaction, it starts colliding with something much harder to control: reality itself.

Because this is the point where services become dependent on:

A service may feel seamless on the surface while underneath relying on dozens of interconnected systems that users never see.

A book that captures this transition particularly well is Mapping Experiences by Jim Kalbach, particularly in how it shows that experiences are shaped by the wider systems, processes, and organisational structures surrounding the interaction itself.

One of the reasons service design is still misunderstood in many organisations is because most people enter digital work through UX work. Screens are visible. Journeys are tangible. Prototypes can be demonstrated. UX/UI work creates the comforting illusion that complexity can be contained neatly inside interaction patterns.

But real services do not operate neatly.

The moment organisations move beyond relatively simple products, complexity expands aggressively. A modern service is rarely delivered by a single team. It exists across overlapping operational layers that often have competing incentives and entirely different definitions of success.

The same pattern increasingly exists in the private sector as well. Banking platforms are no longer simply financial products. They are regulatory systems. Logistics systems. Identity systems. Fraud systems. Risk systems. Communication systems. Infrastructure systems.

And this is one of the biggest shifts happening underneath modern service work: organisations are no longer competing purely through products. They are competing through operational coordination.

This is also why the role of service ownership has become substantially more important over the last decade.

Traditional product ownership often assumes that teams can optimise relatively independently. Service ownership forces the opposite realisation. Almost nothing meaningful can be changed in isolation because every improvement creates consequences somewhere else in the system.

This is why many organisations accidentally confuse activity with transformation. They redesign interfaces, modernise journeys, improve usability scores, introduce AI assistants, optimise conversion metrics, while the underlying operational structure remains fundamentally unchanged.

The result is what increasingly feels like operational theatre.

The service appears modernised from the surface while the internal system continues operating through fragmentation, manual workarounds, duplicated processes, supplier dependencies, organisational silos, and invisible escalation paths holding the entire experience together behind the scenes.

And nowhere does this become more visible than in the public sector.

One of the biggest mistakes people make when moving from private-sector digital work into government is assuming that public services operate like slower startups.

They do not.

Here are four examples of how service models differ depending on the systems, incentives, and operational environments they exist within.

In the UK particularly, public-sector digital work became heavily influenced by the standards introduced through the Government Digital Service (GDS). The introduction of service standards, accessibility requirements, design systems, and assessment models attempted to create consistency across fragmented government ecosystems that historically operated through isolated departmental structures.

But what often gets missed externally is that these frameworks are not simply “design guidance”.

They are governance mechanisms.

The GDS Service Standard, for example, is fundamentally an attempt to reduce systemic fragmentation across government delivery. It exists because public services cannot rely purely on market competition to self-correct operational failures in the same way private companies sometimes can.

This is also why service design inside government becomes deeply connected to procurement, commercial structures, and supplier ecosystems.

Understanding service in government therefore requires understanding institutional behaviour itself.

And institutional behaviour is inseparable from politics.

A resource designed around this complexity is the ”System Thinking in Service Design“ Workbook. This workbook explores how services operate beyond interfaces, helping readers understand the realities of policy, operations, governance, procurement, and large-scale service ecosystems across both public and private sectors.

Public-sector services do not exist outside politics. They exist inside systems of funding, governance, legislation, institutional priorities, and national direction, all of which shape how services are ultimately delivered to citizens.

Services in public are often described as neutral systems designed purely around delivery.

In reality, the structure of services is heavily influenced by political ideology, economic direction, and governmental priorities. Elections do not simply change leadership. They often reshape how institutions define efficiency, accessibility, investment, automation, accountability, and the role of the state itself.

This creates one of the defining complexities of service design inside government.

Services are not operating inside stable systems. They exist inside constantly evolving political, economic, and institutional environments where operational decisions can simultaneously carry legal, financial, social, and ethical consequences.

And this is precisely why public-sector transformation increasingly requires systems thinking rather than purely interface thinking.

A book that captures the complexity of public-sector service particularly well is Transforming Public Services by Louise Downe. The book explores how public services operate across policy, governance, operations, and institutional accountability, showing why designing at national scale requires systems thinking far beyond interfaces alone.

Politics shapes public services through ideology, regulation, funding, and institutional direction. But private-sector systems are not isolated from these pressures either. They simply respond to different incentives.

Where governments optimise around public accountability, social outcomes, and national infrastructure, private organisations optimise around competition, revenue, retention, growth, operational efficiency, and market positioning.

For years, the private sector appeared significantly more digitally advanced than government. And in many ways, it was. Companies could centralise decisions faster, move aggressively, abandon failing products quickly, and invest heavily in customer experience as a competitive advantage.

But over the last decade, something important changed.

Private-sector services also became systemically complex.

Modern banking is no longer simply financial infrastructure. It is now identity management, fraud prevention, AI-assisted risk modelling, behavioural analytics, operational orchestration, compliance management, ecosystem integration, and real-time security operating simultaneously across the same service environment.

The same applies to logistics platforms, enterprise SaaS, streaming ecosystems, subscription services, marketplaces, and increasingly AI-native products.

And this is precisely where many organisations began discovering that “good UX” alone was no longer sufficient differentiation.

This shift becomes even more visible inside B2B environments, where service complexity operates very differently from consumer platforms.

Consumer vs Enterprise Service Models:

This is also why Account-Based Marketing (ABM) became increasingly important across enterprise organisations.

Large B2B companies are rarely selling isolated products anymore. They are selling ecosystem compatibility, operational trust, integration capability, and long-term organisational alignment.

This works particularly well in B2B environments where relationships are concentrated around high-value organisational accounts, but the same logic breaks down in public-sector services, while public-sector environments involve far more fragmented institutional structures, political dependencies, regulatory constraints, and overlapping stakeholder realities, making it much harder to treat institutional roles the same way you would in traditional B2B environments.

Although agencies, consultancies, startups, and product companies may use similar digital methods on the surface, the systems underneath behave entirely differently.

And this is precisely why copying practices blindly between industries frequently fails.

This becomes even more complex when product companies or startups begin operating inside public-sector environments, where commercial models collide with institutional, political, and operational realities.

A startup culture built around speed and experimentation may create catastrophic risk inside healthcare and government infrastructure. A heavily governed public-sector delivery model may completely collapse inside an early-stage startup environment. A consultancy operating model designed around transformation programmes may struggle inside product-led organisations optimising for continuous iteration.

The methods may look similar on the surface.

The systems underneath are not.

A book that captures the operational complexity of private-sector service particularly well is ”This Is Service Design Doing” by Marc Stickdorn, Markus Edgar Hormess, Adam Lawrence, and Jakob Schneider. Rather than focusing only on customer experience, the book explores how services operate across business models, organisational structures, operations, strategy, and ecosystem coordination, making it especially valuable for understanding service beyond interfaces and into real organisational delivery.

Increasingly, the most important services in the world are no longer isolated organisations. They are ecosystems.

Uber is not simply transport. Amazon is not simply retail. Modern banking is no longer simply financial infrastructure. These organisations operate through interconnected systems coordinating suppliers, logistics, cloud platforms, identity layers, AI tooling, operational dependencies, and behavioural data simultaneously.

Over the last decade, competitive advantage has slowly shifted away from isolated features and toward coordination at scale.

This becomes particularly visible across:

According to Gartner and McKinsey, ecosystem-based business models are becoming one of the primary drivers of long-term economic value creation as industries become increasingly interconnected.

And this is ultimately the deeper shift happening underneath modern service design.

The organisations dominating the next decade are unlikely to be the ones producing the best interfaces alone. They will be the ones most capable of coordinating complexity across interconnected systems, infrastructures, and operational environments at scale.

AI is accelerating this rapidly. Interfaces are becoming easier to generate, production cheaper, and delivery faster. But understanding how systems behave across organisations, regulations, operations, platforms, and ecosystem dependencies remains difficult for the future and even more urgent across AI ethics and human responsibility.

This is why systems thinking is increasingly becoming a strategic capability.

The future of service work is no longer primarily about producing user experiences. It is about understanding consequence, coordination, and complexity across interconnected environments.

This is why I created the ”System Thinking in Service Design Workbook”

This workbook was designed to help professionals move beyond isolated outputs and understand how real services operate across systems, operations, governance, delivery ecosystems, and organisational complexity.

Inside the workbook, you’ll explore:

If you’d like to explore more topics around service, systems, AI, and organisational complexity, you can also follow me on Linkedin.

This volume was about understanding that services behave differently depending on the systems they operate within.

As services become increasingly interconnected, the work itself also changes. The future of service design will belong to the people capable of understanding complexity, coordination, governance, operations, and systems in context.

Next, we expand the conversation beyond organisations and into society itself, exploring how services increasingly operate as infrastructure behind modern life.

From digital identity systems like the EU Wallet to cross-border banking, remote work, digital nomads, healthcare access, taxation, and platform ecosystems, the next volume examines what happens when people begin living across systems that were never originally designed to operate together.