Conversation Design Quick Reference Pick the right use cases

Optimize for a voice experience.

Not all experiences transfer well from a graphical UI to a voice interaction. Focus on actions that enable speed, simplicity, and convenience. Things people can answer off the top of their heads.

Ways to avoid pulling out a phone or finding a piece of paper.

Help for someone with hands full or eyes occupied.

Create a persona

Pick your voice

Choosing a persona makes it easier to use the right words, syntax, and structure when you design your interactions. Also, consider that users will perceive a persona whether you plan for one or not, so it’s worth taking time to frame the experience YOU want to get across instead of leaving it up to chance.

Think about how you want your conversations to feel and sound. Will you use a whimsical tone? Or a more deliberate, serious tone? Actions on Google has different voices to choose from to help you match your persona.

Write sample dialogs

Principles to design by

“What would you like to know?”

Once you’ve picked out your use cases and decided on a persona, you’re almost ready to build, but not quite! Start writing out some sample conversations with your users. Go beyond the “happy path" and explore different levels of familiarity, unexpected responses, and early exits.

Keep it short. Respect users' time. Get to the point and get out of the way. Give users credit. People know how to talk. Don’t put words in their mouth. Be relevant and sensitive to context.

“Ready...set...go!”

To keep it sounding natural and avoid written language style, say everything out loud as you go.

Delight the ear without distracting the mind. “That’s it! I was thinking of the number 19.”

Engage beginners and attract experts. Take turns. Just asked a question? Stop talking. Don't read minds. Give them the facts and let them decide. g.co/dev/ActionsPrinciples

Greetings and Goodbyes Tell users who you are The Google Assistant hands off the user experience to your action, so be sure to let users know they are entering your experience. Does your persona tell the user who they’re talking to? Is there a clear transition from the Google Assistant into the action, and do users know where they are now?

Give the right amount of information Your greeting should cater to users with varying degrees of familiarity with your actions: Will a brand-new user understand what your action is all about? Is the initial greeting informative without overwhelming them? Does your greeting sound repetitive for an experienced user? Is there a shorter, more familiar greeting for return users?

End conversations appropriately When users are done with the core intents fulfilled by your action, give them a chance to do something else or let them move on with their day.

Sound natural

Prevent errors by expecting variations

For every dialog you write, read it aloud and make sure it: Is something your desired persona would say

Provide helpful reprompts or pivot to another question

Be cooperative Does your VUI accommodate the innate rules of human conversation? To be effective, you should be as truthful, informative, relevant, and clear as the situation calls for. Read more at g.co/dev/ActionsDesign.

Take turns

Design Checklist

Reframe questions for users when they say things your action doesn’t understand or when they don’t say anything at all (two very different contexts!).

Be prepared to help at any time Users might ask for help at any point in the conversation (“What can I do?”), so be prepared and either reprompt them or offer an explicit help dialog. TIP: Prevent confusion with intuitive commands.

A good conversation partner knows how to give the right cues.

Let users replay information Recognize and appropriately respond to user input like “what?”, “repeat”, “say that again”, and other similar phrases.

DO give users enough context to respond each time you yield a turn. DON’T just make an ambiguous statement and then open the mic.

Fail gracefully

DO give users a question or prompt that turns over the conversation to them.

If users don’t provide a response or one that you can’t recognize after two or three tries, exit with an appropriate message.

DON’T keep speaking after asking a question.

Persona Reflect your unique brand and identity If you don’t already have a persona defined for your brand, create one! Find out how in our Design Tips video youtu.be/MSUPVbbhIGA.

g.co/dev/ActionsChecklist

Your actions should understand input that’s phrased in many alternate ways, such as “yes”, but also: “yeah”, “sure”, “it does”, “it sure does”, “of course”, or “definitely”.

Has been written with voice in mind rather than just a copy of some other medium (such as a converted mobile app or website).

Is there an unobstructed path to the exit? Are simple back out requests like “nevermind” and “no, thanks” honored in the contexts where they make sense for the user?

Conversation Repair

Conversational Dialogs

Stay consistent Maintain the persona throughout the entire conversation, so users don’t experience jarring or confusing dialogs that feel like they’re talking to multiple personalities.

