Source: Unsplash
Something fundamental has shifted in product design: the primary user of your software may no longer be human. AI agents are now interpreting interfaces, executing workflows, and making decisions autonomously across enterprise software at unprecedented scale. This is Machine Experience (MX) design, and most product teams have no idea how to approach it. In this article, I break down what MX means, why traditional UX frameworks fall short, the design patterns that actually work in 2026, and what every product designer needs to start doing differently right now.
I have been in product design for over eight years. I have shipped 42 products across Fortune 500 companies, worked on AI interfaces at Apple, and spent the last few years focused almost entirely on what I call AI-native UX. I have watched design practices evolve through mobile-first, then voice-first, and now we are at something far more disorienting: agent-first.
The numbers make it undeniable. According to Gartner, 40% of enterprise applications will embed task-specific AI agents by end of 2026, up from less than 5% just last year. The global agentic AI market has already surged past $9 billion. 51% of enterprises have AI agents running in production right now, and another 23% are actively scaling them. Salesforce's Agentforce platform alone is running 3 billion automated workflows monthly across 18,500 enterprise customers.
These agents are not just retrieving data. They are navigating interfaces, clicking buttons, filling forms, and making decisions on behalf of users. They are, in every meaningful sense, users of your software. And they are nothing like human users.
"In Machine Experience design, minimalism means well-structured data and clear hierarchy. Machines need to understand exactly what an object is, its current state, and what actions are possible. Clear logic is the new clean design."
— Smartters MX Design Report, 2026
What Machine Experience (MX) Design Actually Means
MX is how well your software is structured so AI agents, bots, and automation tools can understand, navigate, and act on it without relying on visual interfaces. Where UX asks "is this easy for a human to use?", MX asks "can a machine understand what this is, what state it is in, and what actions are possible?"
Those are very different questions. A beautifully designed dashboard with gradient cards, animated charts, and micro-interactions might score a 9 out of 10 on UX. That same dashboard might score a 2 on MX if the underlying data has no semantic structure, the actions are buried in nested menus, and there is no API surface for an agent to invoke actions programmatically.
I have run into this problem directly on products I have built. We designed something that users loved in testing. Clean interface, great information hierarchy, thoughtful interactions. Then we tried to add an AI agent layer on top, and it was a disaster. The agent could not reliably identify what state the workflow was in. The action labels were human-friendly but not machine-parseable. The data lived in four different components with no consistent schema. We had to go back and rethink core parts of the architecture.
That experience, which I have seen repeated at multiple companies now, taught me that MX is not a feature you add later. It is a design constraint you build in from the start.
via GIPHY
Why Traditional UX Frameworks Break Down
The entire canon of UX design assumes a human in the loop. Nielsen's heuristics talk about error recovery and user control because humans make mistakes and want to feel in charge. Don Norman's affordances are about visual signals that help humans understand what to do. Information architecture is optimized for how human cognition processes hierarchy and navigation.
None of this maps cleanly to agents. An AI agent does not care if a button looks clickable. It cares whether the button has a reliable, machine-readable label and whether clicking it produces a deterministic, parseable outcome.
Smashing Magazine published a detailed piece in February 2026 on agentic UX patterns. Three design patterns came out consistently across user testing and enterprise deployments:
- Plan-and-execute transparency: Agents need to show their work. Before taking an action, the agent presents its plan to the human user for review. This is not just a safety feature. It is a core trust mechanism. Users who can see what the agent plans to do before it does it are far more comfortable granting it higher autonomy over time. The UX challenge is making this plan review feel lightweight, not like a compliance checkbox.
- Confidence signaling: Agents operate with probabilistic certainty, not binary yes or no. A well-designed agentic interface communicates confidence levels visually, so users know when to pay attention. Low confidence should surface the action for human review. High confidence should allow the agent to proceed autonomously. Designing this spectrum, not just an on/off toggle, is one of the hardest MX problems I have worked on.
- Progressive delegation: This one is elegant. Rather than demanding full autonomy from the start, the agent starts in a supervised mode. As it builds a track record of correct decisions, it earns more autonomy. One enterprise team described hitting a threshold where after the agent got 40 consecutive suggestions right, they switched it to auto-execution with notifications rather than approval gates. The design pattern makes trust feel earned, not assumed.
What This Means for How We Build Products
If you are a product designer today and you are not thinking about MX alongside UX, you are building for half your user base. Here is how I approach it on current projects:
First, every data object in your product needs a clear identity and state. What is this thing? What state can it be in? What transitions are possible? This is just good data modeling, but most design teams leave it entirely to engineering. MX design means designers need to own this semantic layer too. When I design a workflow screen now, I am explicitly annotating the states and valid actions alongside the visual design, not as a separate spec document but as part of the design artifact itself.
Second, action surfaces need to be both human-friendly and agent-accessible. In practice, this often means working closely with your API team during design, not after. If an action exists in the UI, there should be a corresponding API endpoint that an agent can invoke. If that endpoint does not exist, that is a design gap. I have started flagging these gaps in design reviews the same way I flag accessibility gaps.
Third, feedback loops matter more than ever. When an agent takes an action, the system needs to confirm clearly what happened and what state things are in now. Ambiguous or delayed feedback is fine for human users who can read context and wait. Agents need deterministic, immediate confirmation. Building this into your component library early saves enormous pain later.
The Opportunity Nobody Is Talking About
There is a real competitive advantage for design teams that get ahead of this. Most enterprise software teams are still treating MX as an engineering problem. They are building agent support as an API layer bolted onto existing products, without redesigning the core experience to support agents natively.
Microsoft's Design team published guidance on UX for agents in 2026, and the key insight is that the products winning in the agentic era are not the ones with the most capable AI underneath. They are the ones with the clearest, most consistent, most machine-readable interface layer on top. The AI is commodity. The interface architecture is the moat.
Salesforce understood this. Their Agentforce platform is built around the idea that agents need a consistent, structured surface to work against, not a retrofitted API. The result: $540 million in ARR, 18,500 enterprise customers, and 3 trillion tokens processed. That is not a coincidence. It is the business outcome of treating MX as a first-class design concern from day one.
How to Start Shifting Your Design Practice
You do not need to tear down what you have. Start by auditing your current product through an MX lens. Pick one core workflow and ask these questions: Can an AI agent identify every element on this screen and understand its purpose? Are the actions available on this screen clearly labeled and consistently placed? If an agent takes an action, will it receive clear, structured feedback? Is there an API surface that mirrors the UI surface?
The gaps you find in that audit are your MX design backlog. Prioritize them the same way you would prioritize accessibility issues, because in 2026, they are basically the same class of problem. Agents and assistive technologies both depend on semantic structure, consistent labeling, and predictable behavior.
I wrote more about specific MX design patterns and the component-level changes needed on the reloadux blog and over at medium.com/@iahmadullahcs, where I break down how to structure your design system for agentic workflows. If you are actively working through this, those posts are worth reading alongside this one.
The designers who will matter most in the next three years are not the ones who can make the most beautiful screens. They are the ones who understand both sides of the interface: what the human sees and what the machine needs. That is the new scope of our craft. And honestly, it is the most interesting design problem I have worked on in years.
Are you designing for AI agents in your current product? Have you run into MX challenges that traditional UX thinking could not solve? Drop your experience in the comments below. I want to know what the rest of you are seeing on the ground.
Sources: Gartner 2026 Enterprise App Predictions (gartner.com), Smashing Magazine "Designing Agentic AI: Practical UX Patterns" (smashingmagazine.com, Feb 2026), Smartters MX Design Report 2026 (smartters.in), Microsoft Design UX for Agents (microsoft.design), Salesforce Agentforce 2026 Data (salesforce.com), VentureBeat Salesforce Enterprise Growth (venturebeat.com), Tech Insider Agentic AI Enterprise Market 2026 (tech-insider.org), Ringly AI Agent Statistics 2026 (ringly.io), Pragmatic Coders UX to AX Design Guide (pragmaticcoders.com)