How would you design a product org for a company scaling from 50 to 200 people?
Model answer
Model answerAt 50 people, everyone knows everything and coordination is informal. At 200, informal breaks down. The design principle: structure the org around the product architecture, not the other way around. If you have three core product areas, consider three pods. The trap is creating too many PM roles too fast — better to have fewer, stronger PMs than many weak ones. I'd also invest early in a central product operations function to handle process that would otherwise fragment.
Framework · Platform Strategy
- PProduct architecture first
Org structure should mirror product structure — Conway's Law is real - SSpan of control
1 PM per 5–8 engineers is sustainable. Below that, PMs become project managers - CCentral vs embedded
Design, data, and research: centralized early, embedded as you scale - GGovernance early
Define decision rights before you need them — ambiguity at 200 people is expensive
Related questions
- How would you decide whether to enter the European market?
- How would you build the case for a multi-year product investment that won't show ROI for 18 months?
- How do you set product strategy when the CEO keeps changing their mind?
- How would you approach building a product in a regulated industry (fintech, health, etc.)?
- How do you build organizational buy-in for a product strategy that leadership is skeptical of?