From User Journeys to Agent Journeys: Rethinking Experience Design for AI Systems

For decades, journey maps charted what humans did, felt, and struggled with across the arc of an experience. They were the cartography of attention, frustration and delight. But in 2026, our users aren't just human anymore — AI agents are planning, deciding, and acting alongside (and sometimes instead of) them. The discipline of UX is being rewritten in real time, and journey mapping sits at the centre of the transformation. What follows is a practical playbook for the teams trying to design for this new reality.

From Human-Centred to Agent-Centred: Why UX Is Being Rewritten

The shift underway is more than incremental. Practitioners are calling it UX 2.0 or Agent Experience (AX) — a discipline that treats AI agents as first-class users of the systems we build. As Smashing Magazine put it earlier this year, when systems plan, decide and act on our behalf, UX moves beyond usability testing into the realm of trust, consent, and accountability. The old questions (Is it usable? Is it desirable?) still matter, but they now sit alongside new ones: Did the agent act within its mandate? Did the user understand what happened? Can the action be reversed? Designers are no longer just shaping screens — they are shaping delegation, governance and the choreography between humans and machine collaborators.

Two Journeys, One Map: The Human and the Agent

Journey mapping now runs in two directions at the same time. The first is the human-AI collaborative journey, which tracks what users do, think, and feel, plus where AI agents step in, help out, or take over. The second, explained by Leonie Monigatti in her Agent Journey Map work, treats the agent itself as a user of your software. Developer Experience changed how we design APIs, and now Agent Experience is changing documentation, tools, error messages, and login flows so machines can use them reliably. What does this mean in practice? Your team might need two journey maps for one feature: one showing the human's emotional path, and another tracing the agent's route through your APIs, tools, and guardrails.

The Three Coordination Zones of Human-AI Collaboration

One of the most useful frameworks to emerge this year comes from Amazon Science, which proposes three coordination zones for calibrating how much autonomy an agent should have at any given moment:

• Done-with-me: collaborative co-execution, where the human and agent work side by side in real time.

• Done-for-me: delegated autonomous action, where the agent completes a task on the user's behalf and reports back.

• Done-under-me: background operation, where the agent works invisibly within a larger workflow.

The framework is paired with the concept of responsive salience — adapting the visibility of the agent based on the user's context, expertise, and accumulated trust. A new user might see every step the agent takes; a seasoned user might only see the result. Crucially, salience is not static. It dials up when stakes rise and dials down when the system has earned confidence.

Core Principles for Designing Agent Experiences

A few key principles keep showing up across the research. Explainability is a must — people need to know what the agent did, why it did it, and how sure it was. Consent and accountability matter at every big step, especially when agents spend money, send messages, or touch personal data. Empathy and humanity still count too; even when an agent works on its own, the experience should feel respectful and responsible. Behind all of this sits the classic tug-of-war between autonomy and control — the agent needs enough freedom to actually help, but not so much that users feel out of the loop. Get this balance wrong and you end up with a system people either don't trust or have to babysit until it's useless.

UX Patterns That Are Actually Shipping in 2026

Theory is helpful, but designers want to know what actually works in real products. Mantlr's roundup of 10 UX patterns for agent experiences points out a few that keep showing up in shipped apps:

• Status and progress indicators that show what an agent is doing, so long tasks don't feel like a black box.

• Confirmation checkpoints before big actions like sending, paying, deleting, or publishing.

• Interruptibility and smooth handoff, letting users jump in, take over, or redirect the agent without losing their place.

• Hybrid chat-and-visual interfaces that mix plain language with real UI pieces like tables and previews.

• Confidence signals that show how sure the agent is, so users know when to trust it and when to double-check.

These patterns are quickly becoming the bare minimum. Teams that skip them often see their agents abandoned — not because the agents can't do the job, but because users can't tell what they're doing.

A New Research Playbook for Agentic Systems

Old-school usability testing — things like task completion, time spent, and satisfaction scores — only shows a tiny part of what matters for agentic systems. As Victor Yocco points out in Smashing Magazine, researchers now need to study long, multi-step tasks that people hand off to agents, where the key moments might play out over days instead of minutes. They also need to measure trust calibration — does the user's confidence in the agent go up and down in the right way as it succeeds or fails? And they need to look at accountability flows: when something goes wrong, who spots it, who fixes it, and how fast? Diary studies, long-term trust check-ins, and red-team tests focused on misuse and edge cases are quickly becoming go-to tools in the agent UX research kit.

Practical Takeaways for UX Teams

If your team is starting to design for agents, a few clear steps will help right away.

First, map both journeys — the human's and the agent's — and look for where they overlap, clash, or hand off to each other.

Second, sort every agent action by coordination zone (done-with-me, done-for-me, done-under-me), then decide how visible each one should be.

Third, build a checkpoint list: figure out which actions need confirmation, which need a notification, and which can just run quietly in the background.

Fourth, use research methods that track trust over time, not just how happy someone felt after one session.

Finally, work with engineering and policy teams early on. Agent UX choices are also governance choices, so you can't solve them alone inside a design tool.

Conclusion

Agent journey mapping is not a replacement for human-centred design — it is its natural evolution. The discipline still begins with empathy, still tries to reduce friction, still aims to create experiences people trust. What has changed is the cast of characters: the user is no longer alone on the map, and the agent has its own arc to consider. The teams that thrive in this new landscape will be the ones that learn to design for both. So the question worth asking your team this quarter is this: how will you reorganise your design, research and engineering practices to take the agent seriously as a user — without ever losing sight of the human it serves?