Chat Off-Ramp
When the best AI interface is no conversation at all
Chat gets bolted onto tasks that have a known shape — and suddenly cropping an image takes three turns of typing. When the task's parameters are enumerable, the strongest move is the one this library keeps circling: skip the conversation entirely. Ship the task-native control — a toolbar, a slider, a button — with the model behind it, and keep a free-form escape hatch for the long tail. NNGroup's most radical finding, distilled: sometimes the fix is not a better surface next to chat, but no chat at all.
Framing
The problem
Chat gets bolted onto tasks with a known shape, adding turn-taking, typing, and interpretation variance to something a control could do in one gesture.
The pattern
When the task's parameters are enumerable, skip the conversation: ship the task-native control with the model behind it, and keep a free-form escape hatch for the long tail.
Why chat breaks here
This is the meta-case — the conversation itself is the overhead; there is nothing for the dialogue to disambiguate.
Risks
Fixed controls cap the ceiling — without an escape hatch to free-form input, the unenumerated 20% of intents has nowhere to go.
Avoid when
Open-ended, exploratory, or genuinely conversational tasks — when intent cannot be enumerated, chat earns its place.
Use when
The task's parameters are enumerable and repeated — a conversation adds turns where a control would do.
DOPE evaluation
- Directability
- One gesture does what three chat turns approximated, and the free-form hatch stays open for the unenumerated case
- Observability
- The available actions are the interface — every capability is a visible control, none hides behind phrasing
- Predictability
- A labeled control does one named thing — no turn-taking, no interpretation variance between runs
- Explainability
- The control's label is the explanation — what it does is what it says, before it runs
In the wild
- Adobe Photoshop · Generative Fill toolbar (Adobe) — Generative AI behind a selection tool and a button — the model does the work, the interface stays a toolbar. The optional prompt field is the escape hatch, not the primary surface.
- Google Photos · Magic Editor (Google) — Tap, drag, erase — generative editing with zero conversation. Suggested edits appear as buttons; parameters the task actually has (position, size, presence) map to gestures.
- Canva · Magic Studio tools (Canva) — A suite of single-purpose AI tools (Magic Eraser, Magic Expand, Magic Grab) shipped as named buttons in the editor — each does one enumerable thing, no dialogue required.
FAQ
When should I use the Chat Off-Ramp pattern?
The task's parameters are enumerable and repeated — a conversation adds turns where a control would do.
When should I avoid the Chat Off-Ramp pattern?
Open-ended, exploratory, or genuinely conversational tasks — when intent cannot be enumerated, chat earns its place.
What problem does Chat Off-Ramp solve?
Chat gets bolted onto tasks with a known shape, adding turn-taking, typing, and interpretation variance to something a control could do in one gesture.
Why is chat the wrong fit for this?
This is the meta-case — the conversation itself is the overhead; there is nothing for the dialogue to disambiguate.
Related patterns
- Often paired with: Property Panel — The cockpit is where the off-ramp leads for parameterizable tasks.
- Often paired with: Select & Transform — Act on the selection directly — no conversation about what you meant.
- Alternative to: Disambiguation Branch — Ask a clarifying question vs remove the need to ask one.