3 ms·
I think you’re getting bad answers here. It’s not just about talking to customers and understanding what they want, it’s about taking that and matching it again
by mdorazio 4y ago
I think you’re getting bad answers here. It’s not just about talking to customers and understanding what they want, it’s about taking that and matching it against bigger business goals, budgets, and priorities plus making sure you’re not duplicating or messing up things other teams are planning plus prioritizing within all the features all the customers want. If you have time to do all that then why is the company paying you an engineering salary to write code?
- shuckles 4y agoIf you’re doing all that, the company could be paying you staff engineer or senior manager salaries?
- ebiester 4y agoIt's not about being able to do all of it -- it's about being able to do it in a sustainable number of hours a week. Otherwise, you just have someone with the programmer title but actually doing PM work, and not doing it as well as someone who is specialized in the role.
- shuckles 4y agoThe arguments in the thread are that aligning the product as built and architected with the goals of the company is actually engineering work and not PM work.