Hey Google; Whats Next? / Conversational UX

Since the beginning, a UX designers’ job is assisting the user to perform the needed task in the possible shortest time by minimalizing the information and the interface they interacted. Nowadays, things are a bit different than the past. Now, users don't even have to look for the content to get the answer. The only thing they need to do is talking with a chatbot or a virtual personal assistant which response in seconds!

So, for a UX designer, things are tougher than ever. If you look the evolution of the virtual personal assistants and chatbots, you'll see no interface problems about reaching the content. Let's dive into the magical world of VPAs and chatbots to see how the voice interactions and the conversational UX make our daily life easier than ever.

This presentation aims to teach beginners how to create a flow for a Conversational App (Personal Assistants or Chatbots)

Conversational Design Sprint

The Conversation Design Sprint is a short 4-hour collaborative workshop, in which teams will participate in activities to "learn by doing" the design process and principles for conversational experiences.

This is especially useful for product teams who are creating a brand persona from their existing brand identity and writing dialog for Actions on Google. Here you will find all of the resources you need to run your own Conversation Design sprints with your product teams and clients.

List of items:
Regarding the size of the space, we need enough space for 30 people to spread out and be able to work in teams of 4.

Projector
Chairs for all
Easels / moveable whiteboards (If not, wall space will do) 1 per group
Printed worksheets
Sharpies for all
Post-its for all
Tape (to stick the worksheets up)

What does God need with a starship?

Let's assume you have a product that is already working. This product has different problems or aspects that it has accomplished quite well.

But at the end of the day, you needed to redesign your existing product because of the aesthetic concerns, or because of the new needs that arise over time. How will you manage this process?

Should you change the current product in one go? Or is it better to spread this process over time? What will your users like in your new design? Is there really such an action needed? In this talk, let's learn how to manage a redesign process!