AXD vs Service Design

Service Design, as a discipline, is fundamentally anthropocentric. It emerged from a need to choreograph the complex interactions between people and the services they consume, viewing the 'user' as a human actor with specific needs, goals, and emotional states. Its tools and methods, such as customer journey maps, service blueprints, and personas, are all predicated on the assumption that a human is at the center of the service experience, making decisions, performing actions, and experiencing touchpoints.

This human-centricity has been its greatest strength, enabling the creation of more intuitive, efficient, and desirable services across countless industries. Service Design gives us a language and a process to see the invisible structures of a service, mapping out the frontstage and backstage interactions to ensure a seamless and coherent user experience. It excels at orchestrating the people, processes, and props that constitute a service encounter.

However, the rise of agentic AI introduces a non-human actor into this ecosystem, one that doesn't have the same motivations, cognitive processes, or limitations as a human user. An AI agent isn't a 'user' in the traditional sense; it is a proxy, an autonomous entity executing a delegated task. This fundamental difference challenges the core assumptions of Service Design and reveals the boundaries of its human-centric toolkit.

In the context of Agentic Experience Design, the AI agent is the primary actor, not the user. The human is the 'principal' who delegates a task, but the agent is the one navigating the digital or physical environment to achieve the specified outcome. This distinction is critical. A user directly experiences a service's touchpoints, whereas a principal experiences the outcome of the agent's actions. Their experience is indirect, mediated by the agent's performance and reporting.

This shift requires us to move beyond the concept of a 'user journey' and instead focus on the 'delegation architecture'. We are no longer designing for a person's interaction with a system, but for a system's interaction with other systems on behalf of a person. The agent's 'experience' is one of APIs, data protocols, and operational envelopes, not intuitive interfaces or emotional responses.

Therefore, the design focus shifts from usability and satisfaction to reliability, security, and trust. Can the principal trust the agent to act in their best interest? Is the delegation's scope clearly defined? Are the constraints robust? How does the agent handle ambiguity or failure? These are the central questions that AXD seeks to answer, questions that lie outside the typical scope of traditional Service Design.

A cornerstone of Service Design is the service blueprint, a detailed diagram that visualizes the relationships between different service components - people, props (physical or digital evidence), and processes. It maps the customer journey against the frontstage and backstage actions, support processes, and physical evidence. It is a powerful tool for understanding and optimizing human-delivered services.

AXD introduces a new primary artifact: the delegation design framework. This isn't a map of a journey, but an architectural plan for autonomous operation. It defines the structure of authority and responsibility passed from the principal to the agent. It specifies the agent's operational envelope, its decision-making power, its constraints, and its escalation paths. It is less about orchestrating touchpoints and more about engineering trust and control.

While a blueprint clarifies 'who does what and when' in a human-centric service, a delegation architecture clarifies 'what the agent can do and how'. It is a formal, often machine-readable, specification of autonomy. It includes elements like intent translation, consent horizons, and recovery protocols - concepts that are native to the world of autonomous systems but foreign to traditional service blueprints.

Service Design is obsessed with touchpoints - the specific points of interaction between a customer and a service provider. A touchpoint can be anything from a website and a mobile app to a physical store and a call center agent. The goal is to design each touchpoint to be as effective and emotionally resonant as possible, contributing to a positive overall journey.

In AXD, the concept of a touchpoint becomes less relevant, as the principal is often absent during the agent's operation. Instead, we focus on trust points. These are the critical moments in the human-agent relationship that establish, calibrate, and maintain trust. A trust point isn't an interaction with the service, but an interaction with the agent about the service.

Examples of trust points include: the initial delegation (defining the task and constraints), the agent's reporting (communicating progress and outcomes), the handling of exceptions (escalating for human input), and the final handover. Each trust point is an opportunity to reinforce the principal's confidence in the agent's competence and alignment. Designing these trust points is a core activity of AXD, ensuring the human-agent relationship remains strong even in the principal's absence.

The customer journey map is arguably the most iconic tool in Service Design. It visually represents the customer's experience over time, plotting their actions, thoughts, and feelings across a series of touchpoints. It tells a linear story of engagement with a service, from awareness to post-service evaluation.

AXD requires a different temporal model: the relational arc. Because the agent is persistent and the relationship with the principal is ongoing, the interaction is not a linear journey with a clear beginning and end. It is a cyclical, evolving relationship characterized by periods of delegation, autonomous operation, and reporting. The relational arc maps the evolution of trust and authority over time, not just a single transactional journey.

This arc includes phases like onboarding, initial delegation, trust calibration, increasing autonomy, handling major failures (trust debt), and potential 'offboarding' of the agent. It forces the designer to think about the long-term dynamics of the human-agent relationship, moving beyond the episodic view of a journey map. The goal is not to optimize a single journey, but to foster a resilient and adaptive long-term partnership.

AXD does not replace Service Design; it extends it. The two disciplines are complementary, and their intersection is a fertile ground for innovation. Service Design's tools and mindset remain invaluable for designing the 'human-facing' parts of an agentic system - the interfaces for delegation, the reporting dashboards, and the escalation workflows. These are, in essence, services provided to the principal.

Where AXD takes over is in designing the 'agent-facing' world: the architecture of autonomy itself. A service blueprint might be used to design the process for a human to delegate a task to an agent. But a delegation design framework would be used to structure what the agent does next. The former is about the human's experience of the delegation; the latter is about the agent's execution of it.

Ultimately, as agentic AI becomes more integrated into our lives, the most effective designers will be those who can operate across both disciplines. They will use Service Design to ensure the human experience is seamless and intuitive, while using AXD to ensure the underlying agentic systems are robust, trustworthy, and aligned with human intent. The future of design is not one versus the other, but a synthesis of both.