Designing the Judgment Layer: How UX Governs AI Autonomy

Defining the Judgment Layer

To better understand this shifting landscape, it is useful to consider the following four layers that are emerging in AI-enabled systems:

1. Generation—Produces content or user interfaces.
2. Recommendation—Suggests the next actions.
3. Autonomy—Executes decisions.
4. Judgment—Determines when automation is appropriate.

While the first three layers increasingly involve AI, the fourth remains deeply human. UX designers are uniquely qualified to shape the judgment layer because it requires balancing competing concerns such as user goals, organizational risk tolerance, ethical implications, cognitive load, and trust calibration. As I described in my UXmatters column, “Ensuring the Staying Power of User Experience in Your Organization,” UX professionals often possess many transferable skills that favor our ability to shape judgment when it comes to AI. After all, although AI can generate outputs, it might not understand consequences in the way that UX designers must.

Manufacturing Purposeful Friction

For years, UX design practice has emphasized reducing friction. We’ve optimized for speed, efficiency, and seamlessness and have celebrated moments when the user interface “gets out of the user’s way.” Remember the old axiom that states most effective user interfaces are essentially invisible? Such user experiences are so seamless and easy that any user interface or experiential construct fades into the background.

But AI complicates this principle. When systems begin making probabilistic decisions, removing friction entirely can introduce greater risk and uncertainty. Thus, it becomes important to manufacture friction where it makes sense. Protective friction can take multiple forms, as follows:

• reflection friction—Prompts users to confirm consequential decisions.
• transparency friction—Reveals how a system has arrived at a recommendation.
• accountability friction—Makes visible who or what is responsible for an outcome.

Rather than eliminating friction entirely, UX designers must calibrate friction appropriately. The goal is not resistance to automation, but alignment between system capabilities and human expectations. The need to reduce friction mirrors a broader pattern that I explored in my UXmatters column, “Embracing Boredom”: Environments that we’ve optimized for constant efficiency often undermine reflection, attention, and judgment—precisely the qualities we now need AI‑mediated systems to support.

Designing for Probabilistic Systems

Historically, most software solutions have behaved deterministically. If a user clicked a button or link, the system executed a predictable function. Now, AI systems behave differently, generating outputs probabilistically, often conveying confidence levels rather than guarantees—even though they tend to provide information in overtly confident ways. AI can recommend actions, prioritize information, and in some cases, initiate workflows autonomously. As a result, our primary design outputs are changing. UX designers no longer just design workflows, screens, affordances, and navigation models. We’re now designing the following:

• decision boundaries
• confidence thresholds
• escalation paths
• intervention mechanisms

The UX designer’s role is expanding from shaping interactions to shaping authority. When systems begin recommending or taking action on behalf of users, UX designers must address new questions such as the following:

• When should the system suggest versus decide?
• When should the system ask for permission?
• When should the user be able to override the system?
• What level of confidence is necessary before automation should occur?

These questions extend beyond usability into governance, which I’ll get to later in this column. While traditional usability heuristics emphasize consistency, AI introduces variability. Thus, it is becoming increasingly critical to help users understand what the system has done, why it did it, how confident it was, and how to change the outcome. Designing for probabilistic systems represents an expansion of familiar UX principles into new territory.

Planning for Composition in an Era of Open, Interoperable Systems

We’re increasingly seeing a shift away from monolithic, vendor‑controlled, single-point solutions and more toward customer‑assembled ecosystems that they’ve built upon interoperable services and application-programming interfaces (APIs). This paradigm shift is also becoming evident in industrial automation, on which my career has focused for many years. Rather than a single provider owning the full experience surface, we now create value through participation in modular platforms that enable customers, partners, and intelligent agents to compose solutions dynamically.

This shift is already visible in API‑first architectures, open standards for AI agents, and the growing availability of AI‑assisted development tools. For example, we can now use natural‑language programming tools to assemble—or vibe code—personal dashboards that integrate data and insights from multiple health and fitness platforms, services, and devices, often without direct involvement from the original vendors. This is a big win for users who want a single pane of glass for all their health data. However, scenarios like this can lead to ambiguity for UX designers, who can no longer assume a fixed application boundary or a fully knowable set of user journeys.

