Senior-friendly phone: choosing the user segment, key features and success measures

Quick Overview

A product design interview question asking a product manager to design a phone for elderly people. It tests comparing segments of older users, identifying the needs today's phones leave unmet, prioritizing hardware, software and setup features, and defining success metrics with guardrails and risks.

Senior-friendly phone: choosing the user segment, key features and success measures

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are a product manager asked to design a phone for elderly people. Explain what the product should achieve, decide which older users it is for and what today's phones fail to do for them, then propose, prioritize and measure the features you would build. ```hint Follow one person's day Pick one older user and walk through an ordinary day with the phone they own now; the moments where they give up or have to ask someone for help show what your design must fix first. ``` ### Clarifying Questions - Is this a mobile phone, and are we building a new handset, a simplified software experience on an existing handset, or both? - Is the goal to win new buyers among older adults, to keep existing owners using their phones, or to support their safety and independence? - Which age range and market do we mean, and are we designing for healthy older adults in general or for people with specific conditions such as low vision, hearing loss or a tremor? - Who usually buys and sets up the phone: the older person, or an adult child or caregiver? ### What a Strong Answer Covers - A stated goal for the product and the business reason a phone maker would build it - Older-user segments compared, with one chosen and the reason, plus the role family members or caregivers play - Concrete pain points for the chosen segment, drawn from how they use a phone today and ranked by severity - Solutions spanning hardware, software and setup, prioritized with explicit criteria - A primary success metric with guardrails, and the main risks with mitigations ### Follow-up Questions - How would you test the design with older users before committing to new hardware? - How would you keep the phone from feeling like a product "for old people" that buyers are reluctant to carry? - If early sales were strong but many phones went unused after a month, how would you find out why, and what would you change?

Overview: A product design interview question asking a product manager to design a phone for elderly people. It tests comparing segments of older users, identifying the needs today's phones leave unmet, prioritizing hardware, software and setup features, and defining success metrics with guardrails and risks.

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

You are a product manager asked to design a phone for elderly people. Explain what the product should achieve, decide which older users it is for and what today's phones fail to do for them, then propose, prioritize and measure the features you would build.

Clarifying Questions Guidance

  • Is this a mobile phone, and are we building a new handset, a simplified software experience on an existing handset, or both?
  • Is the goal to win new buyers among older adults, to keep existing owners using their phones, or to support their safety and independence?
  • Which age range and market do we mean, and are we designing for healthy older adults in general or for people with specific conditions such as low vision, hearing loss or a tremor?
  • Who usually buys and sets up the phone: the older person, or an adult child or caregiver?

What a Strong Answer Covers Guidance

  • A stated goal for the product and the business reason a phone maker would build it
  • Older-user segments compared, with one chosen and the reason, plus the role family members or caregivers play
  • Concrete pain points for the chosen segment, drawn from how they use a phone today and ranked by severity
  • Solutions spanning hardware, software and setup, prioritized with explicit criteria
  • A primary success metric with guardrails, and the main risks with mitigations

Follow-up Questions Guidance

  • How would you test the design with older users before committing to new hardware?
  • How would you keep the phone from feeling like a product "for old people" that buyers are reluctant to carry?
  • If early sales were strong but many phones went unused after a month, how would you find out why, and what would you change?