Google Pay Strategy: Sequencing Next-Year Priorities and a Three-Year Direction

Quick Overview

A product strategy question that asks a product manager to lay out Google Pay's roadmap in two horizons: what to deliver over the next year and where to take the product over three years. It tests goal setting, market choice, thinking across consumers, merchants and banks, prioritization by horizon, and choosing metrics for each.

Google Pay Strategy: Sequencing Next-Year Priorities and a Three-Year Direction

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are the product manager for Google Pay. Build its product roadmap in two horizons: what you would deliver over the next year, and where you would take the product over the next three years. Explain the goal the roadmap serves, which users and partners it is built around, what goes into each horizon and why it belongs there, and how you would tell whether the plan is working. ```hint Let one goal drive both horizons Settle what Google Pay should achieve for its users and for Google before you list ideas. Then test each idea: can it ship with today's product and partners, or does it depend on new partnerships, regulation or a change in the product's role? ``` ### Clarifying Questions - Which market should the roadmap target: the United States, where in-store phone payments compete with Apple Pay on iPhones, India, where Google Pay runs on the national real-time bank-transfer system, or a global plan? - Which goal matters most to leadership: more active payers and payment volume, new revenue, or the value Pay adds to the rest of Google's products? - Which surfaces are in scope: tap-to-pay in stores from Android phones and watches, checkout on the web and in apps, peer-to-peer transfers, or all of them? - Does the roadmap cover partnerships and go-to-market with merchants, banks and card networks, or product features only? ### What a Strong Answer Covers - A clear goal for Google Pay and a reasoned market choice that both horizons serve. - The payments ecosystem (consumers, merchants, banks and card networks, developers) and which side limits growth in the chosen market. - A one-year plan of prioritized bets that can ship on the current product, and a three-year direction that changes Google Pay's role, with a reason each item sits in its horizon. - Metrics for each horizon, with guardrails for fraud, payment failures, privacy and partner health. - Risks and dependencies: competition, regulation, partner incentives, and what would make you revise the plan. ### Follow-up Questions - Your three-year plan adds lending or other financial services. Would you build them or partner, and which regulatory, credit and trust problems must be solved first? - What result at the end of year one would make you change the three-year direction, and which metric would tell you? - Banks often prefer customers to use their own apps. How would you get card issuers to support Google Pay setup in the first year?

Overview: A product strategy question that asks a product manager to lay out Google Pay's roadmap in two horizons: what to deliver over the next year and where to take the product over three years. It tests goal setting, market choice, thinking across consumers, merchants and banks, prioritization by horizon, and choosing metrics for each.

Google logo
Google
Oct 8, 2024
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are the product manager for Google Pay. Build its product roadmap in two horizons: what you would deliver over the next year, and where you would take the product over the next three years.

Explain the goal the roadmap serves, which users and partners it is built around, what goes into each horizon and why it belongs there, and how you would tell whether the plan is working.

Clarifying Questions Guidance

  • Which market should the roadmap target: the United States, where in-store phone payments compete with Apple Pay on iPhones, India, where Google Pay runs on the national real-time bank-transfer system, or a global plan?
  • Which goal matters most to leadership: more active payers and payment volume, new revenue, or the value Pay adds to the rest of Google's products?
  • Which surfaces are in scope: tap-to-pay in stores from Android phones and watches, checkout on the web and in apps, peer-to-peer transfers, or all of them?
  • Does the roadmap cover partnerships and go-to-market with merchants, banks and card networks, or product features only?

What a Strong Answer Covers Guidance

  • A clear goal for Google Pay and a reasoned market choice that both horizons serve.
  • The payments ecosystem (consumers, merchants, banks and card networks, developers) and which side limits growth in the chosen market.
  • A one-year plan of prioritized bets that can ship on the current product, and a three-year direction that changes Google Pay's role, with a reason each item sits in its horizon.
  • Metrics for each horizon, with guardrails for fraud, payment failures, privacy and partner health.
  • Risks and dependencies: competition, regulation, partner incentives, and what would make you revise the plan.

Follow-up Questions Guidance

  • Your three-year plan adds lending or other financial services. Would you build them or partner, and which regulatory, credit and trust problems must be solved first?
  • What result at the end of year one would make you change the three-year direction, and which metric would tell you?
  • Banks often prefer customers to use their own apps. How would you get card issuers to support Google Pay setup in the first year?