Google Play

Helping Google Play business development managers oversee and optimize their portfolio. 

 
 
 

THE CHALLENGE

Create a single place to track and manage developers in the ecosystem and reduce overhead of maintenance of multiple tools, training users and user frustration.

Impact: increased value of business development role 

3 month client project completed in Dec 2016. Worked alongside 3 engineers, and 1 business owner. 

 

MY ROLE

User Research Wireframing
Content Strategy
Low/ High Fidelity Prototyping
Usability Testing

 
 

Overview: All the apps on the Google play store are managed by a Google Play business development manager. Their goal is to keep their partners in their portfolio engaged, make sure they’re up to date on new Android platform news/ features and to help them achieve their business goals. The more successful the partners are, the more money Google Play makes. 

 

The impetus for this project was that there were too many tools…

- lack of ability to deliver insights when tools are in sync and talking to one another

Research: I kicked off the project by speaking to BD managers in 1:1 interviews and observational sessions in an attempt to understand what their day to day workflows and experiences were. After synthesizing the insights, I created a easily shareable and digestible deck called “The Life in the Day of a BD Manager”

From these insights, I realized that the initial goal of just combining the tools into one mega tool shouldn’t be the only goal. Instead, I sought to identify a few other areas of focus for design.

Defining the new experience:

How might we use data help BD managers become more proactive in their relationships with their partners within this new tool? 

How might we reduce the manual tasks that BD managers have to do regularly?

 

Together, with the product manager, we identified the primary task flows that a BD manager might use in this new tool. And then we came up with a few concept sketches.

After we got to a point where we felt that the flows were defined a bit more, we did a information architecture exercise among others to determine what information needed to be visible and accessible at every stage.