The short version
  • Design around user jobs and decision points, not model features.
  • Make actions, assumptions, and sources visible at the right moment.
  • Treat clarification and recovery as primary flows.

01

Define the conversation contract

State what the assistant can do, what information it uses, and when it will ask for confirmation. A clear contract reduces both user confusion and unsafe automation.

02

Structure context progressively

Ask only for information needed at the current decision point. Summarize retained context and provide controls to correct assumptions before consequential actions.

03

Design for failure and recovery

Use specific error states, preserve user work, offer a next best action, and make escalation easy. Test ambiguous language and incomplete inputs, not only ideal examples.

Common questions

Questions worth asking

Is conversational AI design the same as prompt writing?

No. Prompt writing is one implementation detail. Conversation design also covers user goals, interaction flow, state, interface controls, recovery, and trust.