Creating a Persona: Intro Conversational Design [Assistant Content Bundle]

https://www.meetup.com/it-IT/GDG-Milano/events/248566884/

Questo evento fa parte di una serie di eventi globali: "Build Actions for Your Community".

Sabato, 23 giugno 2018 dalle 9:30 alle 13:00 si terrà il primo evento del GDG Milano dedicato INTERAMENTE su Google Assistant.

L'evento è aperto a chiunque. Non preoccupatevi se pensate di non avere le giuste competenze, vi introdurremo in questo nuovo mondo.
É preferibile una minima esperienza nello sviluppo software.

Agenda per la giornata
09:30 - Colazione
09:50 - Talk: Creating a Persona
10:10 - Talk: Build Assistant Apps
10:30 - Codelab: Costruisci il tuo assistente
12:30 - Presentazione delle vostre app! 🎉

Come sempre l'evento è gratuito, la registrazione è obbligatoria.

• Presentazione delle vostre app! 🎉
Visto il grande entusiasmo per lo scorso evento "Building a new horizon with Google Assistant as a shopper (by Women Techmakers)" abbiamo pensato di premiare i vostri sforzi.
Durante l'evento "Build Actions for Your Community" vorremmo dare ad ognuno di voi qualche minuto per presentare il proprio lavoro.

• Obiettivi 🎯
Esplora: Hai un progetto in mente? Potrebbe aiutare qualcuno? Questo è il momento di provare a realizzarlo!
Condividi: Approfitta del fatto che parteciperanno al evento altre persone interessate agli assistenti virtuali. Sono i principali utilizzatori del tuo prodotto e il loro feedback può essere d'aiuto.
Ispira: Ogni problema può avere più soluzioni, e mostrare le propria idea agli altri può avviare nuove discussioni, far sorgere nuove idee ed eventualmente nuove collaborazioni!
Premi 🎁
Nonostante non sia l'obiettivo principale, abbiamo deciso di premiare i migliori progetti!
Sono previsti premi per i migliori 10 progetti, con premi speciali per i migliori 3!
La votazione sarà fatta direttamente dal pubblico durante l'evento.

• Consigli su come prepararsi 😉
Sono ben accetti tutti i vostri progetti!

Tema suggerito: Build Actions For Your Community (volutamente generico)
Tempo a disposizione per la dimostrazione: 3-5 minuti, in base al numero di partecipanti.
Presentazione: La dimostrazione deve essere pratica (NO SLIDE) e fatta tramite simulatore o un dispositivo con Google Assistant.

