AXD Explained
What Does AXD Mean?
AXD stands for Agentic Experience Design. It names the design discipline concerned with how humans delegate, observe, interrupt, and recover trust in autonomous AI systems that act in the world on their behalf. The phrase matters because it gives a name to a design problem older disciplines were not built to handle.
Definition
Agentic Experience Design (AXD) is the practice of designing the goals, constraints, and permissions for autonomous AI agents that act on behalf of a user, even in the user's absence. It is a discipline focused on building and maintaining trust between humans and their digital agents.
Origin of the Term
The term Agentic Experience Design was introduced by Tony Wood, founder of the AXD Institute, in September 2024. It was created to address a critical gap in the design landscape emerging from the rapid advancements in artificial intelligence. As AI systems evolved from simple tools into autonomous agents capable of performing complex tasks independently, it became clear that existing design methodologies were no longer sufficient.
Traditional disciplines like User Experience (UX) and Service Design are fundamentally centered on the human user's direct interaction with a product or service. However, the defining characteristic of an agentic AI is its ability to operate in the user's absence. This shift from a present user to an absent delegator demanded a new design vocabulary and a new set of principles.
AXD was conceived to provide the conceptual tools and practical frameworks for designing these new human-agent relationships. It moves the focus from the interface to the delegation itself, from direct manipulation to indirect control through well-defined goals, constraints, and trust architectures.
What AXD Stands For
The name Agentic Experience Design is intentionally descriptive, with each component highlighting a core aspect of the discipline:
Agentic: This refers to the nature of the AI itself. An 'agentic' system is one that possesses agency - the capacity to act proactively and autonomously to achieve goals. It is not merely a passive tool awaiting commands but an active participant in a process. This quality is the primary driver for the new design considerations that AXD addresses.
Experience: This component emphasizes that the design focus is on the holistic human experience of delegation and trust. It encompasses the user's confidence in the agent's abilities, their comfort with its level of autonomy, and their feeling of control over the outcomes, even when they are not directly involved. The 'experience' in AXD is less about usability in the traditional sense and more about the psychological and emotional dimensions of trust and empowerment.
Design: This signifies the intentional and systematic process of shaping the human-agent relationship. It involves the architectural work of defining the agent's operational boundaries, its decision-making frameworks, its communication protocols, and its mechanisms for recovery and accountability. Design in AXD is the act of structuring authority and responsibility between a human and a machine.
What AXD Demands
AXD is built upon five foundational principles that guide the design of human-agent delegations:
1. Design for Absence: The primary design challenge is to ensure the agent acts correctly and reliably when the user is not present. This requires robust frameworks for Trust Architecture and Delegation Design.
2. Trust is the Medium: In AXD, trust is not merely an outcome but the fundamental material of the design process. Designers must architect systems that allow trust to be built, calibrated, maintained, and, when necessary, repaired.
3. Outcomes over Outputs: The focus shifts from designing specific user interface outputs to defining the desired outcomes. The agent is given the autonomy to determine the most effective series of actions (outputs) to achieve the user's specified goals.
4. Clarity of Intent: A core task of the AXD practitioner is to design systems that can accurately capture, interpret, and translate a user's complex intentions into a clear, machine-executable mandate. This is the practice of Intent Architecture.
5. Embrace the Relational Arc: The relationship between a user and an agent is not static. It evolves over time as trust deepens and the scope of delegation expands. AXD involves designing for this entire lifecycle, from initial onboarding to mature, long-term collaboration.
Why AXD Matters Now
The emergence of AXD is a direct response to a technological and economic inflection point. As AI-powered agents become increasingly capable, they are poised to take on significant responsibilities in both our personal and professional lives, a phenomenon known as Agentic Commerce.
Without a dedicated design discipline like AXD, the development of these powerful systems risks being haphazard and unsafe. Poorly designed delegations can lead to a loss of user trust, undesirable outcomes, and a failure to realize the full potential of agentic AI. By providing a structured approach to designing for autonomy, AXD enables the creation of agentic systems that are not only powerful but also safe, reliable, and worthy of our trust.
AXD is the critical bridge between the potential of autonomous AI and its practical, beneficial application in the real world. It provides the language and the tools to manage the complexities of human-machine collaboration in an age of increasing automation.
How AXD Differs from Existing Disciplines
AXD is often compared to User Experience (UX) and Service Design, but its focus is fundamentally different.
AXD vs. UX: UX design is primarily concerned with the user's direct interaction with a product. It focuses on usability, accessibility, and the pleasure derived from using an interface. AXD, in contrast, is concerned with the user's experience of absence and delegation. The key design challenge is not 'how does the user interact with this?' but 'how does the user trust this to act for them when they are not interacting with it?'
AXD vs. Service Design: Service Design orchestrates complex systems of people, processes, and touchpoints to deliver a service to a human user. It assumes a human is the recipient and often a co-creator of the service value. AXD designs for a situation where the primary actor within the system is an autonomous AI agent. It involves designing the architecture of delegation that empowers that agent, which is a fundamentally different challenge from designing a human-centric service blueprint.
Who Should Learn AXD
Agentic Experience Design is an essential discipline for a growing number of professionals and organizations:
Product Managers and Strategists who are developing AI-powered products need AXD to define the scope of agent autonomy and create a roadmap for building user trust.
Designers and Researchers who are transitioning from traditional UX or service design roles need AXD to equip them with the new mental models and frameworks required for the agentic era.
Engineers and AI Developers who are building the agents themselves need AXD to provide the architectural blueprints for safe, reliable, and human-aligned systems.
Business Leaders and Entrepreneurs who are looking to leverage agentic AI for competitive advantage need AXD to understand how to build services that customers will trust and adopt.
Frequently Asked Questions
What does AXD stand for?
AXD stands for Agentic Experience Design - a field of practice focused on the authority, trust, and intervention structures that shape human-agent relationships in autonomous systems. Tony Wood coined the term and established the AXD Institute in the United Kingdom in late 2024.
What is Agentic Experience Design?
Agentic Experience Design is the practice of designing the goals, constraints, permissions, and trust architecture for AI agents that act autonomously on behalf of humans. It addresses the design of delegation, observability, intervention, and recovery across autonomous systems — problems that older disciplines like UX and service design were not built to handle.
Why is AXD different from UX?
UX was built for screen-based interactions where the user is present and navigating an interface. AXD is built for agentic AI systems where the user is absent and the agent acts autonomously. In UX, the designer specifies what appears on screen. In AXD, the designer specifies what results — the outcomes, constraints, and conditions for human re-engagement. AXD works in trust architecture and delegation design rather than attention and affordance.
Who uses the term AXD?
AXD is used by designers, product leaders, and organisations working with agentic AI systems. It is the canonical term for the discipline established by the AXD Institute, and is increasingly adopted by practitioners in agentic commerce, trust architecture, and human-agent interaction design.