INQUIRING LINE

Should you tell an AI what you want, or still click and drag things yourself — and when does each actually work better?

How does intent-based interaction differ from traditional direct-manipulation design?

This explores how designing AI around people stating what they want (intent) differs from the older approach of having people directly click, drag, and edit things on screen, and whether one is replacing the other.


This explores how intent-based interaction, where you tell the system what outcome you want and it works out the steps, differs from direct manipulation, where you act on visible objects yourself and see the result right away. The short version from the corpus is that they are not rivals. Mature AI interfaces seem to need both, and the hard design problems sit where one hands off to the other. Nielsen's model puts it most clearly. He describes three layers: an Intent surface for saying what you want, an Orchestration surface for watching the AI's work as it happens, and a Direct-Manipulation surface for precise corrections. Each layer covers a failure the others can't handle. Intent gets around the problem of not knowing which steps or commands to use. Direct manipulation comes back when you need exact control over a detail that's hard to put into words How should AI interfaces handle the shift from doing to supervising?.

The less obvious point is that intent-based design can be a step backward if it's done badly. Medeiros argues that defaulting to chat brings back the layer of words and symbols that direct manipulation was invented to remove. Before graphical interfaces, you typed commands. GUIs let you point at the thing itself. A chat box asks you to describe the thing again, and for structured, goal-directed work that adds mental effort. Medeiros suggests two test questions: does conversation make this task faster, and does the value come from talking or from the output? Is chat the wrong default interface for AI products?. Friedman makes a similar case. Typing out what you want is slow, so good AI products add tools like visual intent maps, style 'lenses', and editable canvases. These capture intent without making you spell everything out Can task-oriented UI patterns reduce the friction of AI chat interfaces?. Generative interfaces push the same idea further. When an LLM builds a task-specific dashboard or tool on the spot, instead of answering in text, users prefer it in over 70% of cases Do generated interfaces outperform text-based chat for most tasks?. In other words, intent can be the input while direct manipulation stays the way you work with the result.

A deeper difference is that intent usually isn't ready to state at the start. The 'gulf of envisioning' research finds that people often can't say what they want until they've seen some options. Models tend to answer exactly what was asked instead of helping people work it out. Showing generated options turns an open-ended 'imagine it' task into an easier 'pick and adjust' task, which is a direct-manipulation idea applied to intent itself Why can't users articulate what they want from AI?. Some systems skip asking altogether. Poppins watches your screen and infers short-term goals, and its outputs beat standard LLMs 66–86% of the time Can systems infer what users want from watching their screen?. Other work reads intent from behavior such as hesitation, gaze, and typing speed. That same data can be used to time help well or to profile people manipulatively Can AI systems read cognitive state from interaction patterns alone?.

The shift also changes what 'good usability' means. In direct manipulation, the interface is stable. Buttons stay where they are, so you can learn them. In AI interaction, the context the system is working from (prompt, history, retrieved data) keeps changing and is mostly hidden. You can't build the same mental model of it How does AI context differ from conventional software context?. That's why Nielsen moves the main measure from preventing errors to calibrating trust: knowing when to rely on the AI and when to step in. On the engineering side, the same move is visible in dialogue systems. Rasa replaced fixed intent categories with generated commands that handle context more naturally Can command generation replace intent classification in dialogue systems?.

One twist you might not expect: the interface now has two audiences. AI agents also do direct manipulation when they click and type through screens for you. Interfaces designed with agent-specific cues help agents finish tasks without making things worse for human users Can interface design help agents complete computer tasks better?. So the future may not be intent replacing direct manipulation. You state the intent, and an agent does the direct manipulation on your behalf.


Sources 10 notes

How should AI interfaces handle the shift from doing to supervising?

Nielsen proposes Intent, Orchestration, and Direct-Manipulation surfaces that each address specific problems: articulation barriers, loss of implicit knowledge, and precise correction needs. This reframes usability metrics around trust calibration rather than error prevention.

Is chat the wrong default interface for AI products?

Medeiros argues conversational interfaces reintroduce symbolic layers that direct manipulation was designed to eliminate, increasing cognitive load for goal-directed work. Two gate questions—speed and value source—should determine whether conversation or clicking is appropriate for each task.

Can task-oriented UI patterns reduce the friction of AI chat interfaces?

Friedman identifies five design levers—intent capture, output shaping, refinement, agentic tasks, and workflow embedding—that sidestep slow typed prompts. Examples include node-based intent visualization, style lenses for output, and canvas manipulation, shifting AI interfaces away from conversational chat toward direct interaction.

Do generated interfaces outperform text-based chat for most tasks?

Research shows users strongly prefer LLM-generated interactive interfaces—dashboards, tools, animations—over text blocks, especially for structured and information-dense tasks. Structured representation and iterative refinement reduce cognitive load.

Why can't users articulate what they want from AI?

Intent develops through interaction, not in isolation. Since AI models respond rather than probe, they miss opportunities to help users discover unarticulated requirements. Structured dialogue that presents model-generated options shifts the cognitive burden from open-ended envisioning to constrained evaluation.

Show all 10 sources
Can systems infer what users want from watching their screen?

Systems that passively observe user activity to infer just-in-time objectives produce outputs preferred 66–86% of the time over standard LLMs. This approach sidesteps fixed training objectives by inferring narrow, momentary goals from behavior instead.

Can AI systems read cognitive state from interaction patterns alone?

Research shows AI systems can instrument multimodal behavioral signals (gaze, hesitation, speed) to read cognitive state during interaction, preserving flow by avoiding disruptive explicit probes. However, the same substrate enables both helpful timing and manipulative profiling.

How does AI context differ from conventional software context?

AI interactions operate on a substrate of constantly shifting context—prompt, history, retrieved data, hidden state—that users cannot internalize like traditional UIs. This structural mutability demands a new design discipline centered on context engineering rather than interface design.

Can command generation replace intent classification in dialogue systems?

Rasa's dialogue understanding architecture generates domain-specific commands instead of classifying intents, eliminating annotation requirements, handling context naturally, and scaling without degradation—treating understanding as pragmatics rather than semantics.

Can interface design help agents complete computer tasks better?

UI-Verse benchmark testing found that augmented heuristics targeting agent perception, grounding, and control consistently improved agent task completion and efficiency. Human studies confirmed these designs preserved usability for human users with no observable regressions.

Papers this line draws on 8

The research behind the notes this line reads — ranked by how closely each paper relates.