Google Cloud

Marketplace

Goals

Led the design of Google Cloud Marketplace, a central area for users to discover and deploy GCP and 3rd party services, VM images and APIs

Roles

Led the cross-functional alignment of 3 teams to get buy-in on integration. Presented to a VP of eng to get conceptual approval. Led a team of 3 UX designers and 1 visual designer to create the designs and worked with cross-functional stakeholders from concept to implementation.

Outcomes

The GCP Marketplace has become the primary method for users to discover and deploy 1st and 3rd solutions.

The new marketplace powered API Library was a success with enablement increasing 7.1% in GCP and 13.49% in the API console.

Project details

01

Problem

Discovery and deployment of various solutions (APIs, VM images, GCP services and 3rd party solution) was divided between the API Library, Launcher and GCP left-nav. This redundancy forced users to search in 3 different areas to discover relevant solutions.

1 / 11
1 / 11
1 / 11

02

Solutions

I Led the cross-functional alignment of 3 teams to get buy-in on integration. Presented to an engineering VP to get conceptual approval. Led a team of 3 UX designers and 1 visual designer to create the designs and worked with cross-functional stakeholders from concept to implementation.

Solution 01

Google Cloud Marketplace

Google Cloud Marketplace brought together 3 separate but similar solutions into one integrated area for users to discover 1st and 3rd party solutions, VM images and APIs.

1 / 11
1 / 11
1 / 11
1 / 11
Soltuion 02

Marketplace embedded in other GCP services

Marketplace functionality was also embedded in other Google Cloud products. When creating Virtual Machines or enabling APIs, users could use Marketplace within those services, without loosing context.

1 / 11
1 / 11
1 / 11
1 / 11

03

Outcomes

The UX researchers for my product area (APIs) ran extensive AB tests, surveys and monitored success metrics during the staged rollout. The new marketplace powered API Library was a success with enablement increasing 7.1% in GCP and 13.49% in the API console. There was a statistically significant decrease in time to enablement and there was no statistically significant change in CSAT.