This is the era of voice experience. As a Product Owner, how do you decide what exactly to enable as part of a branded voice experience? Kelly Rader, VP of Digital Experience shares best practice guidelines for voice user interface design.
This is the era of voice experience. People of all ages are fascinated with voice features and assistants like the Echo, Alexa, Ecobee and Spot that can do everything from answer general questions to wake you up or even give you the balance of your checking account. The popularity of voice capabilities makes sense, too. It’s easy. Talking is so natural. We have conversations all day, every day, plus we talk faster than we type.
As a Product Owner, how do you decide what exactly to enable as part of a branded voice experience? Well, for some businesses the answer is obvious. If you’re Uber, you focus on all the ways a customer might ask for a ride. If you represent a pizza brand, you start with how to order a pie.
If it’s not obvious to you, try to prioritize features with voice-enablement for the most common interaction with a brand. Look at call center data and IVR menu options. Which common tasks do customers access most? Which tasks are the most costly to the business? Armed with those answers, reach out to design teams. To encourage success, give your design teams guidance, data and prep-time to explore journeys for different candidate tasks. Allow plenty of time to create story artifacts for the top voice features because designing a voice user interface(VUI) is really different from designing a graphical user interface (GUI). Here are just a few best practice guidelines to follow.
If you are looking to build voice capabilities into a brand experience and need support, contact Object Edge or Sarah Falcon directly at sarah.falcon@objectedge.com.
