Prototyping Voice Experiences: Design Sprints for the Assistant
summary
A practical method for prototyping Assistant experiences centers on an 8-phase Voice Action Sprint that combines design-sprint tools (crazy 8s, experience maps) with improv role-play to produce brand persona-driven sample dialogs. Teams record either Wizard of Oz vs Dialogflow prototypes, run about 5 user tests of ~45 minutes, and iterate on conversational repair, task scope, and success metrics. Case work with Filtrete and H&M yields key use cases, validated voice prototypes, and concrete learnings about appropriate information level and user engagement.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:01Design Sprints
- 3:21When to use a Sprint
- 7:44Principles of Conversation
- 9:08Openended vs Guided Conversations
- 10:06The Raw Chicken Moment
- 11:34Examples
- 13:34Research
- 15:51Brand Persona
- 18:53User Value Matrix
- 21:59Sample Dialogue
- 25:39Prototyping
related talks
24mVoice design best practices
50mDesigning Experiences For Voice Interactions
24mFail fast, fail cheap, making voice apps the guerrilla way
44mFaster from Problem to Prototype with Design Sprints: Are MvPs Dead?
37mHow to Test Cultural Code, or UX Testing a Children's Voice Assistant
01mUX/UI
22mDesigning Voice For Humans
25mHow to run a design sprint without a panic attack