"Design a product for the elderly": model PM answer

Q: Design a product for the elderly.

Model PM answer for "design a product for the elderly." Segment selection, real JTBD, metrics with targets, and the 2026 data that kills the weak answer.

This question is not an accessibility exercise. Interviewers use it to find out whether you treat a massive, wealthy, underserved demographic as a real product opportunity or as a charity case that needs bigger fonts. The candidates who fail treat “elderly” as a monolith defined by disability. The candidates who pass pick a specific sub-segment, name an unmet job, and build toward a product that earns genuine use rather than grudging tolerance.

Why “elderly” is not a segment

“Elderly” covers a 30-year span with three meaningfully different design surfaces. Independent-active adults aged 60 to 75 still shop, travel, work part-time, and manage complex lives. Transitioning adults aged 70 to 80 are managing increasing health complexity but remain largely autonomous. Dependent adults aged 80-plus increasingly rely on others for daily tasks. The business model, the core job, and the right product differ completely across these groups. Designing for dependency when your user is still independent is not empathetic, it is condescending, and interviewers will name it.

Pick one segment and defend the choice. Not doing so is the clearest signal that you have not done the work.

What the 2026 data actually says

The outdated premise buried in most PM prep answers is that seniors cannot use smartphones. AARP’s 2026 Tech Trends report puts that to rest: 90% of adults 50-plus now own a smartphone, up from 55% in 2016. Adults 50-plus use an average of 14 digital services and 10 apps in any three-month window. 71% purchased technology in 2025, spending an average of $756 per year. The US population 65-plus is approximately 58 million and is the fastest-growing demographic in American history.

The real gap: 3 in 5 adults 50-plus say technology is not designed with their age in mind, despite owning and actively using it. That is the design problem. Not inability to use a phone. Not need for bigger buttons. The problem is that nothing proactively organizes the most consequential layer of their life.

AI adoption in this cohort is accelerating. AARP 2026 data shows AI usage among 50-plus nearly doubled in one year, from 18% in 2024 to 30% in 2025, with health being the leading use case. Telehealth went from 12% to 24% adoption among 65-plus between 2020 and 2023. These are not laggards.

The constraint is real but specific: 53% of adults 65-plus feel overwhelmed by new technology, and 31% cite fear of making mistakes as their top concern (WorldMetrics 2026). Internet use drops sharply after 75, from 89% among 65-to-74-year-olds to 58% among 75-plus. The 75-plus segment is materially different and more constrained.

Pick the sharpest segment

Independent-active seniors aged 65 to 78. Still living alone or with a partner, managing their own health, coordinating with adult children who live elsewhere, and navigating a growing stack of medications, appointments, and family messages with no system that ties it together.

Their top job is not “be safer” or “avoid isolation.” It is: stay independent longer without requiring constant check-ins from family, while managing health complexity that is genuinely increasing. The fear underneath that is not the fear of falling. It is the fear of losing autonomy, of being perceived as diminished, of a family member deciding it is time to “step in.”

A product that addresses that job has to earn use on dignity, not on need.

Structure a strong answer

strong

"I want to narrow the segment before I go anywhere else. 'Elderly' spans 30 years and at least three distinct design spaces. I'm going to focus on independent-active seniors aged 65 to 78, people who still manage their own lives and have no desire to use a 'senior product.' That framing matters because the business model and the core job are totally different for this group versus someone who is dependent on a caregiver.

The AARP 2026 data changes the premise of this question: 90% of adults 50-plus own a smartphone. The problem is not that they cannot use technology. 3 in 5 say tech is not designed with their age in mind, despite using it daily. The gap is not capability, it is organization and proactivity.

The job I want to solve: managing increasing health and coordination complexity without requiring behavior change or making the user feel singled out as old. Medications, appointments, family messages, and health status monitoring are all happening in fragments across their phone, their pharmacy, and their adult children's anxiety. Nothing ties them together. AI makes proactive assembly of that layer feasible; the question is whether a product makes it lovable.

The product concept: a health-and-connection companion, layered on the phone they already own, that passively monitors medication adherence via phone camera, proactively surfaces the one or two family messages worth a response today, and shares a daily status with family that is opt-in and dignity-preserving. The senior does not have to learn new behavior. The family gets peace of mind without calling three times a week. The product earns trust by working quietly.

Why this is lovable, not just usable: the senior stays independent longer. The family member stops worrying. The product never calls attention to age or decline. Those are the jobs that create genuine pull.

On viability: I price this to the adult child, not the senior. $12 to $15 per month for peace of mind is a different conversation than selling 'senior tech.' AARP data shows the 65-plus cohort spends $756 per year on technology already, but a family subscription framing avoids the stigma of a senior-specific product. Acquisition through healthcare providers and AARP partnerships mirrors the channel that drove telehealth from 12% to 24% adoption in three years, with digital health research showing provider endorsement is the strongest adoption facilitator for this group.

Success metrics: 30-day retention above 60% (typical health apps average 20%), medication adherence rate as a proxy outcome, and family-member NPS above 50. For V1 I would cut the daily status dashboard entirely and ship only the medication and family message surfaces, because adding tabs before earning trust is how you lose this user."

weak

"I'd design an app for seniors with large text, high contrast, a simple navigation, and voice control." This fails on every dimension. It describes an accessibility retrofit, not a product. It has no segment, no job, no business model, no metrics, and no opinion. It rests on the false 2026 premise that seniors cannot use technology, when 90% of adults 50-plus already own a smartphone and use 10 apps regularly. Interviewers call this "feature list thinking": the candidate lists modifications to an existing product rather than reasoning from a specific user's unmet need to a differentiated solution. The follow-up "how would you make this viable?" has no answer in this framing, because no one asked what the user was hiring the product to do.

The follow-up traps

Interviewers who like the initial answer will push on three things. First: “Now make it a business.” A candidate who designed an accessibility feature has no answer. A candidate who identified a job (independence and family peace of mind) can immediately name the payer (the adult child), the channel (healthcare providers), and the comparable adoption curve (telehealth). Second: “What happens when the user turns 80?” This is asking whether you understand segment drift. The 80-plus user needs a different product with a different model, and knowing that boundary is part of the answer. Third: “Why wouldn’t Apple or Google just build this?” This requires a real view on why the market has not moved, which is usually distribution and trust, not capability. Provider partnerships take time to build; the channel is not available to a first-party OS team in the same way.

Why this question catches candidates

The prompt sounds generous because “the elderly” feel like an easy empathy target. That is the trap. Candidates flood into accessible UI and stop. The interviewers who designed the question are checking whether you can hold two things at once: genuine empathy for the dignity and autonomy concerns of a 70-year-old who does not want to be treated as impaired, and clear-eyed business reasoning about why this is a large, underserved, commercially viable market. The candidates who do both get the offer. The candidates who nail empathy but have no business model, or who have a crisp GTM but no real understanding of the user’s core fear, do not.