Getting enterprise users to adopt Google Docs version history instead of file copies
Company: Google
Role: Product Manager
Category: Product Design & Strategy
Difficulty: medium
Interview Round: Other
You are a product manager on Google Docs. Among enterprise customers, fewer than 10% of users use the version control feature in Docs. An analysis of the Google Drive contents of 10,000 enterprise users found two patterns:
- More than half of the documents had near-duplicate names with version information in the file name, for example "case study V1.0" stored alongside "case study V1.1".
- 40% of the documents existed both as a Docs file and as a PDF with very similar content, which suggests the user exported a PDF copy at some point.
How would you increase adoption of version control among enterprise users?
```hint Read the workarounds as requirements
Each pattern in the analysis is a job users are already doing by hand. Work out what each copy and each PDF is for before deciding what to build or promote.
```
### Clarifying Questions
- What counts as using version control in the under-10% figure: opening the version history, naming a version, or restoring one?
- Were the version-labelled copies and PDFs created by the document owners themselves, or does the analysis include files received from others and saved to Drive?
- Is adoption the goal in itself, or a means to an outcome such as fewer duplicate files or fewer mistakes from people working on an outdated copy?
- Can the solution change Drive and Workspace admin settings, or only the Docs editor?
### What a Strong Answer Covers
- A diagnosis of low adoption that uses both findings, including the needs behind version-labelled copies and PDF exports.
- A segmentation of enterprise users and document workflows, with a reasoned choice of focus.
- Prioritized solutions that meet users inside the behaviors they already have, not only campaigns that promote the feature.
- A precise adoption metric with guardrails, and an experiment design that accounts for documents shared between co-editors.
- Risks such as nudge fatigue, fear of losing work, compliance needs and PDF uses a native version cannot replace.
### Follow-up Questions
- After launch, named versions rise sharply but copies with version labels in their names barely fall. What would you conclude, and what would you do next?
- How would you run an A/B test when the people editing the same document could land in different test groups?
- Should Docs ever offer to merge a family of copied files into one document with its history? What would make that safe?
Overview: A product adoption case for Google Docs: under 10% of enterprise users use version control, while Drive data shows widespread version-labelled file copies and PDF duplicates. It tests reading user workarounds as needs, segmenting enterprise workflows, prioritizing in-flow solutions, and defining adoption metrics and experiments.