Individual To-Do App Product Design: Segment, Features and Success Metrics
Company: Microsoft
Role: Product Manager
Category: Product Design & Strategy
Difficulty: medium
Interview Round: Other
Design a to-do app that helps one person manage their own tasks. Decide who it is for and what problems it solves, choose the features that come first, and explain how you would measure success.
```hint Ask why lists get abandoned
Most people have tried a to-do app and quit. Look for where the habit breaks, from getting a task in to actually finishing it, before listing features.
```
### Clarifying Questions
- Does "personal" cover one person's work and home tasks together, or only life outside work, such as errands, bills and appointments?
- Is this a new standalone app or part of an existing productivity suite, and may it connect to the user's email and calendar?
- Is the main goal user growth in a crowded category, paid subscriptions, or engagement that supports a wider ecosystem?
- Is the first release mobile only, or should desktop and voice assistants be included?
### What a Strong Answer Covers
- A clear goal and target segment, chosen with the crowded, free-alternative market in mind
- Pain points across the task life cycle: capture, prioritizing, reminders, finishing and lists that decay
- A differentiated, prioritized feature set with a lean first release rather than a catalog of standard to-do features
- Success metrics centered on tasks finished and lasting habits, with guardrails such as notification opt-outs
- A monetization approach and risks such as over-automation and the privacy of connected accounts
### Follow-up Questions
- Users add many tasks but finish few. How would you tell whether the product or the users' planning is at fault?
- Every phone ships a free reminders app. Why would someone switch, and how would you test that reason early?
- Which features would you charge for, and which must stay free?
Overview: A product design interview question asking for a to-do and task management app that individuals use to manage their own tasks. It tests choosing a segment in a crowded category, finding why task lists get abandoned, prioritizing a focused feature set, and defining success metrics and monetization.