Keep users coming back Think of your persona as a real person and someone that you and your users would want to interact with - even (or perhaps especially) after many encounters.

Is your action ready for users? g.co/dev/ActionsDistribute

© 2017 Google Inc. All rights reserved. Google and the Google logo are trademarks of Google Inc.

Conversation Design Quick Reference Developers

Conversation Design Quick Reference. Pick the right use ... when you design your interactions. Also, consider ... converted mobile app or website). Reflect your ...

8MB Sizes 18 Downloads 295 Views

Recommend Documents

Go Quick Reference Go Quick Reference Go Quick Reference - GitHub
Structure - Package package mylib func CallMeFromOutside. Format verbs. Simpler than Cās. MOAR TABLE package anothermain import (. "fmt". ) func main() {.

LIKWID | quick reference - GitHub
likwid-memsweeper Sweep memory of NUMA domains and evict cache lines from the last level cache likwid-setFrequencies Control the CPU frequency and ...

Log4j Quick Reference Card - GitHub
log4j.appender.socket.port=10005 log4j.appender.socket.locationInfo=true log4j.logger.com.my.app=DEBUG. Level. Description. ALL. Output of all messages.

Quick Reference Guide* * * * * * * * * * * * * * * * * * * * * Nutrition and ...
Fruit seeds and cores. ○ Chocolate. ○ Onions. ○. ○ Tomatoes(plants are toxic )ripe tomatoes small amounts fine. ○ Heavy wheat and flour based foods.

Quick Reference Guide.pdf
o Contact the ThunderRidge HS Portal Manager at [email protected]. Student Portal Account and Student Moodle Account. Username = Last Name ...

CustomGuide Quick Reference
To Delete a Message: Select the message and ... http://login.customguide.com/HancockCountySchools ... from the contextual menu, and select Clear Flag.

Quick Reference Guide.pdf
example, multiple Ziploc bags with socks in each), you only need to enter once and choose the correct. quantity. The system will create multiple line items/tags ...

In Conversation, There Are No Errors Developers
your users' experience and your app's success. Errors as opportunities. There's no such thing as a query without intent. Users always want to do something, ...

Garmin 430W Quick Reference Guide.pdf
WARNING: Do not use data link weather information for. maneuvering in, near, or around areas of hazardous weather. Information contained within data link ...

Javascript Quick Reference Card - Cheat-Sheets.org
Code Structure var ... //Global variable ... //your code here. }] aName='ExplainThat!'; ..... pathname – the path to the document on the host protocol – the protocol ...

RollCall Attendance Quick Reference Guide.pdf
participation of students. How to Get Started - Login to Canvas through the Mesa Community College home page, mesacc.edu. Additional Resources – Visit the ...

2017 Quick Reference letter size.pdf
There was a problem previewing this document. Retrying... Download. Connect more apps... Try one of the apps below to open or edit this item. 2017 Quick Reference letter size.pdf. 2017 Quick Reference letter size.pdf. Open. Extract. Open with. Sign I

Quick Reference Sheet v2.1.pdf
Overload Bonus 100% Armor HP 100%. Bomb/Smrt Bomb Dmg100% Signature Rad. -50%. Smart Bomb Rng 100% Small Wp. Dmg 200%. EWAR Types.

Subaward Invoicing Quick Reference Guide_Jan2015.pdf ...
Page 1 of 2. NYU Program Services Oce. FAQs. What is flextecs? The subaward invoicing system. uses a software called flextecs to. manage the payments of.

Know Your Customer: Quick Reference Guide - PwC
Jan 1, 2014 - regarded as bank customer according to the Article 76 of Banking Law. ...... of preventative medicine, medical diagnosis, medical research, the ...

SENIOR QUICK REFERENCE GUIDE.pdf
There was a problem previewing this document. Retrying... Download. Connect more apps... Try one of the apps below to open or edit this item. SENIOR QUICK ...

Chronical Quick Reference Guide.pdf
tube, use food grade silicone grease, Star San, or water as a lubricant. In the event you need to replace the O-ring inside the 1⁄2” threaded adapter,. spares are available on our site at www.ssbrewtech.com . We recommend that you orient the rack