Product Design: A Multi-Source News App for Older Adults

Quick Overview

Design a news aggregation product for older adults, deciding which seniors to serve and what the first version must include. The prompt tests audience segmentation, accessibility and trust-aware product thinking, MVP prioritization, and choosing success metrics and guardrails for a calm, reliable news habit.

Product Design: A Multi-Source News App for Older Adults

Company: Microsoft

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Design a service that gathers news from many outlets into one place, built specifically for older people. Explain exactly who you would build it for, which of their problems it solves, what the first version includes, and how you would measure whether it succeeds. ```hint Narrow the audience "Elderly" spans recent retirees to people in their nineties, with very different eyesight, comfort with devices and reasons for following the news. Choose one group and let its specific limits and habits drive the design. ``` ### Clarifying Questions - Which age range counts as the elderly market here, and in which country and language would the service launch? - Is this a new standalone product, or can it build on a news product, browser or device the company already runs? - Is success judged on reach and engagement first, or must the service make money (ads or subscriptions) from launch? - Which devices should it cover: phones and tablets only, or also TVs and smart speakers? ### What a Strong Answer Covers - A segmentation of older news readers and a justified choice of target group - Pain points rooted in this audience: physical accessibility, overload and clutter, trust in sources, and exposure to scams or misinformation - A prioritized first version whose features map to the chosen pain points, with later phases sketched - A goal and success metrics centered on staying informed as a habit, with guardrails - Risks such as patronizing design, misinformation, publisher licensing and privacy in any family features ### Follow-up Questions - How would you keep misinformation and scam-like content out of the service without making it feel censored? - An older reader's family wants to set up and keep an eye on the app for them. How far should that go, given the reader's privacy? - After launch, retention is strong but readers rarely open anything beyond the main daily view. Is that a problem?

Overview: Design a news aggregation product for older adults, deciding which seniors to serve and what the first version must include. The prompt tests audience segmentation, accessibility and trust-aware product thinking, MVP prioritization, and choosing success metrics and guardrails for a calm, reliable news habit.

Microsoft logo
Microsoft
Apr 27, 2026
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Design a service that gathers news from many outlets into one place, built specifically for older people. Explain exactly who you would build it for, which of their problems it solves, what the first version includes, and how you would measure whether it succeeds.

Clarifying Questions Guidance

  • Which age range counts as the elderly market here, and in which country and language would the service launch?
  • Is this a new standalone product, or can it build on a news product, browser or device the company already runs?
  • Is success judged on reach and engagement first, or must the service make money (ads or subscriptions) from launch?
  • Which devices should it cover: phones and tablets only, or also TVs and smart speakers?

What a Strong Answer Covers Guidance

  • A segmentation of older news readers and a justified choice of target group
  • Pain points rooted in this audience: physical accessibility, overload and clutter, trust in sources, and exposure to scams or misinformation
  • A prioritized first version whose features map to the chosen pain points, with later phases sketched
  • A goal and success metrics centered on staying informed as a habit, with guardrails
  • Risks such as patronizing design, misinformation, publisher licensing and privacy in any family features

Follow-up Questions Guidance

  • How would you keep misinformation and scam-like content out of the service without making it feel censored?
  • An older reader's family wants to set up and keep an eye on the app for them. How far should that go, given the reader's privacy?
  • After launch, retention is strong but readers rarely open anything beyond the main daily view. Is that a problem?