Reasons to hate and/or love Product managers | Hacker News Reader

Reasons to hate and/or love Product managers

9 pointsrokkk5 comments

Honest question, based on your experience as an engineer, tester, etc. I would like to know examples of what was helpful and what was not. I'm preparing a workshop for product folks on this topic.

View on HN

Product management is why I’ve moved away from engineering and into startup building.

All of the fun work has been getting siphoned from engineers and put into PMs hands.

Software engineering now me feels like I’m an assembly line worker moving my tickets along the track. My value is based on how many widgets I produce.

Generally the sequence is something like product research, product ideation, then product development where engineering gets involved. Engineering is quite aware of the impedance mismatches that can occur and try to voice them as soon as they become aware of them.

The best advice I can give is for product managers to be aware that products are not produced in a vacuum and to get input/validation from engineers on feasibility or other possibilities and iterate. This applies to everyone except say Apple where they can re-invent everything all the way down the supply chain.

I think the product manager is key in a startup; for developers their principle role is to act as a buffer between development and sales/management, working out what's feasible, what's desirable. A good product manager makes a startup a nice place for developers to work, by giving them some space to do that work.

Disclosure, I've never been a product manager, but I have benefited from good ones.

I think in larger companies it becomes even more critical for a PM to shield the development team from ad-hoc sales/marketing requests. It's not that anyone is ill intentioned, but everyone tends to think the problem in front of them is the most critical, and may not be aware of everything else that's going on. A PM will hear any request, know the context of the request as well as the context of what the dev team is working on, and manage the expectations of the stakeholders if necessary. In a small startup, I would actually expect that this part of Product Management would be less important, since it's more likely that stakeholders are more aware of everything going on. In large companies, I think it would be crucial for keeping the development team happy & productive.

1) low IQ 2) pushing garbage low value features that pile tech debt because their job is to push features.

Reply on news.ycombinator.com