At Meta, PMs used to brag about how many engineers they worked with. But a PM-to-engineer ratio does not measure a PM’s talent, bandwidth, or importance. It measures the organization around the PM. One PM supporting 30 engineers might have a founder setting clear strategy and partners who stay close to customers and help define the product. Another might be an exhausted ticket writer supporting a team that builds whatever the loudest voice requests.
AI makes that distinction more consequential. As building gets faster and cheaper, judgment, strategy, and a deep understanding of customers matter more. The work of deciding what deserves to ship, protecting quality, and owning outcomes has to happen consistently, wherever it lives in the organization.
What this essay explores
- Read the PM-to-engineer ratio as a clue about where product work lives.
- Distinguish a culture that shares product thinking from one that leaves PMs writing tickets while discovery and strategy slip away.
- Use the 12 competencies to see which product activities need accountable owners and capable partners.
- Make the division of labor explicit across engineering, design, research, data, and business teams.
- Judge which ideas deserve to ship as AI makes building faster and cheaper.
The competencies map the work a product organization must do and the people who can help carry it.
Key takeaway
Product managers may be optional — but only if the rest of your company is ready to do the work. Product management is not.
