[002] The Interface Used to Protect Us From Bad Design Decisions. AI Removed the Buffer.
For two decades, screens absorbed our mistakes. That era is over.
Picture this.
A mother sits on her couch at 9pm. Kids finally asleep. She opens a travel app. She is looking for a family vacation — somewhere the kids will talk about for years. Not a beach resort. An adventure. She has $3,000 and a week in July.
In the old world, she scrolls. She filters. She reads reviews. She opens six tabs. The interface is clunky, but it gives her control. She finds what she wants — eventually. The app did not understand her. But it gave her enough room to understand herself.
Now picture the new world.
She tells the AI agent: “Plan a family trip for late July, under three thousand dollars.”
The AI books a beachfront all-inclusive in Cancun. Four-star reviews. Under budget. Technically perfect.
Her kids wanted to see bears in Yellowstone.
The system executed flawlessly. And it got the job completely wrong. Because nobody defined what “family vacation” meant for this family.
The Real Shift Is Not AI Itself. It Is Where Your Understanding Goes.
Something has changed in design. Not the tools — tools change constantly and designers adapt. Not AI being added to products — that has been happening since recommendation engines and autocomplete.
The change is more specific. And understanding exactly what shifted matters more than the broad-strokes version of this story.
A quick history, with a correction built in.
UX 1.0: Can the user figure it out? The web was new. Software was confusing. The designer’s job: make things learnable and functional. Nielsen’s heuristics. Information architecture. User testing. Success meant the user could complete the task.
UX 2.0: Does the user feel good doing it? Digital products matured. Competition intensified. Usability became table stakes. The job expanded: delight, emotion, brand coherence. Journey mapping. Design systems. Jobs-to-be-Done research. Success meant the experience felt right.
UX 3.0: What is “it” — at the level of human intent? AI handles the mechanics. The designer’s job shifts to defining what the system should actually accomplish for the human it serves.
Here is the correction. The idea of designing from user intent is not new. Good designers have always done this. Jobs-to-be-Done theory was formalized in the 1990s. Don Norman wrote about designing for human goals in 1988. The best UX practitioners in the 2.0 era were not just designing flows — they were understanding the deeper motivations behind them.
So what actually changed?
Same Research. Different Destination.
The method has not changed. The destination has.
In the 2.0 era, a designer who deeply understood user intent used that understanding to design a better interface. The intent informed the layout. The navigation. The labels. The flow. But the user still operated the interface. The designer’s understanding was translated into screens. Users interacted with those screens to reach their goal.
The interface was the medium through which intent became action.
In the 3.0 era, AI receives intent more directly. The user says “find me a flight to Tokyo for next month, under $800, with no more than one stop.” The system acts. The interface does not disappear — but for many interactions it becomes thinner. Optional. A confirmation layer rather than an operational one.
This changes where the designer’s understanding of intent needs to go.
Instead of translating intent into screen layouts, designers now translate intent into the parameters that govern AI behavior.
SYSTEM SPEC: Intent-to-Parameter Translation
2.0 Output:
- Wireframes, prototypes, screen flows
- Navigation architecture
- Visual hierarchy and interaction patterns
3.0 Output:
- Structured job statements (functional/emotional/social)
- Success criteria specific enough for AI optimization
- Autonomy boundaries (delegate vs. control)
- Context triggers (when the same request means something different)
- Constraint hierarchies (what matters most, second-most, least)
Input (unchanged):
- Deep user research
- Contextual inquiry
- JTBD interviews
- Behavioral observation
Key Difference:
- 2.0: Understanding → screens → user operates → goal achieved
- 3.0: Understanding → parameters → AI operates → goal achieved
The research is identical. The same interviews. The same frameworks. The same deep listening.
What changed is what the designer does with the output. Not a better filter UI. A set of decision parameters for an autonomous system.
The Shock Absorber Theory of Interface Design
This is the part that is genuinely new. And it changes everything.
In the 2.0 era, if a designer’s understanding of user intent was slightly off, the interface absorbed it. A well-designed navigation gave users enough control to find their own way — even when the designer had not perfectly anticipated their path. A clear layout let users scan and self-correct.
The interface was a shock absorber. It sat between imperfect design decisions and user goals. It absorbed the bumps.
Think of it physically. A car with good suspension handles rough roads. The driver barely notices the potholes. The ride is smooth enough. The shock absorber does not fix the road. It makes the road survivable.
The interface did the same thing for design decisions. Imperfect understanding? The user could still navigate. Wrong assumptions about priority? The user could reorder their own workflow. Missed context? The user could fill in the gaps manually.
When AI handles execution, that shock absorber is gone.
The driver is no longer driving. The AI is. And it is driving at full speed over every pothole the designer left in the road — because it does not know they are there.
If the intent has been modeled incorrectly. If the success criteria are defined imprecisely. If the constraints are specified incompletely. The AI acts on that wrong model. Confidently. At speed. Sometimes irreversibly.
The imprecision that a good interface could absorb becomes a system failure when AI executes on behalf of the user.
The quality of intent understanding is no longer just good practice.
It is structural. It determines whether the system works or does not.
One Family. Two Eras. The Difference Is the Buffer.
Let me make this concrete.
A user wants to book a family vacation. In the 2.0 world, a designer researching this user learns: they find too many options overwhelming. They want to feel confident in their choice. They care more about their kids’ experience than price.
The 2.0 designer uses this to build a better booking interface. Fewer options surfaced at once. Clear social proof. Filters that highlight family-friendliness.
The user still makes every decision. The designer made the decision-making environment better.
In the 3.0 world, an AI agent books this vacation. For the AI to do its job well, the designer needs to have defined something structured enough to act on:
SYSTEM SPEC: Family Vacation Agent — Intent Model
Job Statement:
“Create a family vacation the kids will remember”
Success Criteria:
- Kids report enjoying the experience (functional)
- Parents feel it was worth the investment (emotional)
- Family creates shared memories (social)
Constraints:
- Budget: $3,000 max
- Dates: July 20–27
- Travel: Max 4-hour flight
- Type: Adventure/exploration, NOT resort/beach
Priority Hierarchy:
1. Experience quality (highest weight)
2. Price
3. Convenience (lowest weight)
Autonomy Boundaries:
- DELEGATE: Flight search, hotel search, itinerary drafting
- CONTROL: Final confirmation before any booking
- ESCALATE: If budget conflict with experience quality
Context Triggers:
- If kids are under 6 → prioritize logistics ease
- If anniversary falls during trip → add one adults-only evening
- If user has booked adventure trips before → increase autonomyThis is the intent translated into system parameters. The AI uses this structure to decide which options to surface. What to prioritize. When to ask versus when to act.
The research that produced this understanding looks identical to 2.0 research. The same interviews. The same JTBD framework. The same deep listening.
The difference: the output is not a better filter UI. It is a set of decision parameters for an autonomous system. And if those parameters are wrong, there is no interface to catch the mistake.
Three Shifts That Define the New Era
What the designer builds is changing.
Alongside wireframes and prototypes, the artifacts that matter now include: intent models, agent role definitions, autonomy parameters, success criteria frameworks. These are not peripheral. They are often what determines whether the system works.
Where the highest-leverage design decisions live is changing.
The most important decisions now happen before Figma opens. What does this system need to understand about the user to act well on their behalf? What should it do autonomously? What should it surface for human decision? What does success look like — in terms specific enough that an AI can optimize for it?
The cost of imprecision is changing.
A slightly wrong mental model produced a slightly confusing interface. Users worked around it.
A slightly wrong intent model produces an AI that confidently does the wrong thing. At speed. At scale.
The stakes of getting the understanding right have increased by an order of magnitude.
The Core Has Not Changed. The Consequences Have.
The fundamental discipline is the same: understanding people deeply enough to know what they are actually trying to accomplish in their lives. Not just what they are doing in your product.
This has always been the core of good design. JTBD. Contextual inquiry. Ethnographic research. The five whys. All tools for getting past surface behavior to underlying intent.
That work is unchanged.
What changed is that this understanding is now the direct input to system behavior — not a step removed through interface design. The quality of the understanding is more exposed. More consequential. More directly testable.
The AI either acts correctly on the intent. Or it does not.
There is no interface to soften the gap.
Good designers have always known that understanding intent was the job. UX 3.0 makes that true for the whole system — not just the human doing the design.
The One Question That Reorients Everything
If you are trying to orient yourself to this shift, the most useful question is not “what tools should I learn?”
It is this:
If an AI were going to act on behalf of my user, what would it need to know?
Not just what the user wants to do. What they are trying to accomplish. What success looks like. What they want to control. What constraints matter and which do not. What context would change everything.
SYSTEM SPEC: The Reorientation Exercise
Step 1: Pick one user task your product handles today
Step 2: Imagine an AI agent will handle it autonomously tomorrow
Step 3: Write down everything the AI would need to know to do it WELL
(not just correctly — well)
Step 4: Notice the gap between what you wrote and what your
current design artifacts capture
That gap is the translation layer.
That gap is where UX 3.0 lives.
That gap is your new job.Answer that question rigorously, and you have done the most important design work for the AI era. Work that looks almost identical to the best design work of the previous era — applied to a context where it matters more than ever.
That is what UX 3.0 feels like from the inside. Not a revolution. A raising of the stakes on work that was always worth doing well.
P.S. — I resisted this framing for a long time. “The shock absorber is gone” felt too dramatic. Too neat. I kept thinking: interfaces will not disappear. Screens still matter. People still click things. All true. But then I watched a user test where an AI assistant rebooked someone’s hotel to save $40 — and moved them from a quiet boutique hotel near the conference venue to a highway-adjacent chain twenty minutes away. The user had not specified “location matters.” The system had no way to know. In the old world, the user would have seen both options on a screen and chosen the boutique in two seconds. The buffer would have caught it. In this test, the buffer was gone. The AI acted on what it knew. And what it knew was incomplete. That is when I stopped resisting the metaphor. The shock absorber is real. And we are the ones who have to rebuild it — not as an interface, but as an architecture of understanding.
Want to go deeper on the framework behind this? Jobs-to-be-Done is the most useful lens I have found for structuring intent in a way AI systems can actually use. I wrote a companion piece on exactly how to apply it: [#003: A 30-Year-Old Research Framework Is Now Writing AI Instructions. Most Teams Don’t Know It Exists. →]
#UXDesign #AIDesign #FutureOfDesign #ProductDesign #IntentFirst #DesignThinking #JTBD