Ask HN: Developers, what have you learned from product managers?

6 points by eadz 3 years ago | 6 comments

How has it changed what you do at work or on side projects?

mikewarot 3 years ago |

I learned a ton about users, and what they need, in the real world, back in the 1980s from Russ Reynolds at Will County Generating Station. He would pull a random worker at the floor of the generating station, explain very carefully that he didn't expect them to be a computer expert, and that I would be responsible if there were any problems... gave them a set of tasks to accomplish, and told me to quietly watch.

First day, first time... the user didn't know to press F1 for help... I made sure it was ALWAYS on the screen after that (back in the days of MS-DOS). One time he asked "what happens if we disconnect right now?", the next week and forever after, it was immune to data loss if there was a disconnect.

The main thing I learned is that people are doing a job, your software is just a tool, and it should make it as easy as possible for them to keep doing it.

Oh... and never have them type data more than once.

tooltitude 3 years ago |

I learned how to have indirect impact. I.e. product managers usually have no authority to make people do something. Engineers, Designers, and other specialists don't report to them. However, they need to persuade people to do something. It was very useful example at work, but have no substantial effect on side projects.

digitalpacman 3 years ago |

Nothing. They are generally always a waste of space and time.

throwawaysalome 3 years ago |

I learned everything from Peter Gibbons. The key is to slip in through the side door to avoid being buttonholed, and to leave 10 minutes early on Friday, so they can't ask you to come in over the weekend.

dimmke 3 years ago |

It’s the most useless job in tech and the fact that it even exists is insulting to developers

dimmke 3 years ago | |

I did want to clarify since this is under my real name, to me product managers are similar to project managers. 80% of them are useless- they don’t make the process of building software easier and don’t make the end result better (by whatever metrics you quantify “better”) but there is 20% that are worth their weight in gold.

My main issue is that decisions about features software should have shouldn’t be delegated to a specific role. That’s absurd. I’ve never seen a situation where this works. Because a product owner can be misaligned with executive level and their specifications for new requirements are always lacking.

But because of the way the industry works I could probably see myself taking on such a role someday as it seems to be one of the paths away from being a direct IC programmer into something more.