3 ms·
This article mischaracterizes the roles of PM's and engineers in most companies. It sets up a strawman of "delegating control to a single person", and assuming
by crazygringo 3y ago
This article mischaracterizes the roles of PM's and engineers in most companies.
It sets up a strawman of "delegating control to a single person", and assuming that person is either an engineer or a PM. Everywhere I've worked, the product teams/leaders and engineering teams/leaders were peers. Engineering didn't report to product, and product didn't report to engineering. Rather, both reported directly to the CEO, often as separate CTO and CPO heads, or they both reported to an executive VP or director or similar.
Because the reality is, you need both. Engineers are great at building but they're not spending time with customers or UX research to know what the market and users need. The main job of a PM is to understand what the market and users need by spending a lot of time with customers and researchers, and to marry that with the business priorities coming from executives. And then a PM and eng lead negotiate back and forth to figure out what can be built that meets everyone's needs.
The idea that a product manager role is a mistake makes as much sense as saying an engineering lead role is a mistake, or a sales lead is a mistake, or a marketing manager is a mistake. A successful business needs all parts.
(Occasionally you're building a product that's by developers for developers, where the engineers do have an accurate understanding of users/market, and a PM isn't necessary. But that's exceedingly rare.)