Context

The Google AR Maps team brought me on board to help them tackle the mounting number of research unknowns. This engineering-heavy team was distributed across Seattle, Mountain View, and San Francisco. An early mock-up was released at the company conference (Google I/O) putting the team under some pressure to produce a functional and mind-blowing AR Maps experience within six months. As the second UX Researcher to join, I was tasked with coordinating the transition from a reactive to a proactive-based research strategy.

Objectives

• Quickly test AR prototypes by building out an iterative research pipeline

• Increase research efficiency for insights into this emerging technology space

• Test many ideas efficiently to narrow focus, learn what works and what doesn't, to build up a knowledge base in the emerging tech space

Process

Being in an emerging tech space with a lack of clear user-informed direction, the biggest need was to help build our knowledge base of mobile world-scale AR usage to establish the building blocks for which we could build any AR experience. I established an iterative research pipeline centered around two-week iteration cycles. Each two-week cycle starts with a research meeting where we identify, prioritize and align the biggest research unknowns.

Next, I selected the best method for the chosen research area. Methods used include concept studies, participatory design, usability studies, cognitive walkthroughs, and interviews. The two-week cycle concluded as I delivered actionable insights, grew our knowledge map, and prepared to kick off the next round of prototype testing.

Impact

• Tripling the number of ideas tested by the team

• Informing product direction with a growing knowledge repository informed by user behavior

• A more informed strategic direction via clear design principles limiting the amount of wasted development time

Reflection

The most enjoyable part of this project was the iterative nature of both the research and my approach. Each two-week research project was followed by a new one, allowing me to constantly refine the process. The most significant areas of improvement were; clear expectation setting with my stakeholders by setting (and reminding) teammates of timelines and next steps, and being more forceful in prioritizing only impactful research. The most interesting part of this work was the underlying team dynamics. I learned how to better manage the pressures team members face and to present a clear path to what we can accomplish.