Conversational Design: Scripting a Dialogue, Not Just a UI
Think of conversational design as scripting a dialogue where the user is the main character. It's how voice assistants and chatbots create natural, two-way interactions.
Why it exists
Users don't think in terms of API calls or button clicks; they think in terms of goals. When interacting with voice or text interfaces, they expect a conversation. Conversational design exists to bridge the gap between a user's natural language and a system's rigid logic, making technology more accessible and less frustrating.
The mental model
Treat the interaction as a cooperative dialogue between two intelligent parties, not a master-servant command structure. The system should have a distinct persona—a personality—that guides its responses, tone, and vocabulary. This persona helps create a consistent and predictable experience for the user, just like talking to a specific person.
How it works
The process begins by defining the system's persona and understanding user goals. Designers then write sample dialogs, scripting out potential conversations for various scenarios, including the "happy path" and common error cases. These scripts cover acknowledgements ("Got it"), confirmations ("Did you mean..."), error handling ("I didn't understand that"), and suggestions to guide the user. This iterative process of writing, testing, and refining dialogs is the core of the practice.
When to use it
Use conversational design for any product with a voice or text-based interface. This includes voice assistants, customer support chatbots, in-car navigation systems, and interactive voice response (IVR) systems. It's critical when the user's hands or eyes are busy, making voice the only viable input, or for complex tasks that can be broken down into a series of questions and answers.
When not to use it
Don't force a conversational interface where a graphical one is superior. Tasks that are highly visual, require browsing large amounts of data, or involve complex form-filling are often better served by traditional GUIs. Forcing a conversation for something easily done with a click creates friction. The key question is: does a conversation make this task easier or just more complicated?
One canonical example
Imagine a food delivery app. A GUI approach is tapping through menus. A conversational approach is: User: "Order a large pepperoni pizza from Pizza Palace." System: "Okay, a large pepperoni from Pizza Palace. Your last order from there also had garlic knots. Want to add those?" This anticipates needs and feels like a helpful assistant, not just a vending machine.
Interview question
Which task would likely create the most friction if implemented solely through a conversational interface?
- a.Ordering a specific item from a known vendor with a simple command.
- b.Troubleshooting a common technical issue by following a guided diagnostic process.
- c.Navigating a complex financial dashboard to analyze trends and generate reports.Correct
- d.Receiving turn-by-turn directions while operating a vehicle.
Why? this is the answer
The card states that tasks which are 'highly visual' or 'require browsing large amounts of data' are better served by traditional GUIs, making a complex financial dashboard a poor fit for a conversational interface. Other options represent scenarios where conversational design excels, such as when hands/eyes are busy or for breaking down complex tasks.
Just read this? Test yourself on what you have been reading.
Read the original → developers.google.com
- #conversational design
- #ux
- #product design
- #voice ui
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles