In the first volume of this series, we explored how service became the structure behind outcomes. In the second, we examined how services behave differently across public, private, and market environments.

This volume expands the lens again.

For most of modern history, institutions were the primary mechanism through which society functioned. Governments administered rights, banks enabled economic participation, universities controlled access to education, and healthcare systems controlled access to treatment.

Increasingly, that is no longer the full picture.

Today, many of the most important interactions in our lives are mediated through services operating across multiple organisations simultaneously.

Most people never see these systems.

They simply experience the outcome.

This creates a subtle but important shift.

As services become increasingly interconnected, they begin to behave less like organisational capabilities and more like societal infrastructure.

The result is that access to healthcare, education, employment, banking, taxation, mobility, and increasingly citizenship itself depends on systems operating far beyond the boundaries of any single institution.

Services are no longer simply supporting society.

They are increasingly becoming the infrastructure through which society operates.

This is something I go much deeper into in ”System Thinking in Service Design Workbook”. My workbook looks at what sits underneath a service once you move past the surface: the operations, decisions, systems, teams, constraints, and structures that quietly determine whether an outcome can actually be delivered at scale.

Once services become infrastructure, the important question changes. It is no longer only what institutions exist, but how those institutions are translated into everyday access.

This is the layer most people experience without naming it. A tax system becomes a login, a calculation, a deadline, a refund, or a penalty. A healthcare system becomes triage, records, referrals, prescriptions, and waiting times. A bank becomes identity checks, fraud controls, access decisions, and payment movement. The institution may still exist in the background, but the lived experience happens through the service layer.

This is not abstract. The UK’s own digital government review shows the scale of this mediation: DVLA reported that over 80% of services are online, with 95 million digital transactions and 4 billion API hits each year, while HMRC reported that 70% of its services are digitally enabled but still processes 37 million calls and 17 million letters annually. (source: gov.uk publications)

That contrast matters.

It shows that service infrastructure does not simply “digitise” society. It creates a new operating layer where digital access, human support, paper processes, data systems, and institutional rules all continue to coexist.

This is why the service layer is so powerful. It decides how institutional complexity becomes understandable, hidden, or pushed back onto the person using it. For some, this makes society faster and easier to access. For others, especially those affected by digital exclusion, it creates a new barrier to work, health, education, benefits, and banking.

So the service layer is not only where society becomes easier to use. It is also where access can quietly become conditional on being able to navigate the system.

But this is where the service layer starts to stretch.

Because once ordinary life is mediated through services, the next question becomes what happens when a person’s life no longer fits neatly inside one system.

That assumption made administration easier. The person, the employer, the bank, the tax authority, the healthcare system, and the pension system were usually operating within the same national frame.

But that is no longer how many people live.

Someone may work remotely for a company in one country, live in another, hold citizenship somewhere else, bank internationally, travel often, and still need healthcare, tax clarity, pension continuity, immigration status, and identity verification across all of those systems.

To the person, this may feel like modern life. To the system, it’s an exception.

This is the tension behind digital nomads, cross-border workers, international students, dual citizens, global freelancers, and families spread across countries. Their lives are becoming more fluid, but the services around them are still largely built around territorial logic.

The problem is not always that one service is badly designed.

Often, the problem is that several services were never designed to recognise the same life at the same time.

This is why digital identity initiatives are starting to happen. The EU Digital Identity Wallet is one example of a broader global question: how can societies make identity, credentials, and access work across different services without creating new risks around surveillance, exclusion, dependency, or state overreach?

Similar tensions are now appearing in cross-border healthcare, international pensions, banking verification, immigration systems, and tax residency.

So the future of service across societies will not only be about improving individual journeys. It will be about designing the connections between systems that were never originally built to move together.

A useful book to read alongside this section is Seeing Like a State by James C. Scott. It helps explain why institutions often simplify human life into categories, records, maps, rules, and administrative systems, and why those systems can struggle when people live across borders, identities, economies, and services that do not fit neatly into one national frame.

The reason cross-border services become so difficult is that every system needs to answer the same basic question before anything else can happen: who is this person, and can we trust the evidence attached to them?

That question used to be answered through documents, offices, signatures, letters, passports, bank branches, and local records. Increasingly, it is answered through digital identity systems that sit quietly underneath banking, healthcare, tax, employment, benefits, travel, education, and immigration.

This changes the role of identity.

It is no longer only something a person proves at the beginning of a process. It becomes the layer that allows the process to exist at all.

