3 ms·
>> youre not here to decide what problems to solve, youre here to solve the problems the product team wants solved they get all upset and moody > Please be ver
by ryandrake 3y ago
>> youre not here to decide what problems to solve, youre here to solve the problems the product team wants solved they get all upset and moody
> Please be very up front that you hold this view when recruiting, it will be better for everyone. This may need to be an "agree to disagree" situation, but my experience goes completely the opposite direction of what you're suggesting here.
Also, there are both types of companies out there! There are places where "engineering" means "implement what the Product Manager dreams up" and other places where it means "you define the product and implementation." Find the company that works best for your expectations. Some people like having a PM do all the ideation and just sit back and program what's in the requirements doc. Others feel put in a box in that environment. Both types of companies exist.
- verelo 3y agoI beg to differ, well, at least i beg to add a 3rd option. I like to subscribe to the thinking that the PM owns the decision but the best outcomes are made when they work closely with, and often take a lot of input from, the developers. At the end of the day the reason i say i like this model is because i want ownership from a product group, and likewise no development team wants PMs prescribing to them how to structured the database or what language to choose. So ultimately, this division of responsibility is kind of a logical divide, to ensure we see where each other operates and let the developers have input but also their own area of ownership without taking away the ownership the product people bring to the table.