Creating a Vision & Telling a Story
Challenge: How to create a vision for a product and communicate it effectively. Approach: Tell them a story that allows them to visualize the process. Contribution: The storyteller and visualizer. Year: 2016
We were at the very beginning of the DIVA our Digital Intelligent Voice Assistant. The task was to build a voice assistant for e-commerce. My entire career has taught me, again and again, “communication is key.” I knew I had to find a way to create a vision and communicate it to the team so everybody understood our goal. It needed to be simple, so that even non-technical people would grasp it.
To understand the possibilities of intelligent assistants and voice recognition, I read many articles and downloaded every possible application to see how far things had been pushed. I completed several product purchases with these apps, and documented the process.
Documenting the buying process in a text based ecommerce assistant
The product arrived at home
Documenting the return process
With Alexa in my home and Siri on my phone, I tried as many interactions as possible. At the end of the research phase I had a good understanding of the landscape and the approaches that were used.
Experiencing voice interfaces with Alexa
Part of the research was to introduce my three-year-old daughter to voice assistants. Seeing how quickly she was able to search for specific videos without being able to write was amazing. This is when I truly grasped how important voice will be for the future of human-computer-interaction.
Our Vision Statement
While doing the research, I already was working on the vision. Since the team was scattered around and focused on other tasks, it was difficult to integrate them into process. The general idea I have regarding interfaces is they are just a glass pane. We interact with computers and smartphones through different tools (mouse, keyboard and touch) just to have information displayed on the glass. The addition of voice recognition and language understanding would make the “glass” much faster. It all boils down to the following vision statement.
To communicate the vision, I came up with the idea of using an analogy of a salesman standing behind the glass, where the glass symbolizes the device’s screen. Here’s the email that I wrote to the team:
The feedback I received on the story was very good. “Wow! the best piece I read about a voice interface. Genius!!!!” The story was then also shared with partners to tell them about the product that we were working on.
The First Prototype
The vision statement was the North Star. The story was our binoculars to see the North Star more clearly. Now we needed something more tangible to know what we would try to build. The best way to do that was to make the product real. My starting point for designing interfaces is (if possible) to look at what is out there and learn from it. See the good things and the not so good things. You immediately can test interaction patterns without building them on your own. The next step was designing an interface. The goal wasn’t to have perfect usability, but an interface to tell a story. For a new project it is also a design exercise because the first version of the design language can be explored in a very simple way.
So, I started and designed the very first version of DIVA. I shared the first designs with the iOS engineer. It is always helpful to get feedback from peers, four eyes see more than two. For the first designs, I used Marvel to make them interactive and easily sharable.
Our User Story told with Personas
But the prototype was not enough, and didn’t tell the whole story. To show the benefits of such an interface, I used personas and embedded the interface in a real life situation. That way I also could show potential AI capabilities and discuss with the team what is possible for us. I extracted the features and highlighted what the AI would need to accomplish to deliver that experience.
The visualized story was used extensively, internally, and with external business partners. I later extended the story to other scenarios. It served us very well and gave us all a shared understanding of what we wanted to build.