Designing For Agentic AI: Practical UX Patterns For Control, Consent, And Accountability
Source: Victor Yocco; Smashing Magazine · 2026-02-11
In the first part of this series, we established the fundamental shift from generative to agentic artificial intelligence. We explored why this leap from suggesting to acting demands a new psychological and methodological toolkit for UX researchers, product managers, and leaders. We defined a taxonomy of agentic behaviors, from suggesting to acting autonomously, outlined the essential research methods, defined the risks of agentic sludge, and established the accountability metrics required to navigate this new territory. We covered the what and the why.
Now, we move from the foundational to the functional. This article provides the how: the concrete design patterns, operational frameworks, and organizational practices essential for building agentic systems that are not only powerful but also transparent, controllable, and worthy of user trust. If our research is the diagnostic tool, these patterns are the treatment plan. They are the practical mechanisms through which we can give users a palpable sense of control, even as we grant AI unprecedented autonomy. The goal is to create an experience where autonomy feels like a privilege granted by the user, not a right seized by the system.
Designing for agentic AI is designing for a relationship. This relationship, like any successful partnership, must be built on clear communication, mutual understanding, and established boundaries.
To manage the shift from suggestion to action, we utilize six patterns that follow the functional lifecycle of an agentic interaction:
Pre-Action (Establishing Intent)The Intent Preview and Autonomy Dial ensure the user defines the plan and the agent’s boundaries before anything happens.
In-Action (Providing Context)The Explainable Rationale and Confidence Signal maintain transparency while the agent works, showing the “why” and “how certain.”
Post-Action (Safety and Recovery)The Action Audit & Undo and Escalation Pathway provide a safety net for errors or high-ambiguity moments.
Before an agent takes any significant action, the user must have a clear, unambiguous understanding of what is about to happen. The Intent Preview, or Plan Summary, establishes informed consent. It is the conversational pause before action, transforming a black box of autonomous processes into a transparent, reviewable plan.
Psychological UnderpinningPresenting a plan before action reduces cognitive load and eliminates surprise, giving users a moment to verify the agent truly understands their intent.
Trust is not a binary switch; it’s a spectrum. A user might trust an agent to handle low-stakes tasks autonomously but demand full confirmation for high-stakes decisions. The Autonomy Dial, a form of progressive authorization, allows users to set their preferred level of agent independence, making them active participants in defining the relationship.
Psychological UnderpinningAllowing users to tune the agent’s autonomy grants them a locus of control, letting them match the system’s behavior to their personal risk tolerance.
- The Explainable Rationale: Answering Why?
When an agent acts, especially autonomously, the immediate question in the user’s mind is often, Why did it do that? The Explainable Rationale pattern proactively answers this question, providing a concise justification for the agent’s decisions. This is not a technical log file. In my first article of this series, we discussed translating system primitives into user-facing language to prevent deception. This pattern is the practical application of that principle. It transforms the raw logic into a human-readable explanation grounded in the user’s own stated preferences and prior inputs.
To help users calibrate their own trust, the agent should surface its own confidence in its plans and actions. This makes the agent’s internal state more legible and helps the user decide when to scrutinize a decision more closely.
The single most powerful mechanism for building user confidence is the ability to easily reverse an agent’s action. A persistent, easy-to-read Action Audit log, with a prominent Undo button for every possible action, is the ultimate safety net. It dramatically lowers the perceived risk of granting autonomy.
Psychological UnderpinningKnowing that a mistake can be easily undone creates psychological safety, encouraging users to delegate tasks without fear of irreversible consequences.
Even the most advanced agent will encounter situations where it is uncertain about the user’s intent or the best course of action. How it handles this uncertainty is a defining moment. A well-designed agent doesn’t guess; it escalates.
Errors are not a possibility; they are an inevitability.
The long-term success of an agentic system depends less on its ability to be perfect and more on its ability to recover gracefully when it fails. A robust framework for repair and redress is a core feature, not an afterthought.
The initial goal is to build the bedrock of trust without taking significant autonomous risks. In this phase, the agent’s power is limited to analysis and suggestion.
Once users are comfortable with the agent’s proposals, you can begin to introduce low-risk autonomy. This phase is about teaching users how the agent thinks and letting them set their own pace.
This is the final step, taken only after you have clear data from the previous phases demonstrating that users trust the system.
Lines of inquiry this paper opens 24
Research framings built by reading the notes related to this paper — the questions it feeds into.
Can mechanistic interpretability reliably explain model reasoning and guide interventions? How does interface design shape effectiveness in human-AI collaboration?- How do Amershi's interaction-phase guidelines compare to concern-based AI UX frameworks?
- How do pre-action UX patterns prepare users for staged autonomy expansion?
- How can designers make control feel available without constant user oversight?
- Where does perceived control diverge from actual intervention capability in AI interfaces?
- How often do products ship all three control patterns together in practice?
- How do autonomy budgets map onto OpenAI's Model Spec scope requirements?
- Should a product override user autonomy settings when agent confidence is low?
- Can autonomy and perceived control both increase together in agentic system design?
- Can we measure whether a deployed agent meets the threshold for being truly agentic?
- Does moving users through autonomy levels require different interface patterns at each stage?
- Can autonomy granted to users ever be revoked if trust breaks down?
- How do discrete autonomy levels map to user-centered delegation preferences?
- How does an action receipt differ from capability disclosure and explainability in the trust workflow?
- What counts as clear data that users actually trust an agentic system?
- What makes users withdraw trust from AI agents they initially delegated to?
- What role does user trust play when evaluating unpredictable AI systems?
- How do stochastic outputs create mental model and trust problems for users?
- Can ambient visual signals replace explicit negotiation surfaces for AI trust?