When identity becomes the gateway to services, exclusion becomes more serious. A failed verification is no longer just an admin problem; it can block access to money, healthcare, work, travel, education, or public support.

This is why digital identity is such a sensitive topic. It promises convenience and coordination, but it also raises difficult questions about surveillance, dependency, data control, private-sector involvement, and what happens when someone cannot prove who they are in the way the system expects.

The real issue is not whether identity becomes digital. It already is, in many parts of everyday life.

The real issue is whether identity infrastructure can become secure, portable, transparent, and inclusive without making people more dependent on systems they cannot understand, challenge, or escape.

Identity is no longer just verification.

A resource designed around this kind of complexity is the ”System Thinking in Service Design“ Workbook. It helps readers look beyond individual service touchpoints and understand how service design shapes complex systems.

Great, now we are getting to a very interesting part. The Future.

Once identity becomes infrastructure, the question becomes more personal.

What happens to the citizen when life no longer fits neatly inside one country, one employer, one bank, one tax system, or one healthcare system?

For a long time, citizenship was imagined through a relatively stable relationship between a person and a state. You lived somewhere, worked somewhere, paid tax somewhere, accessed services somewhere, and eventually retired somewhere. The system was not always fair or simple, but the administrative logic was easier to understand.

That model is now starting to stretch.

In the EU, around 9% of people living in member states were non-nationals in 2023, including citizens from other EU countries and from outside the EU. In 2024, 1.5 million people moved from one EU country to another, while another 4.2 million immigrated to the EU from non-EU countries. Mobility is no longer an edge case. It is becoming a normal feature of modern societies. (source: European commission)

Work is changing too. In Great Britain, 28% of working adults were hybrid working in autumn 2024, showing how work has become less tied to a single office, even if access to that flexibility remains uneven. (source: ons.gov.uk)

This creates freedom.

People can study in one country, work for another, move money across borders, build international careers, care for family elsewhere, or live lives that previous administrative systems would have treated as unusual.

But it also creates dependency.

The more mobile life becomes, the more people depend on services to recognise them correctly across systems. A person may feel coherent in their own life, while appearing fragmented to the institutions around them.

This is the emerging service condition of citizenship.

Citizenship is no longer only a legal relationship between a person and a state. In practice, it is becoming a set of service relationships that must keep working across borders, platforms, employers, banks, healthcare systems, and identity infrastructures.

The future citizen may be more mobile than ever.

But also more dependent on systems being able to keep up.

A useful book to read alongside this section is The Age of Surveillance Capitalism by Shoshana Zuboff. It is not a service design book, but it helps frame one of the biggest tensions in the service society: the same systems that make life more connected, personalised, and convenient can also make people more visible, measurable, and dependent on infrastructures they do not fully control.

This is the positive side of the service society.

If services become infrastructure, they can also make society easier to access.

Not in a vague “digital transformation” sense, but in a practical one. A person does not benefit from a right simply because it exists in law. They benefit when they can understand it, apply for it, prove eligibility, receive a decision, challenge a mistake, and continue their life without the system becoming a full-time job.

This is where good service infrastructure matters.

It can reduce the distance between people and institutions.

It can make public functions easier to reach, especially when the old model depended on office hours, paper forms, phone queues, local knowledge, and repeated evidence. The UK government’s own digital efficiency work estimated that moving transactional services online could create between £1.7bn and £1.8bn in annual savings for government and service users, largely because digital services can reduce the cost and friction of routine interactions.

The benefits are not only financial.

This is also why digital public infrastructure has become such a major global development topic. The World Bank frames digital ID and payment systems as foundations for more inclusive access to services, financial participation, and public delivery, especially when they are designed around equity rather than exclusion.

The strongest positive interpretation is simple.

Services can make society more accessible.

They can turn institutions that once felt distant, slow, fragmented, or geographically fixed into systems people can reach more easily. They can support disabled citizens, rural communities, carers, migrants, remote workers, international families, small businesses, and people whose lives do not fit neatly into one administrative pathway.

But the benefit is not automatic.

A service society only becomes more accessible when the infrastructure is designed with enough care to include the people who are hardest to serve.

Otherwise, the same systems that reduce friction for some people can create new barriers for others.

This is the central trade-off of the service society. We couldn’t be talking about benefits without showing the risks present in these systems. When more of life depends on digital access, identity infrastructure, integrated records, automated checks, platforms, suppliers, and shared systems, the gains are real. But the dependency becomes real too.

