Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Building Voice UI products for events

Creating Voice UIs for events has its own special challenges. I created the concepts for the Amazon Alexa skills for the conferences Tech Open Air and re:publica and here is how we approached the task, decided on the feature set and what challenges we faced.

  • Login to see the comments

  • Be the first to like this

Building Voice UI products for events

  1. 1. Designing Voice UIs for events Nelli Hergenröther
  2. 2. Agenda 1. Introduction 2. Pros & cons of Voice UIs 3. Building Voice UIs for events 4. Discussion
  3. 3. 1. Introduction
  4. 4. Who am I? • Nelli Hergenröther, managing director of software consultancy Evenly • Background in product and project management • • @no_vem_ber
  5. 5. What’s this all about? • We built an Amazon Alexa skill for the conferences re:publica and the Tech Open Air • I created the concept and decided on the feature scope for the first version together with developers • Voice UIs for live events have their own specific challenges
  6. 6. 2. Pros & cons of Voice UIs
  7. 7. Pros of Voice UIs • Speed • Freedom for multitasking • Intuitiveness • Empathy
  8. 8. Cons of Voice UIs • Inconvenience through noise • Privacy concerns • Communication habits • Complex data entry • A computer is not a human
  9. 9. 3. Building Voice UIs for events
  10. 10. Amazon Alexa conference skill A conference skill is a great use case for a Voice UI: • Stationary device • No privacy sensitive information • Short infos (locations, dates etc.) needed • Play audio while doing something else
  11. 11. User stories
  12. 12. The 3 states Before conference • Infos about conference and session dates, location • No recordings yet During conference • Dates and times of sessions • Live sessions After conference • Infos about location or session dates are not relevant anymore • Recordings are available
  13. 13. Listen to a recorded session
  14. 14. Mapping dialogs
  15. 15. Confirmation strategies User needs to know that • Task was successful • Correct task will be done To consider • Cost of getting it wrong • Available modalities for feedback Confirmation method
  16. 16. Explicit and implicit confirmation • Explicit confirmation Forces the user to confirm the information. For example, “I think you want to play the live stream of session X. Is that correct?” • Implicit confirmation
 Lets the user know what was understood, but do not ask them to confirm. For example, “Playing live stream of session X". (In this case user should have possibility to cancel or go back a step)
  17. 17. Error handling Intent not understood • „I couldn’t understand you“ • User can try again (implied) Information not found • „I couldn’t find session X“ • Info is missing or intent was not understood correctly • User can try again (implied) Wrong information found • Plays session bei Anna instead on Hannah • Implicit confirmation - user notices and can cancel
  18. 18. Selecting the feature scope • We focused on a very limited feature set for MVP • More features (user requested) to be added later • Feature scope limited by available data • Possible new features: • Add favorites • Recommendations • Notifications (closed beta)
  19. 19. Summing up VUIs for events • Event skill is great use case for VUI: stationary device, public information, short infos, used as background audio • Keep in mind the 3 states: before, during and after conference • Make skill relevant for users in all 3 states • Work with user stories and move on to mapping dialogs • Use implicit confirmation (cost of failing is not very high) • In case of error: prompt user to try again
  20. 20. Try them out!
  21. 21. 4. Discussion
  22. 22. Let’s discuss! • Do you have experiences with designing/building Voice UIs? • What were the challenges? • What solutions did you choose? • What would be other great use cases for Voice UIs? • What could be interesting features?
  23. 23. Thank you for listening!