The AXD Playbook: 12-Week Agentic Readiness Programme
The Playbook is the structured bridge between understanding agentic systems and operating them. It takes organisations from readiness assessment through trust architecture, delegation design, and observability to operational launch - in a sequenced 12-week programme designed for cross-functional teams. It does not assume you have done this before. It assumes you need to start now.
This playbook assumes familiarity with the AXD Manifesto, AXD Vocabulary, and Four Pillars of AXD Readiness. If you have not read those pages, start there.
01 · Content Structure Framework
The TRUST Framework
Where the AXO discipline uses CLEAR (Concise, Logical, Evidence-Based, Accessible, Referenceable) to optimise content for agent parsing, AXD operates at a deeper layer. The TRUST framework structures the design of the human-agent relationship itself - the delegation, calibration, observation, interruption, and recovery that govern every agentic experience.
T - Transparent
Every agentic action must be legible. Design for observability - not as a debugging afterthought but as a first-class experience requirement. The human must be able to understand what the agent did, why it did it, and what it considered but rejected. Transparency is the foundation of trust calibration.
R - Recoverable
Every agentic failure must have a designed recovery path. Trust recovery is not error handling - it is a relationship repair protocol. Design the path from failure to restored confidence: acknowledge, explain, compensate, demonstrate, and rebuild. The quality of recovery determines the durability of the relationship.
U - Understandable
The delegation contract must be comprehensible to the human principal. Scope, constraints, duration, conditions, and revocation rules must be expressed in terms the delegator can evaluate. If the human cannot understand what authority they are granting, the delegation is not designed - it is defaulted.
S - Scoped
Every delegation must have explicit boundaries. Scope is not a limitation - it is the grammar of trust. Define what the agent may do (positive scope), what it must not do (negative scope), under what conditions it must pause (conditional scope), and when the delegation expires (temporal scope). Unbounded delegation is not trust - it is abdication.
T - Temporal
Agentic relationships accumulate history. Trust is not a static setting but a dynamic state that changes with every interaction, every success, every failure, and every recovery. Design for the temporality of trust - initial calibration, progressive expansion, periodic review, and graceful degradation over time.
02 · Implementation Timeline
12-Week AXD Implementation Roadmap
This roadmap takes an organisation from zero AXD capability to a functioning trust-governed agentic experience. Unlike generic AI implementation timelines, this roadmap is structured around the Five Founding Principles of AXD: Intentional Delegation, Trust as Primary Material, Absence as Primary Use State, Relational Temporality, and Outcomes Replace Outputs.
Phase 1: Foundation
Weeks 1-3Principle: Agency Requires Intentional Delegation
Conduct an AXD Readiness Assessment using the Four Pillars diagnostic (Trust Architecture, Delegation Design, Agent Observability, Human Re-engagement) to establish your organisational baseline.
Map every existing human-agent interaction in your organisation - identify where delegation is explicit (designed) versus implicit (defaulted), and where trust is earned versus assumed.
Establish the AXD vocabulary within your team - the 64 canonical terms provide a shared language that prevents the discipline from being absorbed into generic UX or AI product management.
Assign AXD roles: Trust Architect (owns trust architecture), Delegation Designer (owns scope and authority), Observability Lead (owns agent legibility), and Re-engagement Designer (owns human return paths).
Define your organisation's trust architecture principles - what trust means in your context, how it is earned, how it is measured, and how it is recovered after failure.
Phase 2: Architecture
Weeks 4-6Principle: Trust Is the Primary Material
Implement the Intent Architecture Framework - design the translation layer between human intent and agent action, specifying how vague human desires become precise agent mandates.
Build your Delegation Design Framework - define the grammar of authority: what can be delegated, to what scope, under what conditions, with what revocation mechanisms, and for what duration.
Design your Trust Calibration system - implement the mechanisms by which trust levels are set initially, adjusted based on performance, and recalibrated after failures or context changes.
Establish your Operational Envelope - define the boundaries within which agents may act autonomously, the thresholds that trigger human re-engagement, and the circuit breakers that halt autonomous operation.
Create your Interrupt Pattern library - design the taxonomy of interruptions (informational, advisory, blocking, emergency) and the criteria that determine which pattern applies in each situation.
Phase 3: Implementation
Weeks 7-9Principle: Absence Is the Primary Use State
Implement Agent Observability - build the systems that make autonomous agent behaviour legible to humans who were not present when the agent acted, including structured logging, behaviour summaries, and decision traces.
Design the Autonomy Gradient for each agent interaction - map the spectrum from full human control through supervised autonomy to full agent autonomy, and define the trust thresholds that govern movement along the gradient.
Build your Trust Recovery protocols - design the specific sequences that restore trust after different categories of failure (minor deviation, significant error, trust violation, catastrophic failure).
Implement the Memory and Continuity Framework - design how agents maintain relationship context across sessions, how trust state persists, and how delegation history informs future interactions.
Deploy your Orchestration Visibility system - make the coordination between multiple agents and between agents and humans visible, traceable, and interruptible at every stage.
Phase 4: Maturity
Weeks 10-12Principle: Outcomes Replace Outputs
Implement outcome measurement - shift from measuring agent outputs (actions taken, tasks completed) to measuring outcomes (human satisfaction with delegated results, trust trajectory, relationship quality over time).
Establish your AXD governance framework - define who reviews trust architecture decisions, how delegation scope changes are approved, and how trust failures are investigated and remediated.
Conduct your first Trust Debt audit - identify where trust has been borrowed (assumed rather than earned), where trust recovery has been deferred, and where delegation scope has expanded without corresponding trust verification.
Train your organisation on AXD principles - move beyond the core team to embed trust architecture, delegation design, and human-agent interaction thinking across product, engineering, design, and leadership.
Establish continuous AXD improvement cycles - monthly trust architecture reviews, quarterly delegation scope audits, and annual AXD maturity assessments using the Four Pillars diagnostic.
03 · Team Structure
AXD Team Roles and Responsibilities
AXD implementation requires roles that do not exist in traditional UX, product, or engineering organisations. These roles are defined by the discipline's founding principles - they work in trust rather than attention, in delegation rather than interaction, and in outcomes rather than outputs.
Trust Architecture Team
Trust Architect: Owns the structural design of trust - how trust is established, measured, calibrated, and recovered across all human-agent relationships in the system.
Trust Recovery Designer: Specialises in failure response - designs the specific protocols that restore trust after different categories of agent failure, from minor deviations to catastrophic violations.
Trust Measurement Lead: Defines and implements the metrics that track trust state over time - trust trajectory, trust debt accumulation, recovery effectiveness, and calibration accuracy.
Delegation Design Team
Delegation Designer: Owns the grammar of authority - designs how humans specify scope, constraints, conditions, and revocation rules when granting authority to agents.
Intent Translator: Bridges the gap between vague human desires and precise agent mandates - designs the systems that convert 'find me something nice for dinner' into actionable agent specifications.
Scope Enforcement Engineer: Implements the technical systems that ensure agents cannot exceed their delegated authority - structural constraints, not just warnings or guidelines.
Observability and Re-engagement Team
Observability Designer: Makes autonomous agent behaviour legible to absent humans - designs the summaries, traces, and explanations that allow humans to understand what happened while they were away.
Re-engagement Designer: Owns the human return path - designs how humans re-enter the agentic experience after periods of absence, including context restoration, decision review, and authority reconfirmation.
Interrupt Pattern Designer: Designs the taxonomy and criteria for agent-initiated interruptions - when to inform, when to advise, when to block, and when to escalate to emergency human intervention.
AXD Governance Team
AXD Programme Lead: Coordinates the cross-functional implementation, manages the 12-week roadmap, and ensures alignment between trust architecture, delegation design, and observability workstreams.
Ethical Constraints Designer: Defines the value alignment boundaries - what agents must never do regardless of delegation scope, and how ethical constraints interact with commercial objectives.
Compliance and Audit Lead: Manages Know Your Agent (KYA) requirements, delegation audit trails, and regulatory compliance for autonomous agent operations in regulated industries.
04 · Quality Assurance
AXD Pre-Launch Checklist
This checklist operationalises the Five Founding Principles. Every item maps to a specific principle and a specific framework from the Practice section. An agentic experience that fails any critical item should not launch.
Trust Architecture
Principle: Trust Is the Primary Material
Trust is established through a designed onboarding sequence, not assumed from first interaction.
Trust levels are tracked as explicit state - the system knows the current trust level for every human-agent relationship.
Trust calibration mechanisms exist - the human can adjust trust levels up or down based on observed agent performance.
Trust recovery protocols are designed for at least three failure severity levels (minor, significant, catastrophic).
Trust debt is monitored - the system tracks where trust has been borrowed and flags relationships where trust recovery has been deferred.
Delegation Design
Principle: Agency Requires Intentional Delegation
Every delegation has explicit scope - what the agent may do, what it must not do, and under what conditions it must pause.
Delegation duration is specified - every grant of authority has a defined expiry or review trigger.
Revocation is immediate and propagating - when a human revokes authority, every agent in the delegation chain stops within defined time bounds.
The delegation contract is comprehensible - the human can understand and evaluate what authority they are granting before they grant it.
Delegation audit trails are maintained - every grant, modification, and revocation of authority is logged with timestamp, scope, and rationale.
Agent Observability
Principle: Absence Is the Primary Use State
Agent actions are logged with reasoning - not just what the agent did, but what it considered, what it chose, and why.
Behaviour summaries are generated at multiple levels of abstraction - from high-level outcome summaries to detailed action traces.
The human can reconstruct what happened during their absence without replaying every individual agent action.
Anomaly detection flags unusual agent behaviour for human review before it compounds into larger failures.
Post-mortem tooling exists - when failures occur, the full context can be reconstructed for investigation and learning.
Human Re-engagement
Principle: Relationships Have Temporality
The human return path is designed - when the human re-enters the experience, context is restored and decisions since departure are summarised.
Interrupt patterns are categorised (informational, advisory, blocking, emergency) with clear criteria for each level.
The system adapts to the human's re-engagement patterns - frequent reviewers receive different summaries than infrequent ones.
Authority reconfirmation is triggered after significant context changes, extended absences, or trust-relevant events.
The experience degrades gracefully when the human is unreachable - the agent reduces autonomy rather than proceeding with stale authority.
Outcome Specification
Principle: Outcomes Replace Outputs
Success is defined in terms of outcomes (human satisfaction, relationship quality) not outputs (tasks completed, actions taken).
The human specifies desired results, constraints, and conditions - not step-by-step instructions for the agent to follow.
Outcome measurement includes temporal dimensions - immediate results, medium-term relationship trajectory, and long-term trust accumulation.
Failure is defined in terms of outcome deviation, not just action errors - an agent that completes all actions but produces the wrong outcome has failed.
Outcome feedback loops exist - the system learns from outcome assessments to improve future delegation, calibration, and autonomous operation.
05 · Industry Applications
Industry-Specific AXD Applications
AXD principles are universal but their application is domain-specific. The trust architecture for a financial services agent managing investments differs fundamentally from the trust architecture for a retail agent selecting products. Each industry has different delegation boundaries, different trust calibration requirements, and different failure severity classifications.
Financial Services
Delegation boundaries are regulated - financial agents operate within regulatory frameworks (FCA, SEC, MiFID II) that define maximum delegation scope regardless of human trust levels.
Trust calibration requires fiduciary alignment - the agent's trust level must reflect not just performance history but alignment with the client's financial interests and risk tolerance.
Know Your Agent (KYA) is a regulatory requirement - financial institutions must verify agent identity, capability, and authority before permitting autonomous transactions.
Failure severity is amplified - a financial agent's error can cause irreversible monetary loss, making trust recovery protocols and circuit breakers critical infrastructure.
Retail and E-commerce
The machine customer is the central figure - agentic shopping agents act as autonomous customers, requiring merchants to design experiences for non-human buyers.
Signal clarity replaces visual merchandising - agents parse structured data, not browse attractive displays, so product information architecture becomes the primary competitive surface.
Delegation scope is preference-bounded - retail agents operate within taste, budget, and quality constraints that are difficult to specify precisely and evolve over time.
Trust is built through purchase satisfaction - the trust calibration loop in retail is outcome-driven: did the agent's selection match what the human would have chosen?
Healthcare
Non-delegatable decisions define the architecture - clinical decisions that require human judgement create hard boundaries in the delegation design that no trust level can override.
Trust calibration requires clinical validation - healthcare agents must demonstrate accuracy against clinical standards, not just user satisfaction, before trust levels increase.
Observability is a patient safety requirement - every agent recommendation, every data source consulted, and every alternative considered must be traceable for clinical audit.
Failure classification follows clinical severity - agent errors are classified by patient harm potential (no harm, near miss, adverse event, serious adverse event) with corresponding response protocols.
Professional Services
Delegation design mirrors professional hierarchies - legal, consulting, and advisory agents operate within authority structures that parallel human professional delegation patterns.
Trust is credentialed - professional services agents must demonstrate domain expertise before trust is granted, mirroring the credentialing requirements of human professionals.
Confidentiality constraints shape the operational envelope - professional agents handle privileged information, requiring delegation designs that enforce information boundaries.
Outcome specification is engagement-scoped - professional services agents operate within defined engagement parameters, and delegation scope resets between engagements.
06 · Measurement
AXD Measurement Framework
Traditional UX metrics (time on task, click-through rate, conversion) measure attention-based interactions. AXD metrics measure trust-based relationships. The shift from measuring what the human does on screen to measuring what the agent achieves in the human's absence requires a fundamentally different measurement architecture.
Trust Metrics
Trust Trajectory: The direction and rate of trust change over time - is trust accumulating, stable, or degrading? Measured as a time-series of trust state changes.
Trust Debt Ratio: The proportion of trust that has been assumed versus earned - high trust debt indicates fragile relationships that are vulnerable to single-point failures.
Recovery Effectiveness: How quickly and completely trust is restored after failures - measured as the percentage of pre-failure trust level recovered within defined time windows.
Calibration Accuracy: How well the system's trust level matches the human's actual confidence - measured through periodic trust surveys compared against system trust state.
Delegation Metrics
Delegation Scope Utilisation: What percentage of delegated authority the agent actually exercises - low utilisation suggests over-delegation, high utilisation suggests the scope may be too narrow.
Scope Violation Rate: How often agents approach or exceed delegation boundaries - a leading indicator of trust architecture stress that precedes actual failures.
Revocation Frequency: How often humans revoke delegated authority - high revocation rates indicate delegation design problems or trust calibration failures.
Intent Translation Fidelity: How accurately agent actions reflect human intent - measured by comparing agent outcomes against human-specified desired results.
Operational Metrics
Absence Duration: How long humans remain absent between re-engagement events - increasing absence duration indicates growing trust, decreasing duration indicates trust erosion.
Interrupt Appropriateness: Whether agent-initiated interruptions were warranted - measured by human assessment of whether each interrupt was necessary and correctly categorised.
Re-engagement Satisfaction: How effectively the human return path restores context and enables informed decision-making - measured through post-re-engagement surveys.
Outcome Alignment: How closely agent-achieved outcomes match human-specified desired results - the ultimate measure of agentic experience quality.
07 · Failure Patterns
Common AXD Implementation Failures
Most AXD implementation failures stem from applying traditional UX thinking to agentic problems. These are not edge cases - they are the predictable consequences of designing for attention when you should be designing for trust, and designing for presence when you should be designing for absence.
Trust Architecture Failures
Assumed Trust: Granting agents full autonomy from first interaction without a designed trust-building sequence. The agent has authority it has not earned, and the first failure destroys a relationship that was never properly established.
Missing Recovery: Designing the happy path without designing the failure path. When the agent fails (and it will), there is no protocol for acknowledgement, explanation, compensation, or rebuilding. Trust collapses permanently.
Static Trust: Treating trust as a one-time setting rather than a dynamic state. The system never adjusts trust levels based on performance, context changes, or the passage of time. Trust becomes stale and disconnected from reality.
Trust Debt Accumulation: Borrowing trust through defaults and assumptions without ever earning it through demonstrated performance. The relationship appears stable until a single failure reveals that the foundation was never built.
Delegation Design Failures
Unbounded Delegation: Granting authority without explicit scope, duration, or revocation mechanisms. The agent can do anything, for any duration, and the human has no designed way to stop it. This is not trust - it is abdication.
Incomprehensible Contracts: Delegation specifications that are technically precise but humanly incomprehensible. The human 'agrees' to a delegation they cannot evaluate, making informed consent impossible.
Irrevocable Authority: Delegation designs where revocation is technically possible but practically difficult - buried in settings, delayed in effect, or incomplete in scope. Revocation must be immediate and total.
Scope Creep: Gradual expansion of agent authority without corresponding trust verification. Each individual expansion seems small, but the cumulative effect is an agent operating far beyond the trust level the human has actually granted.
Observability and Re-engagement Failures
Invisible Autonomy: Agents that act without leaving legible traces. The human returns to find outcomes they cannot explain, decisions they cannot trace, and a system state they cannot understand. This is the opposite of designed absence.
Information Overload: Observability systems that log everything but summarise nothing. The human is presented with raw action logs instead of meaningful behaviour summaries, making re-engagement cognitively overwhelming.
Missing Return Path: No designed experience for the human's return. The human re-enters the system with no context restoration, no decision summary, and no mechanism to review or reverse agent actions taken during their absence.
Interrupt Fatigue: Agent-initiated interruptions that are too frequent, too urgent, or too trivial. The human learns to ignore interrupts, which means they also ignore the genuinely critical ones. Interrupt design requires the same rigour as trust architecture.
Implementation Summary
Structure: Use the TRUST framework to design every human-agent relationship around Transparency, Recoverability, Understandability, Scope, and Temporality.
Timeline: Follow the 12-week roadmap grounded in the Five Founding Principles - from foundation through architecture and implementation to organisational maturity.
Team: Establish AXD-specific roles (Trust Architect, Delegation Designer, Observability Lead, Re-engagement Designer) that do not exist in traditional UX organisations.
Quality: Validate every agentic experience against the pre-launch checklist before it reaches humans - trust architecture, delegation design, observability, re-engagement, and outcome specification.
Measure: Shift from attention metrics to trust metrics - trust trajectory, delegation scope utilisation, absence duration, and outcome alignment.