4 ms·
Trying to make it more like a checklist: * Do the developers know what the customers want? * Do the customers have realistic expectations? If yes to both, th
by qznc 1y ago
Trying to make it more like a checklist:
* Do the developers know what the customers want?
* Do the customers have realistic expectations?
If yes to both, then the PM in between is doing a good job. Bonus points if higher management is aware of that.
- NickC25 1y agoExactly. A good PM should effectively get out in front of the sales team to make sure customers/users feel heard and understood, and also to communicate to the customers/users what is and isn't possible within a given period of time. A good PM should also know how to communicate a "no" to anyone in the business cycle from anyone else in the business cycle. Their job is effectively to be the firewall/filter from one team to another. No, customers don't want Feature XYZ even though engineering wants to build it No, engineering can't build Feature ABC even if a customer wants it No, sales cannot promise Feature 123 to customer, especially without checking with engineering first. No, executives can't force engineering to focus on the CMO's pet project, or force sales to hit numbers if the product sucks or isn't what the market wants And so on