Diagnose why a product you personally value fails to spread among your friends
Company: Google
Role: Product Manager
Category: Product Design & Strategy
Difficulty: medium
Interview Round: Other
Pick a product that you genuinely love but have not managed to get a single one of your friends to start using. Describe the product and why it matters to you, explain why your friends have not adopted it, and say what, if anything, could change that.
```hint Need or friction?
Before listing reasons, decide whether your friends simply do not have the problem the product solves, or whether they have it but the cost of starting (effort, money, trust, changing a habit) outweighs the benefit they can see.
```
### Clarifying Questions
- Does the product need to be one you expect me to know, or is any product fine as long as I explain it first?
- Does "adopt" mean trying it once, or using it regularly the way I do?
- Should I answer only as a user, or also step into the role of the product's manager and suggest changes?
### What a Strong Answer Covers
- A specific product and a sharp description of the job it does for you, rather than a list of features.
- A diagnosis of why adoption stalls that separates your situation from your friends': need, setup effort, existing alternatives, price, trust, habits and network effects.
- Evidence from your own attempts to convert friends, and what their objections revealed.
- Concrete changes aimed at the main barrier, ranked, with a way to tell whether they work.
- Self-awareness that you may be an unusual user, and what that means for whom the product should target.
### Follow-up Questions
- If you were this product's PM, which one change would you ship first, and which metric would show it worked?
- Could the product be right not to target people like your friends? How would you decide?
- What did failing to convert your friends teach you about driving adoption of a product you build?
Overview: A Google product manager interview prompt asking candidates to describe a product they love that none of their friends have adopted. It tests explaining the product's value, diagnosing adoption barriers such as setup effort, trust, existing alternatives and network effects, and proposing targeted changes with a way to measure them.