Set the vision and prioritized roadmap for Google's Inbox email app

Quick Overview

A Google product strategy question asking you to act as product owner for the Inbox email app and lay out its roadmap. It tests setting a vision, choosing users and problems, sequencing themes by impact and dependencies, defining success metrics with guardrails, and handling the app's relationship with Gmail.

Set the vision and prioritized roadmap for Google's Inbox email app

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Imagine you are the product owner for Google Inbox. Lay out the product roadmap you would drive: where you would take the product, which users and problems you would focus on, what you would build first and what later, and how you would measure progress. ```hint Start from what Inbox is for Before naming any feature, decide what job Inbox does for its users that ordinary email does not. Group the work into a few themes that serve that purpose, then sequence the themes by impact and by what each one depends on. ``` ### Clarifying Questions - Does "Google Inbox" mean the separate Inbox by Gmail app, which ran on top of Gmail accounts, or the inbox experience inside Gmail itself? - Is the roadmap for consumers using personal accounts, for businesses using Google's paid workplace email, or both? - What horizon should the roadmap cover, and what team size should I assume? - What does leadership want most from the product: growing its own user base, or proving new ideas that later move into Gmail? ### What a Strong Answer Covers - A clear product vision and goal, grounded in what Inbox is for compared with Gmail and other email clients. - A chosen user segment and its most important email problems, used to derive the roadmap themes. - Themes prioritized and sequenced into now, next and later, with reasoning about impact, effort, dependencies and risk. - Metrics for the roadmap's goals with guardrails, and how the roadmap is revisited as results come in. - Risks such as users' trust in automation that sorts their mail, privacy, and confusion or cannibalization between two Google email apps. ### Follow-up Questions - Leadership asks whether Google should keep two email apps at all. What do you recommend, and what happens to your roadmap? - An automatic sorting feature on your roadmap misfiles some important messages in testing. How do you decide whether it is ready to launch? - How would the sequencing change if the goal were winning paying business customers rather than consumers?

Overview: A Google product strategy question asking you to act as product owner for the Inbox email app and lay out its roadmap. It tests setting a vision, choosing users and problems, sequencing themes by impact and dependencies, defining success metrics with guardrails, and handling the app's relationship with Gmail.

Google logo
Google
May 8, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Imagine you are the product owner for Google Inbox. Lay out the product roadmap you would drive: where you would take the product, which users and problems you would focus on, what you would build first and what later, and how you would measure progress.

Clarifying Questions Guidance

  • Does "Google Inbox" mean the separate Inbox by Gmail app, which ran on top of Gmail accounts, or the inbox experience inside Gmail itself?
  • Is the roadmap for consumers using personal accounts, for businesses using Google's paid workplace email, or both?
  • What horizon should the roadmap cover, and what team size should I assume?
  • What does leadership want most from the product: growing its own user base, or proving new ideas that later move into Gmail?

What a Strong Answer Covers Guidance

  • A clear product vision and goal, grounded in what Inbox is for compared with Gmail and other email clients.
  • A chosen user segment and its most important email problems, used to derive the roadmap themes.
  • Themes prioritized and sequenced into now, next and later, with reasoning about impact, effort, dependencies and risk.
  • Metrics for the roadmap's goals with guardrails, and how the roadmap is revisited as results come in.
  • Risks such as users' trust in automation that sorts their mail, privacy, and confusion or cannibalization between two Google email apps.

Follow-up Questions Guidance

  • Leadership asks whether Google should keep two email apps at all. What do you recommend, and what happens to your roadmap?
  • An automatic sorting feature on your roadmap misfiles some important messages in testing. How do you decide whether it is ready to launch?
  • How would the sequencing change if the goal were winning paying business customers rather than consumers?