Gmail Product Design: An On-Demand Help Button Modeled on Amazon's Mayday

Quick Overview

A product design question on bringing a one-tap help feature like Amazon's Mayday, which paired customers with a live advisor who could see their screen, into Gmail. It tests goal and audience choice, a session design that protects private mail, and staffing cost, wait time, security and scam risk at Gmail's scale.

Gmail Product Design: An On-Demand Help Button Modeled on Amazon's Mayday

Company: Amazon

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Amazon introduced Mayday on its Kindle Fire tablets: with one tap, a customer opened a live video window with an Amazon advisor. The advisor could see the customer's screen but not the customer, could draw on the screen to point things out, and could walk the customer through a task or carry it out for them, free and at any hour. Suppose your team wanted to build something similar into Gmail. Explain how it would work: whom it would serve, which problems it would solve, how a help session would run from start to finish, and how you would decide whether it is worth offering. ```hint Count the stuck moments first List the situations in which a Gmail user is stuck badly enough to want live help, then ask what one-to-one help would cost across Gmail's user base before deciding who gets it. ``` ### Clarifying Questions - Is the main aim to lower support costs, keep paying customers, grow paid plans, or make Gmail easier for less confident users? - Should the help come from people, from software, or from a mix of the two? - Which accounts are in scope: free personal accounts, paid personal plans, business and school accounts, or all of them? - Is showing the user's screen to a helper acceptable in an email product, given that the screen is full of private messages? ### What a Strong Answer Covers - What made Mayday work, and which of its parts carry over to an email product and which do not - A goal and a target user group chosen with a reason, given Gmail's scale and its mix of free and paid accounts - An end-to-end session flow, including how the helper sees enough to help without exposing private mail - Staffing, cost and wait-time trade-offs, and how they shape who gets access - Success metrics with guardrails, plus privacy, security and abuse risks ### Follow-up Questions - How would you stop scammers from posing as live Gmail support to trick people into handing over their accounts? - If demand at launch were far above the staffing you planned for, what would you change first? - How would the feature work for a business account whose administrator controls the settings?

Overview: A product design question on bringing a one-tap help feature like Amazon's Mayday, which paired customers with a live advisor who could see their screen, into Gmail. It tests goal and audience choice, a session design that protects private mail, and staffing cost, wait time, security and scam risk at Gmail's scale.

Amazon logo
Amazon
Dec 2, 2023
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Amazon introduced Mayday on its Kindle Fire tablets: with one tap, a customer opened a live video window with an Amazon advisor. The advisor could see the customer's screen but not the customer, could draw on the screen to point things out, and could walk the customer through a task or carry it out for them, free and at any hour.

Suppose your team wanted to build something similar into Gmail. Explain how it would work: whom it would serve, which problems it would solve, how a help session would run from start to finish, and how you would decide whether it is worth offering.

Clarifying Questions Guidance

  • Is the main aim to lower support costs, keep paying customers, grow paid plans, or make Gmail easier for less confident users?
  • Should the help come from people, from software, or from a mix of the two?
  • Which accounts are in scope: free personal accounts, paid personal plans, business and school accounts, or all of them?
  • Is showing the user's screen to a helper acceptable in an email product, given that the screen is full of private messages?

What a Strong Answer Covers Guidance

  • What made Mayday work, and which of its parts carry over to an email product and which do not
  • A goal and a target user group chosen with a reason, given Gmail's scale and its mix of free and paid accounts
  • An end-to-end session flow, including how the helper sees enough to help without exposing private mail
  • Staffing, cost and wait-time trade-offs, and how they shape who gets access
  • Success metrics with guardrails, plus privacy, security and abuse risks

Follow-up Questions Guidance

  • How would you stop scammers from posing as live Gmail support to trick people into handing over their accounts?
  • If demand at launch were far above the staffing you planned for, what would you change first?
  • How would the feature work for a business account whose administrator controls the settings?