Instead, UX designers must focus on designing the conditions for composition: clear affordances, visible system behaviors, trustworthy data exchanges, and mechanisms that support human and machine judgment across contexts that the original designers did not—and could not—fully anticipate.

You might wonder what designing for unpredictable, composable ecosystems looks like. At a high level, it’s important to remember that UX design does not disappear—it relocates, moving further upstream. Consider the following tips to ensure users’ success, regardless of what conditions they create, whether intentionally or unintentionally.

• Design data as a user interface. Treat every exposed data object as a user‑facing artifact that has meaning, intent, and clarity, even when there is no user interface attached or associated with it.
• Name for human understanding. Use field names and labels that reflect real‑world concepts, not internal system or engineering terminology and jargon.
• Expose context with the value. Include metadata such as freshness, confidence, source, and assumptions, ensuring that we need not interpret numbers in isolation and, thus, provide adequate context.
• Differentiate signal types. Clearly separate raw observations, evaluated assessments, and recommended actions to reduce judgment ambiguity.
• Make constraints explicit. Document what we should not compare, combine, or infer to prevent unsafe or misleading compositions.
• Design for reuse, not completion. Assume the extraction, remixing, and partial use of your data or capability outside its original workflow.
• Support judgment, don’t eliminate it. Design outputs that help humans and AI agents know when to trust, question, or defer decisions.
• Assume unknown orchestrators. Design as if tools, agents, or systems that you’ll never see or control will consume your work.
• Shift UX design upstream. Participate in schema design, API contracts, and architectural reviews, defining meaning early and implicitly.
• Own the decision space. Focus UX design efforts on shaping what decisions your system’s outputs should enable, discourage, or constrain.

Ensuring AI Decision-Making Remains Visible

As is often true for user interfaces, invisible AI isn’t always better AI. Many organizations aim to make AI feel magical and invisible, but invisibility can undermine users’ trust and create a black-box perception for them. When users can’t see how an AI is making decisions, they can’t evaluate whether those decisions align with their goals.

Visibility doesn’t necessarily mean or require exposing technical complexity. Visibility requires communicating the scope of system responsibility, its confidence level, and opportunities for human intervention. In most cases, users don’t need to understand how an algorithm works. They need to understand when they should pay attention.

Reframing UX Design as Governance

AI will undoubtedly change aspects of UX design practice. Tasks involving the production of artifacts may become faster or be fully automated. However, faster production doesn’t reduce the need for judgment. In fact, it increases this need and determines how we should govern it. Think of this as a scale: As we reduce the cost of generating options, we increase the cost of selecting wisely. Therefore, UX designers must help organizations to determine the following:

• which decisions we can automate safely
• which decisions require human oversight
• which decisions require human discretion

These are not purely technical questions. They involve understanding context, consequences, and tradeoffs. This is where UX design increasingly intersects with governance. UX designers should influence how much autonomy systems possess, when to notify users of system actions, how to surface system errors, and how to structure accountability. These are the decisions that shape the relationship between humans and intelligent systems.

AI then reinforces the positioning of UX design as integral to early organizational decision-making rather than as a downstream production function—a practice that sadly still plagues many organizations today. At the end of the day, while AI might automate some aspects of user-interface production, it doesn’t eliminate the need for human judgment, contextual reasoning, ethical consideration, or understanding human behavior.

Rather than diminishing the role of UX design, AI can—and should—expand its scope. Since UX designers are typically responsible for defining how intelligent systems interact with human judgment, we’re in a great position to shape the future of this incredible new technology.

Conclusion

AI changes the surface of UX design work, but it reinforces and even reshapes the underlying purpose of UX design. We help organizations make better decisions about how technology can serve human needs. As AI systems generate user interfaces and design recommendations, the UX designer’s role evolves from crafting screens to defining boundaries.

Furthermore, UX design is becoming less about pixels, outputs, and frictionless interactions and more about principles, oversight, and calibrated user trust. UX designers have navigated complexity and ambiguity before. AI simply introduces a new form of ambiguity. With it emerges an opportunity for UX designers to define how intelligent systems should support rather than supplant human judgment.

Now, I’d like to hear from you. How are you governing AI autonomy through the lens of UX design? Please share your comments!