Questions › Execution › Google
Create a launch plan for a high-risk Gmail feature for creators
- Execution
- Hard
- 15 min
Problem Statement Description
Product context: Google is a consumer technology, ads, AI, and cloud company; its products include Search, YouTube, Android, Maps, Gmail, Chrome, Google Play, Workspace, and Google Cloud. Gmail is Google's email product; its products and surfaces include inbox, search, labels, spam protection, attachments, smart compose, and Workspace integrations.
You are a PM on Gmail at Google preparing to launch a high-risk feature designed for creators who use email to manage audience relationships, brand partnerships, sponsorship outreach, newsletters, collaborations, fan messages, and business operations. The feature may touch sensitive Gmail surfaces such as inbox organization, sending workflows, AI-assisted drafting, audience segmentation, monetization, or creator-to-fan communication, so the launch must account for trust, privacy, abuse, deliverability, and user control.
This is an execution-focused question. Your task is to create a launch plan that turns an ambiguous, risky product concept into a controlled rollout across Gmail’s global consumer and enterprise ecosystem. You should define how the team would prepare, sequence, monitor, and communicate the launch while protecting Gmail’s reliability and user trust.
Assume the feature has meaningful upside for creators but also elevated risk: it could be misused for spam, create privacy concerns, confuse recipients, affect inbox quality, trigger regulatory or policy review, or conflict with expectations from Workspace admins and everyday Gmail users. The launch plan should show how you would coordinate product, engineering, design, legal, privacy, trust & safety, support, marketing, and go-to-market partners.
The experience should consider:
- Target creator segments, eligible users, and whether the launch starts with allowlists, beta cohorts, regions, or specific creator categories
- Operating plan, milestones, owners, dependencies, and sequencing from internal testing through broader availability
- Readiness criteria for privacy, security, abuse prevention, policy review, accessibility, localization, support, and legal approval
- Instrumentation, launch dashboards, alerting, and metrics that indicate adoption, quality, abuse, deliverability, user trust, and creator value
- Go/no-go decision gates, experiment design, cohort expansion rules, and criteria for pausing or rolling back
- Risks to Gmail’s core experience, including inbox quality, sender reputation, recipient consent, spam perception, and enterprise admin concerns
- Communications plan for creators, recipients, support teams, internal stakeholders, and potentially Workspace customers
- Post-launch monitoring, incident response, escalation paths, feedback loops, and prevention of repeated launch issues
Your goal is to present a practical launch plan for a high-stakes Gmail creator feature that balances creator growth with Google’s standards for privacy, safety, reliability, and product quality at global scale.
What this question tests
- Prioritization
- Roadmap Thinking
- Stakeholder Management
- Launch Planning
Practise this question under interview conditions. Answer it out loud against a timer with an AI interviewer that asks follow-ups, then review the scored report.
Related Execution questions
- Google Pay has a launch delay caused by engineering constraints. How do you re-plan executionGoogle · Execution · Hard
- How would you run the first 90 days after taking over GeminiGoogle · Execution · Hard
- Google Pay has a launch delay caused by engineering constraints. How do you re-plan executionGoogle · Execution · Medium
- How would you run the first 90 days after taking over GeminiGoogle · Execution · Medium
- You have conflicting stakeholder requests for Maps. How do you decide what ships firstGoogle · Execution · Medium
- Prioritize five roadmap bets for Android when students is the main growth audienceGoogle · Execution · Medium
All Execution questions · Product manager interview questions by skill area