Gmail · Product sense · Entry · 45 to 60 minutes

Should Gmail Enable Actions Inside Emails?

Gmail is Google's email service, used by people to send, receive, and manage messages on the web and on phones. Answer this product management case and get it graded line by line against a weighted rubric.

Product sense
User empathy
Prioritization
Metrics thinking
Tradeoff analysis

The situation

You are a PM on Gmail in 2013. The team has noticed that many emails are really prompts to do something next, such as reply to a conversation, like a post, or follow an account after getting a notification from another service. Today, the usual path is long: open the message, click a link, wait for another page or app to load, then complete the action there. Some teammates believe Gmail could make these tasks easier and more useful by helping users finish common actions without leaving the email context. Others are concerned that adding interactive actions could clutter the inbox, create trust and safety issues, or only help a small set of cases while adding product complexity. Your manager wants a recommendation on whether Gmail should invest in this area now, and if so, what the first version should be. The timing matters because mobile use is growing, extra taps and page loads are more painful, and the team wants a focused improvement that helps users without making email feel noisy or risky.

What to produce

Write a 1 page product recommendation memo, about 500 to 700 words.

Your answer must

Name the primary user and the single use case Gmail should solve first.
Map the current user flow from receiving an email to completing the follow up action, and identify the biggest point of friction.
Make a clear recommendation on whether Gmail should build an in email action feature now, and describe one focused MVP experience.
Define 3 success metrics, including 1 primary metric and at least 1 guardrail metric related to trust, safety, or mistakes.
Outline a lightweight test or rollout plan, and list the top 2 risks with a mitigation for each.

Constraints

Keep the scope to Gmail's inbox and message experience, not redesigning outside products or services.
Do not rely on major changes to email standards or unrealistic new permissions.
Preserve user trust, safety, and inbox simplicity, avoid solutions that would make phishing or accidental actions more likely.

Format

Use short sections with headings: user problem, recommendation, MVP, metrics, risks, test plan.

How Gmail actually played it

Looks at Gmail quick actions and hypothesises that letting users act inside an email would raise conversion on reply, like and follow steps. Short case on removing steps in a funnel.

Every extra click lowers conversion
Test where actions can happen in place

Built from The Email Growth Tactic You Need To Be Following by Brian Balfour.