The End of Buttons: Designing for Intent Instead of Clicks in UX
1. From UX that designs clicks to UX that understands goals
What users want is not the process of manipulating the screen, but the result of finishing the task.
- The flow of entering date, price, and layover conditions separately to find a flight changes into a single request.
- When you say, “Find me a nonstop flight to Chicago for under $300,” AI performs the search and comparison.
- The designer’s role also expands.
- In addition to button placement, they must design how the system interprets intent and what results it shows.
2. Three kinds of effort reduced by intent-centered experiences
The intermediate steps users used to handle directly in search, creation, and planning are reduced.
- Perplexity AI: Reduces the effort of reading and organizing information across multiple tabs.
- It gathers answers, comparison tables, and sources that match the question.
- Vercel v0: Shortens the creation process of placing UI elements one by one.
- If you describe the screen you want, it generates the UI and code.
- Goblin.tools: Breaks vague goals into actionable steps.
- It turns the burden of deciding where to start into a small checklist.
3. Reading context, creating the needed screens, and executing
Intent-centered UX is a broader design than simply adding a chat input field.
- Understanding goals and context: Uses time, location, and prior behavior along with the user’s request.
- Generative UI: Provides interfaces such as comparison tables or calculators needed for the current task.
- Autonomous execution and recovery: The system performs the task, but provides paths for modification and undo.
4. Even if manipulation is reduced, control must remain
As automation increases, users must be able to understand and intervene in the system’s judgments.
- Important decisions require confirmation points.
- High-impact tasks such as finance and personal information leave room for the user to make a judgment before execution.
- Show the basis for judgment along with the result.
- Users should be able to confirm which conditions were reflected and what was executed.
- Allow corrections to incorrect interpretations.
- Paths to request revisions, undo execution, or return to manual operation support a sense of control.
