Google Docs improvement: pick a user segment, find an unmet need, prioritize a fix
Company: Google
Role: Product Manager
Category: Product Design & Strategy
Difficulty: medium
Interview Round: Other
You are a product manager on Google Docs, Google's browser-based document editor. How would you make it better?
Pick the users you would focus on and the problem you would solve for them, explain what you would build first, and say how you would know it worked.
```hint Look past the core editor
Writing, formatting and real-time co-editing are mature in Docs. Look at what one group of users does before and after writing a document, and where they still leave Docs or work around it.
```
### Clarifying Questions
- Which users should the improvement serve first: people on free personal accounts, students and teachers, or teams on paid business plans?
- What is the goal: deeper engagement from current users, winning people who still prefer another word processor, or growth in paid business subscriptions?
- Is the scope the web editor only, or the mobile apps too, and are AI writing features in scope?
### What a Strong Answer Covers
- A goal for the improvement tied to why Google invests in Docs, and a reasoned choice of one user segment
- Pain points specific to that segment, checked against what Docs already does so the proposal is not an existing feature
- Several candidate solutions prioritized on impact and effort, with one recommended and scoped into a first version
- A primary success metric with supporting metrics and guardrails
- Risks and trade-offs, such as added complexity for casual users or notification overload
### Follow-up Questions
- How would your improvement work on a phone, where reading and editing long documents is harder?
- How would you show the feature made Docs more useful rather than shifting activity from another Google product?
- Early data shows only large companies adopt the feature and small teams ignore it. What do you do?
Overview: A product improvement exercise for Google Docs. The candidate chooses a user segment, identifies pain points the editor does not yet solve, proposes and prioritizes solutions, and defines a success metric with guardrails for the recommended improvement.