UX Research Case Study

Voice User Interface for GoogleMaps

My Skillsets & Tools Utilized
Voice UI
Automotive
UX Research
Wireframing
Case Study
Information Architecture
Protopie
Figma
Rapid Prototyping
Client
Google
Designer(s)

Isaac Tseng (Interaction Design)
Bryana Lee (Interaction Design)
Yuna Kim (Interaction Design)
Jaemo Seong (Interaction Design)

Research Project Details

Successful design was determined upon higher numeric scoring from our user test trials based on our evaluation methods.

Test 1:

Test A: “ping” sound notification - Average Situation Awareness Level: 8.75/15
Test B: “ping” sound notification and voice over - Average Situation Awareness Level: 13.5/15

A “ping” sound combined with voice over is useful for creating Situation Awareness, especially when it is the driver’s first time ever hearing this notification.
- The “ping” is the necessary attention grabber to create successful Perception.
- The voice-over explains what is going on to create successful Comprehension.
- The voice-over’s question that follows the description of the situation informs the driver of what they can expect to be the next procedure to create successful Projection.

Test 2:

Test A: VUI screen feedback with color only - Average Situation Awareness Level: 13/15
Test B: VUI screen feedback with text only - Average Situation Awareness Level: 11/15

Color UI was more effective than using text for an in-car voice user interface based on Situation Awareness. When asked about a potential combination of color and text, testers were hesitant because they felt it would be informational overload. Testers did mention that a verbal repeat of their total order would be helpful to double check that their order was correctly heard.

Test 3:

Test A: “Switch to a different route? Yes or No” - Ease of Use Score: 5/5
Test B: “Switching to a different route in 5 secs. Cancel.” - Ease of Use Score: 2.5/5

Providing a “yes or no” choice is a much more preferred option to cancelling an impending change during driving. The choice provides a much clearer indication to the driver of what process is happening and when they should provide input to the VUI.

Test 4:

The flows were easy to follow overall and having redundant information both spoken and written on screen was helpful in case the user missed something audibly.Users overall would like to have a unique sound to indicate when it’s user’s turn to speak in addition to the yellow glow.

Methodology

This research project was conducted in 4 segments:

  1. Testing a sound/voice-based alarm/notification
  2. Testing different screen-based feedback for voice inputs
  3. Testing different mental models
  4. Testing overall dialogue flow and visual feedback

These 4 separate tests were devised to methodically research different aspects that voice user interface design needs to consider. Each test was performed using a working live prototype on Protopie that reacted directly to voice input.

Tests 1, 2 and 3 utilized A-B testing and numeric scoring to evaluate effective design choices. Each test used a specific task flow to test variables.

The final 4th test on overall dialogue flow utilized qualitative feedback and numeric scoring to evaluate effectiveness. 3 different task flows were tested for potential friction points, comprehension, and overall ease of use.

Evaluation

Test 1 + 2 tested notifications and feedback using Situation Awareness Evaluation on 3 levels:

  1. Perception (How well the user's attention is attained)
  2. Comprehension (How quickly the user understands the prompt/notification)
  3. Projection (How well the user can predict what should happen next)

Test 3 tested user's mental models and evaluated user projection under an emergency navigation change:

  1. Switch to a different route? Yes or No (Ignore is stay on current path)
  2. Automatically switching to a different route in 5 secs. Cancel. (Ignore is to choose new path)

Test 4 collected qualitative feedback on the ease of use of 3 dialogue flows:

  1. Placing an order for pick up or delivery home from Mendocino Farms.
  2. Making a restaurant reservation, routing to multiple locations, and sharing your ETA to multiple parties.
  3. Picking up a curbside order from Ralph’s Grocery Store, routing to multiple locations, and sharing ETA to multiple parties.

Guiding Questions - How Might We...

- prototype personalized food recommendations with VUI based on individual user preferences, previous orders, and dietary restrictions?
- minimize distractions and ensure safe VUI operation experiences?
- design VUI to answer multiple requests effectively in one command rather than separate conversation interactions?
- structure a conversation that inspires trust in a VUI to execute commands perfectly?
- integrate food ordering with in-car navigation and driving through VUI?
- influence user trust, especially in terms of order accuracy, timely delivery, and payment security?

Overall Conclusion:

- Clear verbal affirmation and reiteration is needed for lengthy orders, commands or reservations.

- Visual feedback can be kept simple and minimal, as long as the auditory feedback is sufficient in notifying the user if the VUI is listening, what the VUI has heard, and whether a command has successfully been executed.

- The visual feedback should serve to support the voice as a reassurance, and not distract the user’s eyes away from the road.

- The VUI should never assume the user’s intentions. Whether in an emergency alert situation or a food ordering situation, the VUI should provide the user options rather than an automated decision so that the user still feels in control and can build trust.

This is Giga, the persona for our Voice User Interface. We wanted to create a VUI bot that was reliable and calm, especially for the use case within a car as a driver or passenger. Giga’s personality is more on the warm side, however he maintains a more formal tone when speaking. Emotionally we have designed him to be more neutral as well so that he remains calm in a stressful environment like driving. Visually we designed Giga with several different faces. The largest you see is the default face, with four other variations below dependent on the situation.

Objectives

The main objective of this project was to study effective speech patterns and signifiers necessary in a Voice User Interface for automotive use.

Target Audience

User Testing Recruitment Criteria

Generations:
- Millennials
- Gen Z

Technological Skill:
- Experienced users of in-car smartphone mirroring technology such as Apple CarPlay and Android Auto
- Occasional to experienced users of Google Maps for navigation
- Average to savvy technological skill
- Average to no experience with using Voice User Interfaces

An even mix of user testers were recruited for each test. (4 recruits per test)

Design Proposal
Details
Explore Other Projects