Description
Two people read written sample dialogs aloud, one voicing the system and one the user, to hear where a conversational design sounds stilted, repetitive or confusing.
Sample dialogs are film-script-style exchanges between a voice or chat interface and its user, written for the five or so most common use cases on the best path plus key error cases. In a table read, one person reads the system's lines and another the user's, aloud. Speech exposes what reads fine on paper: overly formal wording, identical acknowledgements repeated ('got it' three times in a row), missing conversational markers such as timelines and confirmations, and turns after which users would not know how long the conversation will last. Reading with developers also surfaces behaviours that need complex engineering, such as pronoun resolution or references to past use, securing early buy-in. A higher-fidelity variant records the dialogs with the planned voice talent or text-to-speech engine to hear them before development.
Attributes
- Discipline
- Design & Product Practice
- Loss type
- Active
- Stage
- Design
- Data
- Qualitative
- Effort
- Hours
Steps
- Write sample dialogs for the five most common use cases on the best path and for several error and no-match paths.
- Read each dialog aloud yourself as you write it.
- Hold a table read: one person reads the system, another the user, without rehearsal.
- Note stilted, repetitive or unclear turns and missing markers (timelines, acknowledgements, confirmations).
- Repeat the read with developers to flag behaviour that is technically complex.
- Optionally record the dialogs with the chosen voice or TTS engine and listen again before building.
Sources
- Designing Voice User Interfaces (Pearl, 2017)
- Chatbot Research and Design: CONVERSATIONS 2022 (Følstad et al., 2023)
- Conversational Design (Hall, 2018)
Also known as
- Table read of sample dialogs
- Sample dialog read-through
- Script read-through
Categories
- Design
- Design & Product Practice