A society can become faster, more coordinated, and more efficient, while also becoming more fragile.

This is why “digital access” is not the same as access. The UK Government’s own Digital Inclusion Action Plan points to data showing that digital exclusion affects people’s ability to engage with healthcare, finance, work, education, benefits, and public services; it also notes that only 6.7% of people with the lowest digital capability are likely to engage with their finances digitally, compared with 100% of those with the highest capability.

The risk is also operational. The UK Public Accounts Committee warned in 2025 that government cyber resilience remains far from where it needs to be, with risky legacy IT estimated to make up 28% of the public sector IT estate. It also reported that 319 legacy systems had been identified across government by January 2025, with around a quarter rated high risk.

That really matters because a service society does not fail in the same way a paper-based society fails. A closed office affects one place. A broken identity service, cyberattack, failed supplier, inaccessible portal, or corrupted record can affect thousands or millions of people at once.

The conclusion is not that society should avoid digital services. That would be unrealistic, and in many cases undesirable. The conclusion is that service infrastructure must be designed with failure in mind.

A mature service society needs:

Otherwise, the service society risks becoming very good at moving people through systems, and very bad at helping the people who do not fit them.

A practical resource for exploring this further is the ”System Thinking in Service Design“ Workbook. It will help you move past isolated points and understand how services operate across the wider system dynamics.

This is where the argument becomes directly relevant to careers.

If services are becoming infrastructure, then the market will increasingly reward people who can understand how systems behave, not only people who can produce outputs inside one discipline. The World Economic Forum’s Future of Jobs Report 2025 estimates that 22% of jobs will be disrupted by 2030, with 170 million roles created and 92 million displaced, creating a net increase of 78 million jobs. The important point is not only that jobs will change, but that the most valuable skills are moving toward analysis, judgement, coordination, and adaptation. Analytical thinking remains the top core skill employers expect to need.

In a service society, this makes sense.

When execution becomes cheaper, coordination becomes more valuable. Interfaces, reports, workflows, research summaries, content, prototypes, and basic operational tasks will become easier to generate. But understanding how a service behaves across policy, governance, risk, operations, procurement, AI, regulation, data, identity, and human behaviour remains difficult.

The important signal is not simply “learn AI”. That is too shallow.

The stronger signal is that organisations will need people who can understand what AI does inside a service system. A model that summarises documents is one thing. A model that influences healthcare triage, benefit eligibility, fraud detection, immigration routing, tax risk, hiring decisions, or identity verification is something else entirely.

The work moves from production to consequence.

This is why I think many future roles will not look like the roles we have today with “AI” added to the title. They will sit between existing disciplines.

The signal is visible in adjacent markets. OECD countries are already using AI in public service design and delivery, while the UK cyber sector continues to grow, with recruiters reporting rising demand for AI-related cyber skills and limited deep experience in the market.

This is the direction I would pay attention to: not becoming an expert in every field, but learning how systems behave across AI, policy, operations, data, governance, and risk.

The competitive advantage will be connecting what other people keep treating separately.

Execution becomes cheaper.

Coordination becomes more valuable.

For a long time, service design was often explained through journeys, touchpoints, blueprints, pain points, and better experiences, both technical and non-technical. Those things still matter. But they are no longer enough to describe the scale of the work.

If services are now part of how society functions, then service design can no longer sit only at the level of improvement.

It has to become a discipline of responsibility.

This is not about becoming an expert in everything. It is about becoming better at seeing relationships.

Because the most important service problems will not always look like service problems at first. They may look like a failed handover, a confusing policy, a broken data flow, a missing escalation route, a procurement constraint, a risk model, a funding decision, or a system that cannot recognise someone’s life.

As AI, automation, digital identity, and service infrastructure become more embedded in everyday life, the value of the designer will not be in producing more artefacts. It will be in protecting context, judgement, fairness, and meaning inside systems that are becoming faster than people can understand.

The discipline becomes less about optimisation.

And more about stewardship.

Not just designing services people can use, but helping shape systems people can trust.

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 how services are becoming the infrastructure behind modern life.

As identity, money, work, healthcare, taxation, mobility, and access increasingly move through interconnected service systems, the question is no longer only how services are designed. It is how much of society now depends on them.

Next, we move from services as infrastructure to AI inside that infrastructure.

From healthcare triage and fraud detection to welfare eligibility, banking risk, immigration systems, tax checks, education, and identity verification, the next volume examines what happens when services do not only process people’s lives, but start making decisions about them.