The shift from instructing to specifying outcomes. How users express intent, not procedure, and designers translate human goals into autonomous machine action..
| Dimension | Traditional UX | Agentic Experience Design (AXD) |
|---|---|---|
| Primary material | Attention and affordance | Trust and delegation |
| User state | Present, navigating | Absent, delegating |
| Design output | Screens and interfaces | Outcomes and constraints |
| Temporal model | Session-based | Relationship-based |
| Success metric | Task completion | Trust calibration |
Outcome specification is the practice of defining what results an autonomous AI agent should achieve, rather than prescribing how it should achieve them. In AXD, outcome specification replaces the traditional UX concept of output specification (designing what appears on screen) with a focus on what the agent should accomplish in the real world.
Traditional requirements specify outputs: screens, flows, interactions. Outcome specification defines results: the state of the world after the agent has acted. This shift is necessary because agentic systems operate autonomously - the designer cannot prescribe every step. Instead, they define the destination and the constraints, and the agent determines the route.
In agentic commerce, the agent must understand what the human wants to achieve, not just what buttons to press. Outcome specification enables this by defining success criteria (find the cheapest flight to Paris), constraints (departing Friday, returning Sunday), and quality thresholds (minimum 3-star airline). This allows the agent to exercise autonomous judgement within defined parameters.
Outcome specification is the practice of defining what results an autonomous AI agent should achieve, rather than prescribing how it should achieve them. In AXD, outcome specification replaces the traditional UX concept of output specification (designing what appears on screen) with a focus on what the agent should accomplish in the real world.
Traditional requirements specify outputs: screens, flows, interactions. Outcome specification defines results: the state of the world after the agent has acted. This shift is necessary because agentic systems operate autonomously - the designer cannot prescribe every step. Instead, they define the destination and the constraints, and the agent determines the route.
The history of human-computer interaction is a story of layers of abstraction. We moved from punch cards to command lines, from text-based interfaces to graphical user interfaces. Each step was a move away from the machine's language and closer to our own, a process of hiding complexity to enhance usability. But the GUI, for all its intuitive power, represents a plateau. It perfected the art of the journey - the clicks, the taps, the drags - while leaving the destination largely in the hands of the user to navigate. We became expert pilots of our digital vehicles, but we still had to manually plot the course, turn by turn. Agentic Experience Design proposes the next abstraction: a shift from designing the journey to designing the destination. At the heart of this paradigm is We are moving beyond the screen, beyond the interface, and into a world where our primary interaction with the digital realm is to simply state what we want to achieve, leaving the "how" to the agentic systems we design. For three decades, the graphical user interface has been the undisputed king of human-computer interaction. It gave us windows, icons, menus, and pointers, a visual vocabulary that made computing accessible to billions. But the kingdom is facing a crisis. The very success of the GUI has created a world of overwhelming complexity. The digital tools meant to simplify our lives now demand our constant attention, forcing us to become perpetual administrators of our own digital existence. We navigate a labyrinth of apps, each with its own logic, its own demands, its own microscopic journey to master. This is the tyranny of the interface: it forces a cognitive overhead that scales with capability. The more a system can do, the more we must learn, manage, and directly manipulate. It is like being given a starship with a million buttons and levers, but no autopilot. The potential is limitless, but the cognitive burden is crushing. The interface, once a window of opportunity, has become