Sometimes a team should just collectively say "No" to a PM. And not in a "you are a moron"-way, but in a "this is not how it is done in the trade"-way.
Bonus points when you build him a excel exporter for github issues.
Simply saying "No" and not understanding another's view point is a missed opertunity. Intuition of process or technology "XYZ" is not the same for everyone. Understanding how to guide Users to a more efficent workflow is half the battle.
Comments
Sometimes a team should just collectively say "No" to a PM. And not in a "you are a moron"-way, but in a "this is not how it is done in the trade"-way.
Bonus points when you build him a excel exporter for github issues.
Simply saying "No" and not understanding another's view point is a missed opertunity. Intuition of process or technology "XYZ" is not the same for everyone. Understanding how to guide Users to a more efficent workflow is half the battle.
more like "no, this is making us all suffer except you" kind of way
Words of wisdom!