Visto il poco tempo a disposizione vi suggeriamo questo schema per la presentazione:
circa 10 secondi - presentazione personale: chi sono
circa 30 secondi - brevissima descrizione del progetto (es: origine dell'idea).
tempo restante - dimostrazione con Google Assistant (messaggio di benvenuto, dimostrazione delle azioni principali)
Seguici sui social per ricevere altri consigli e suggerimenti!

Una volta registrati i vostri progetti possono essere modificati fino al giorno della presentazione.

Il regolamento completo e aggiornato verrà pubblicato nei prossimi giorni sulla pagina dedicata al evento e sul sito.
http://www.gdgmilano.it/build-actions-for-your-community

NOTA: I progetti devono rispettare il nostro codice di condotta http://it.confcodeofconduct.com (In breve: Sii eccellente con gli altri)

Sei pronto/a per la presentazione? Registrati qui: https://goo.gl/forms/kOpNY3PB8LbTnYV53

• Cosa bisogna portare
Per poter provare le potenzialità di Google Assistant vi consigliamo di portare con voi il vostro portatile.

• Cose importanti da sapere
L'evento è aperto a chiunque. Non preoccupatevi se pensate di non avere le giuste competenze, vi introdurremo in questo nuovo mondo.
É preferibile una minima esperienza nello sviluppo software.

Per qualsiasi dubbio contattateci su gdgmilano@googlegroups.com o su Telegram https://t.me/gdgmilanochat

Transcript

1. Conversational Design Intro Omar Miatello | Satispay | @gdgmilano | omar.miatello@gmail.com
3. GUI : VUI What’s the difference?
4. Top 3 Design Tips
5. [1] Create a Persona
6. A Persona is conveyed through: • Tone • Word and phrase choices • Functional design • Style • Technique • Voice And it is based on: • Your user population • Their needs • The imagery & qualities associated with your brand
8. Cowabunga, dude! What flavors do you crave? The bus is approaching your stop now. Your trip will take 45 minutes.
9. [2] Think outside the box. Literally!
10. code code code code code code code code code code code “ dialog string” code code code code code code code code code code “dialog string” code code code code code code code code code code code code code code code code code code code code code code code “dialog string” code code code code code code code code code code code code code code code code code code code code code code code code code STRUCTURE CODE
11. code code code code code code code code code code code “ dialog string” code code code code code code code code code code “dialog string” code code code code code code code code code code code code code code code code code code code code code code code “dialog string” code code code code code code code code code code code code code code code code code code code code code code code code code STRUCTURE CODE
12. DIALOG STRUCTURE
13. [3] In a conversation, there are no “errors”
14. real life user conditions {
15. “I don’t understand you.”
16. When a so-called “error” occurs in a conversation, it should be treated simply as a new turn in the dialog, only with different conditions.
17. Users have intent
18. Conversation repair for timeouts USER Ok Google, let me talk to Number Genie. GOOGLE ASSISTANT Sure, Here's Number Genie. NUMBER GENIE Welcome to Number Genie! I'm thinking of a number from 0 to 100. What's your first guess? USER (says nothing) NUMBER GENIE I didn't hear a number. USER (silent or muffled) NUMBER GENIE If you're still there, what's your guess? Sample Dialogs What to include: 1. Canonical “Happy path” 2. First time experience 3. Tapered experience (Return user) 4. Repair
19. Quit game. User gives up and ends the game USER Hey Google, let me talk to Number Genie. GOOGLE ASSISTANT Sure, Here's Number Genie. NUMBER GENIE Welcome to Number Genie! I'm thinking of a number from 0 to 100. What's your first guess? USER 21- NUMBER GENIE It’s higher than 21. What’s your next guess? USER I give up. [LOGIC: catch ending intent] NUMBER GENIE Sure, I’ll tell you the number anyway. It was 90. What to include: 1. Canonical “Happy path” 2. First time experience 3. Tapered experience (Return user) 4. Repair Sample Dialogs
20. Give users credit They know how to talk Avoid force feeding commands. (such as “to reply to a message, say ‘reply’” or “to hear that again, say ‘repeat’”.) People hardly ever say nonsense. They just weren’t parsed correctly. There was a misalignment in meaning. They know what they want There’s no such thing as a query with no intent. The user wanted to do something, even if they didn’t say so. They want to help Don’t create dead ends when something doesn’t work. If you ask for them to say something again, they will, but rarely exactly the same way. Honor that they’re invested in outcome of a repair attempt.
21. Use the context Environmental Where is the user? What are they doing? What type of device are they using? Situational What’s their intent? Where is the user’s frame of mind? Temporal What happened right before? What’s happening next? How is the experience influenced over time? Behavioral What do users know going in? What data can you use to enrich the experience predictively or to cut out unnecessary steps?
22. Rapid reprompt “What was that?” “Say that again?” Reframe the question “What time is this for?” → “Sorry, what time?” “For when?” → “What time would you like to book this for?” Ask another way “If it helps, we can do this one piece a time.” Be ready for questions about the question “I have your name and email from your account, so now all I need is your phone number.” “You can give me the day, the time, or both.” Be proactive “I could put you down for 6 for now, does that work?” “Do you want to finish this later?” Example strategies to have ready
23. With a VUI, the user can feel like a “prisoner” of the VUI design. They must listen with (or without) patience to each word before they can hear the one that follows it. source: pexels.com A VUI is inextricably linked with time
24. VUI Best Practices
25. VUI Best Practices Avoid written language and use spoken one Kick off the conversation: introduce your own brand, provide a list of high level actions available by Action. Kick off the conversation: if given the context. Example: Talk to <agent_name> about <subject_one> to avoid menu listening.
26. VUI Best Practices Guide user through the conversation: If you expect users to ask make sure to ask a clear question. Don’t leave mic open without a prompt Keep our TTS (Text to speech) short and clear: Analyse if your TTS can be split up in a logical way. Ask first before giving long TTS descriptions.
27. VUI Best Practices Avoid data points unrelated to user query Follow natural turn taking in the conversation Use conversational makers: Adding the “glue” to the conversation and making it more engaging: • Timelines - “first”, “halfway there”, “finally” • Acknowledgements - “thanks”, “got it”, “alright”, “sorry, about that” • Positive feedback -”good job”, “nice to hear”
28. Keep dialog simple
29. Action: Welcome to Sounds of Relaxation. Are you trying to sleep, meditate, cool down, think, or reflect? User: Reflect. Action: Great. We have something for that. Would you like to also include ocean waves, crackling fire, wind blowing, or birds chirping with that? User: Sure, birds. Action: Do you want this for 5 minutes, 30 minutes, or an hour? User: 30 minutes. Action: Find a nice place to sit or lie down … are you ready? User: Yes. Action: Ok, Here’s your 30-minute relaxation sounds with birds chirping. Too Long
30. VUI Best Practices How to recover a conversation? Step 1 Error cannot be eliminated Step 2 Use broader explanation when re-prompting Step 3 Don’t blame the user Step 4 Don’t repeat prompts in error cases
31. Enhance your Action
32. Speech Synthesis Markup Language (SSML) developers.google.com/actions/reference/ssml
33. Sound Library developers.google.com/actions/tools/sound-library/
34. Thank you
35. Console bit.ly/buildactions-console Build with Templates developers.google.com/actions/templates Build with Dialogflow developers.google.com/actions/dialogflow Build with Actions SDK developers.google.com/actions/sdk Resources to get started and supported Documentation developers.google.com/actions Codelabs codelabs.developers.google.com Write and Deploy Functions bit.ly/firebase-get-started Deploy your fulfillment webhook using Cloud Functions for Firebase bit.ly/aog-cloud-functions
36. Actions on Google Community Program developers.google.com/actions/community You are automatically invited to the program with publishing your first Action and will receive a Cool T Shirt + $200 Cloud Credits per month for a year The Assistant team also recognizes milestones: Traction Engagements Globalization
37. Additional Resources G+ Developer community: g.co/actionsdev Videos: bit.ly/aog-tips Dialogflow: dialogflow.com/google-assistant Twitter: @ActionsOnGoogle #AoGDevs Our mailing list: assistant.google.com/developer