Improving Google Voice: Choosing a Segment and Prioritizing Its Biggest Pain Point

Quick Overview

A Google product improvement prompt asking how a product manager would make Google Voice better. It tests understanding the phone-number service and its users, choosing one segment, finding concrete pain points, prioritizing solutions with a scoped first release, and setting success metrics and guardrails.

Improving Google Voice: Choosing a Segment and Prioritizing Its Biggest Pain Point

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are the product manager for Google Voice, Google's service that gives people a phone number for calls, text messages and voicemail that works across their phones and computers. How would you improve the product? ```hint Pick whose problem Voice is used both as a free personal second number and as a paid business phone line. Choose one group, find the moment where the product lets them down, and only then propose changes. ``` ### Clarifying Questions - Should I focus on the free personal version, the paid version sold to businesses alongside Google Workspace, or both? - What is the goal behind improving it: more users, better retention, more revenue from business plans, or fewer support problems? - Are there constraints I should treat as fixed, such as the countries where Voice is offered or the telecom rules it has to follow for calling and texting? - Can the improvement involve other Google products, such as Calendar, Gmail or Meet, or should it stay inside the Voice apps? ### What a Strong Answer Covers - An accurate picture of what Voice does today and who uses it, with a reasoned choice of one segment. - Concrete pain points for that segment, tied to real moments (an important call that goes unanswered, spam, keeping personal and work life apart, follow-up after a call). - Several distinct solutions, prioritized with explicit criteria, and one recommendation with a scoped first release. - Success metrics with at least one guardrail. - Risks specific to a phone service: call-recording consent, messaging abuse, accuracy of any automated features and telephony cost. ### Follow-up Questions - How would you reduce spam calls and texts without blocking legitimate calls from unknown numbers, such as a clinic calling back? - How would you decide whether your improvement should also reach free personal users or stay a paid business feature? - If engineering could support only one platform for the first release (Android, iPhone or web), which would you pick, and why?

Overview: A Google product improvement prompt asking how a product manager would make Google Voice better. It tests understanding the phone-number service and its users, choosing one segment, finding concrete pain points, prioritizing solutions with a scoped first release, and setting success metrics and guardrails.

Google logo
Google
Jan 19, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are the product manager for Google Voice, Google's service that gives people a phone number for calls, text messages and voicemail that works across their phones and computers. How would you improve the product?

Clarifying Questions Guidance

  • Should I focus on the free personal version, the paid version sold to businesses alongside Google Workspace, or both?
  • What is the goal behind improving it: more users, better retention, more revenue from business plans, or fewer support problems?
  • Are there constraints I should treat as fixed, such as the countries where Voice is offered or the telecom rules it has to follow for calling and texting?
  • Can the improvement involve other Google products, such as Calendar, Gmail or Meet, or should it stay inside the Voice apps?

What a Strong Answer Covers Guidance

  • An accurate picture of what Voice does today and who uses it, with a reasoned choice of one segment.
  • Concrete pain points for that segment, tied to real moments (an important call that goes unanswered, spam, keeping personal and work life apart, follow-up after a call).
  • Several distinct solutions, prioritized with explicit criteria, and one recommendation with a scoped first release.
  • Success metrics with at least one guardrail.
  • Risks specific to a phone service: call-recording consent, messaging abuse, accuracy of any automated features and telephony cost.

Follow-up Questions Guidance

  • How would you reduce spam calls and texts without blocking legitimate calls from unknown numbers, such as a clinic calling back?
  • How would you decide whether your improvement should also reach free personal users or stay a paid business feature?
  • If engineering could support only one platform for the first release (Android, iPhone or web), which would you pick, and why?