Google Maps Market-Entry Call: Moving From Restaurant Discovery Into Dining Services

Quick Overview

A product strategy case asking whether Google Maps should expand beyond helping people find restaurants into the restaurant business itself. It tests how a candidate defines the possible forms of entry, weighs Google's assets against partner, operational and regulatory risks, and lays out a phased plan with success metrics.

Google Maps Market-Entry Call: Moving From Restaurant Discovery Into Dining Services

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Google Maps is already one of the main places people go to decide where to eat. Should Google take Maps a step further and enter the restaurant business itself? Give a clear recommendation. Explain what entering the restaurant business could realistically mean for Maps, how you would compare those options, and how you would roll out and measure the one you choose. ```hint Define "enter" before answering The phrase covers very different moves, from running kitchens to letting diners finish a transaction without leaving Maps. Spell out the realistic forms, then test each against what Maps already does well and what Google would have to build from nothing. ``` ### Clarifying Questions - Does "the restaurant business" mean owning or running restaurants and delivery-only kitchens, or does it also cover services Maps could provide, such as table bookings, food ordering, payments or software for restaurant owners? - What is Google trying to achieve: new revenue, more engagement in Maps, stronger local advertising, or keeping restaurant discovery from moving to other apps? - Can Google partner with or acquire existing reservation and delivery companies, or should the answer assume it builds everything itself? - Which markets come first: the US only, or global from the start? ### What a Strong Answer Covers - A clear set of entry options, from operating restaurants to completing bookings and orders inside Maps, and an explicit recommendation. - Google's advantages for each option, such as diner intent at the moment of choice, place data, reviews and existing ties with restaurant owners, weighed against its weaknesses in operations, logistics and thin restaurant margins. - How restaurants, diners and the reservation and delivery companies that depend on discovery traffic would react to each move. - A phased rollout with success metrics for diners, restaurants and Google, plus the results that would end the effort. - Risks such as antitrust scrutiny of self-preferencing, the neutrality of Maps rankings and the cost of supporting real transactions. ### Follow-up Questions - If diners could book or order without leaving Maps, how would you keep rankings trusted when Google earns money from some restaurants and not others? - Many restaurants already pay commissions to delivery apps. What, if anything, would you charge them, and why? - What pilot results would convince you to stop and fall back to sending diners to outside services?

Overview: A product strategy case asking whether Google Maps should expand beyond helping people find restaurants into the restaurant business itself. It tests how a candidate defines the possible forms of entry, weighs Google's assets against partner, operational and regulatory risks, and lays out a phased plan with success metrics.

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

Google Maps is already one of the main places people go to decide where to eat. Should Google take Maps a step further and enter the restaurant business itself?

Give a clear recommendation. Explain what entering the restaurant business could realistically mean for Maps, how you would compare those options, and how you would roll out and measure the one you choose.

Clarifying Questions Guidance

  • Does "the restaurant business" mean owning or running restaurants and delivery-only kitchens, or does it also cover services Maps could provide, such as table bookings, food ordering, payments or software for restaurant owners?
  • What is Google trying to achieve: new revenue, more engagement in Maps, stronger local advertising, or keeping restaurant discovery from moving to other apps?
  • Can Google partner with or acquire existing reservation and delivery companies, or should the answer assume it builds everything itself?
  • Which markets come first: the US only, or global from the start?

What a Strong Answer Covers Guidance

  • A clear set of entry options, from operating restaurants to completing bookings and orders inside Maps, and an explicit recommendation.
  • Google's advantages for each option, such as diner intent at the moment of choice, place data, reviews and existing ties with restaurant owners, weighed against its weaknesses in operations, logistics and thin restaurant margins.
  • How restaurants, diners and the reservation and delivery companies that depend on discovery traffic would react to each move.
  • A phased rollout with success metrics for diners, restaurants and Google, plus the results that would end the effort.
  • Risks such as antitrust scrutiny of self-preferencing, the neutrality of Maps rankings and the cost of supporting real transactions.

Follow-up Questions Guidance

  • If diners could book or order without leaving Maps, how would you keep rankings trusted when Google earns money from some restaurants and not others?
  • Many restaurants already pay commissions to delivery apps. What, if anything, would you charge them, and why?
  • What pilot results would convince you to stop and fall back to sending diners to outside services?