How might we allow users to seamlessly manage their installation service purchase?

Offering installation service

Introduction

I was the co-UX lead, designing the Promotions management system and subsequent features on gCMS, Google Store’s native content management system. gCMS was in its third year of development and trying to meet parity and enhanced functionality with its legacy systems. I needed to solve for how marketing promotions would be managed, scaled, and evolve with the business’ increasing objectives and needs.  


Key context

  • The original system was built exclusively by software engineers

  • Many unknowns and dependencies existed regarding long-term feasibility and scaling

  • A north star and perspective for promotions was necessary to have a functional MVP

Jump to solution


Role and team

UX lead working with Product, Engineering, and Legal teams

Project scope

  • Early 2021 - Early 2022

  • 3 quarters, 9 months

Discovery

bsorbed an overwhelming amount of necessary baseline knowledge to understand how the existing.

bsorbed an overwhelming amount of necessary baseline knowledge to understand how the existing promotions management system had come to be. In addition, it was challenging to scope a “scalable” solution without understanding the business’ promotion vision on the site. Initially, my goal was to define a rough ideal state in which promotions could exist in the future, both on the front-end and back-end. Because this was Google Store’s first attempt to streamline a strategy.

Result

Although launched in phases over a span of 9 months, the addition of promotions management to the gCMS platform had a sizable impact, largely on operator workflow efficiency. Although the numbers are unclear, product managers reported a significant increase in promotion deployment in 2021, with less user publisher resourcing needed compared to past launches.

Next steps

It was a monumental feat to have such a robust MVP that could very well last for multiple quarters. But, there were still many areas that required clean up before UX could even impact a V2. Some outstanding items included:

  • Engineering partners to continue consolidating environments to unnecessary friction added to the user experience as a result

  • Import spreadsheet functionality to remove final piece of manual input work

  • Finding a way to view Staging code batch names on the interface

  • Scaling Rule set functionality to accommodate discount stacking