Polyrepo
Multiple repositories per project/service.
- Term
- Polyrepo
- Field
- Product Management
- Category
- Growth & Lifecycle
What the term covers
Multiple repositories per project/service.
In product management, this concept guides how products are scoped, prioritized, built, measured, and iterated. It typically affects roadmap decisions, feature trade-offs, and definitions of success.
Polyrepo is a growth & lifecycle term for a lifecycle concept. Agree the scope and two people stop talking past each other.
The mechanics
Polyrepo behaves unlike a fixed rule. An early-stage brand and a mature one will apply Polyrepo on different terms. The mechanics follow the inputs around it. Treat Polyrepo as a buzzword and the reporting misleads; agree on it and the numbers hold.
The working rule is plain. Agree what Polyrepo covers first, then act on it. Skip that order and Polyrepo loses its shared meaning, and two teams end up measuring two different things. Start here.
Where it shows up
Polyrepo matters at the point of a decision. In growth & lifecycle, three moments come up again and again. Outside them, Polyrepo is reference material.
- Setting budget. Polyrepo helps decide which channel gets the next dollar.
- Choosing a metric. Polyrepo flags whether the number you report is causal.
- Comparing options. Polyrepo adjusts a compare so the gap is honest.
Worked example
Look at Duolingo. In a streak-driven retention loop, Polyrepo drove the decision rather than sitting in a footnote. A baseline came first, then a single agreed meaning of Polyrepo, then the read: D30 retention improved 14 points.
| Stage | The step taken | Why it mattered |
|---|---|---|
| Baseline | Took a before reading on Polyrepo. | A reference to judge against. |
| Define | Fixed one meaning of Polyrepo for the test. | No room for scope drift. |
| Act | A streak-driven retention loop — one variable. | One change, a clean read. |
| Result | D30 retention improved 14 points | An outcome you can trust. |
These Polyrepo numbers are illustrative -- RGM analysis. The structure travels; the specific figures do not.
Pitfalls in practice
- One blanket rule. Applying Polyrepo the same way everywhere. Split it by audience, channel, and business model.
- Bare numbers. Showing Polyrepo on its own. Context is what makes it readable.
- Wrong target. Treating Polyrepo as the goal. The goal is the outcome it predicts.
- Raw benchmarks. Stacking Polyrepo against rivals blind. Normalize for margin, pricing, and sales cycle.
Frequently asked questions
What is Polyrepo?
Why does Polyrepo matter?
How is Polyrepo used in practice?
What is the most common mistake with Polyrepo?
- What is Polyrepo?
- Multiple repositories per project/service. Agree the scope of Polyrepo before the planning starts.
- Why does Polyrepo matter?
- Polyrepo earns its place when it shapes a real decision. The leverage is in correct use, not in the word itself.
- How is Polyrepo used in practice?
- Teams put Polyrepo to work on a spend split, a metric, or a head-to-head call. See the Duolingo walk-through above.