In the world of digital design, there is a fundamental distinction that is often overlooked, with concrete consequences on project quality and solution effectiveness: the difference between UX design and Service Design.
Two disciplines, a shifting boundary that changes everything
UX design primarily focuses on the interaction between a user and a specific artefact — an app, a website, a digital interface. Its perimeter is defined by touchpoints: it addresses how the user perceives, navigates and evaluates that artefact in terms of usability, utility and overall experience. It is a powerful, necessary and highly visible discipline. Screens are tangible; user flows can be prototyped and approved. This very visibility creates a reassuring illusion within organisations that complexity can be neatly contained within interaction models.
Service Design operates at a structurally different and prior level. Its core object is not the single artefact but the entire service ecosystem: all components, people, tools and processes, both on the frontstage — what the customer directly perceives — and the backstage — employee workflows, operating systems, policies, logistics and infrastructure. Service Design does not design the individual touchpoint; it designs the relationships between touchpoints, and between touchpoints and the organisation.
The fundamental distinction is not one of scale but of object: UX design deals with the experience on the artefact, whereas Service Design deals with the experience through the service — which includes that artefact, but is not limited to it.
A digital product that is excellent from a UX standpoint can still produce a poor overall experience if the underlying organisational processes are poorly designed. A courier's app may have a flawless interface, but if the internal shipping management system fails to communicate correctly with the warehouse, the user will face delays and incorrect information. These are backstage failures that no amount of frontstage optimisation can compensate for. Service Design is the discipline that intentionally designs the causal chain connecting backstage and frontstage — ensuring that the user experience does not rely on chance or individual talent, but on a coherently designed organisational system.
When the experience breaks, the problem is almost always invisible
When a user calls customer support, provides their data, and is then transferred to another operator who asks them to repeat the exact same information, they are experiencing a Service Design flaw. This is not an interface problem, nor a technological issue: it is a problem of how the organisation is designed internally.
Service Design is the activity of planning and organising a company's resources — people, tools and processes — in order to directly improve the employee experience and, consequently, the customer experience. It does not merely focus on what the user sees, but on what lies behind: the invisible chain of decisions, workflows, systems and responsibilities that determines the quality of every single visible interaction.
The contemporary economy has dissolved the traditional distinction between goods and services. Today, almost no organisation delivers a pure product or a pure service; every offering is hybrid. The closer an offering shifts towards the service spectrum, the more internal processes cease to be purely productive factors and instead become an integral part of the user experience. The organisational backstage becomes experiential frontstage. Designing it with the same rigour used to design an interface is no longer a choice — it is a structural necessity.
Frontstage, Backstage and the Line of Visibility
Every service has two dimensions that coexist and mutually influence one another.
The frontstage is everything the customer sees and experiences: digital and physical touchpoints, interfaces, channels and frontline staff. The backstage is everything that remains invisible: internal processes, corporate policies, supporting technologies, information systems and cross-departmental workflows. The line of visibility is the boundary that separates these two levels.
The fundamental paradox of Service Design is that the customer experience is largely determined by what the customer never sees. Backstage failures immediately manifest as user experience problems.
Over time, Esario has developed a solid, methodologically rigorous expertise in designing both levels — working in an integrated manner across frontstage and backstage. This ensures that the quality of the final experience does not depend solely on the care put into visible touchpoints, but on the coherence of the entire operational chain that supports them.
The Service Blueprint: where Esario puts Service Design into practice
The core operational tool that Esario uses in Service Design projects is the Service Blueprint: a diagram that maps — within a single view — customer actions, frontstage employee and technology actions, backstage actions, support processes and physical and digital evidence, all aligned chronologically with the timeline of the customer journey.
Unlike a customer journey map, which narrates the journey strictly from the user's perspective, the blueprint adds the organisational dimension: who does what, where, using which tools, in what sequence and with what dependencies across the different layers of the service. It represents complexity made legible and actionable.
In practice, Esario builds Service Blueprints through a structured process. It begins with research: user and employee interviews, observation of real-world processes, and analysis of operational data. Customer actions are mapped along the journey, identifying the moments of truth — those critical junctures where users evaluate service quality and make future decisions. Then the work goes below the line of visibility, documenting frontstage and backstage actions, the technologies involved, support processes and the physical and digital evidence accompanying each phase.
The resulting blueprint is not a static document. It is an active working tool that Esario leverages to bring to light conflicts between internal processes and user expectations, pinpoint systemic friction points that cause most experience issues, identify operational redundancies that drain resources without adding value, and break down silos by facilitating conversations between departments to uncover their interdependencies.
Systems thinking: seeing the whole, not just the parts
In its most evolved form, Service Design requires a shift in perspective: moving from user-centred design to systems thinking. User-centred design starts with the individual, seeking to understand their needs to build products and services that satisfy them. While this perspective is indispensable, contemporary service systems — with their networks of interdependencies among technologies, organisations, channels, partners and contexts of use — also require the ability to see the whole.
It means understanding how actions in one part of the system create ripple effects in another, and how a change to an internal process can impact the customer experience at a distant, seemingly unrelated point in the journey. For a service designer, this means continuously toggling between two lenses: the close-up perspective, diving deep into the nuances of the individual user's experience, and the wide-angle perspective, seeing how that experience fits into a broader ecosystem of people, processes, technologies and organisational consequences.
Esario applies this dual perspective systematically. When tackling a service reorganisation project in an omnichannel hospitality context, we do not just work on the digital touchpoint; we map the entire ecosystem of processes supporting it. Similarly, when intervening on an information system within the Finance or Biomedical sectors, we analyse the dependencies between operational processes, regulatory constraints, technological systems and user behaviours to ensure that every design intervention aligns with the logic of the entire system.
Service Design and Artificial Intelligence
Artificial Intelligence is tangibly transforming the operational capabilities of Service Design across all its phases.
In the analysis and mapping phase, AI models allow the processing of large volumes of operational data, interaction logs, support session transcripts and omnichannel navigation data — identifying recurring friction patterns, systemic bottlenecks and optimisation opportunities that traditional analysis could not detect with the same depth and speed.
In the construction and validation of Service Blueprints, AI-assisted tools can identify inconsistencies between frontstage and backstage processes, simulate the impact of operational changes on the overall experience, and flag risk areas before any change is implemented.
In the optimisation of internal processes, AI enables the automation of repetitive backstage tasks, freeing up staff for high-value interactions that require judgement, empathy and relational skills. This combination — operational efficiency driven by AI and relational quality driven by people — is exactly what Esario pursues when designing services for its clients.
In the continuous monitoring of live services, AI models detect weak signals of quality degradation before they turn into visible problems, allowing companies to intervene in the internal process chain before the customer ever notices.
At Esario, systems thinking and Artificial Intelligence are not separate tools — they are two complementary lenses used to navigate the growing complexity of contemporary service systems with the same methodological depth that has characterised our approach to design for over twenty years.