Give conversational interfaces a way back
2 min read
Conversation is one part of an interface. Editing, reviewing, and recovering deserve just as much attention.
This field note works through the decisions between an idea and a usable product. It starts with a concrete task and follows the choices that shape the experience, the delivery, and the next iteration.
Keep the conversation connected to the work
Show the document, task, or record the assistant is working with. Give users a way to inspect what context is included.
Allow structured controls where precision matters. A date picker or selection list can be easier to use than another conversational turn.
Let people revise an earlier choice
Offer direct editing of important inputs and make the effect of a revision clear. Preserve earlier output when it helps comparison.
Keep cancellation and retry understandable. The person should know which operation is still running and which result is current.
Write recovery messages as instructions
Describe what prevented progress and give a next step the user can take. Avoid vague failure messages that simply invite the same attempt again.
Test recovery with someone unfamiliar with the system. If the message needs an explanation from the team, rewrite it.
