3 ms·

I think you're missing the point. The point here is that some PMs feel that if they're not demanding changes, they are not necessary / not doing their job / e

I think you're missing the point. The point here is that some PMs feel that if they're not demanding changes, they are not necessary / not doing their job / etc. If there's nothing wrong with the completed work, such a PM will demand unnecessary changes, in order to justify themselves. The duck is a passive counter to the PM's pathological behaviour: ensure there's always some easily-fixed fault, so the PM can feel like they're doing something, without forcing unnecessary high-effort changes. Since the duck is obviously bad and easily removed, it shouldn't prevent the PM from noticing real issues, or detract from fixing real issues. If you feel the need to add ducks, the real problem is that you have a bad PM. But if you're a dev and have no good way to solve the real problem...

Elepsis 12y ago
The problem is that it's not uncommon for a dev/designer/etc. to not understand some of the reasoning for why a PM is requesting changes be made. We all snicker at the incompetent PM who just wants to "make their mark" on a project, but very often the demand that may appear that way is motivated by entirely legitimate concerns. (And yes, the PM should bring the dev along with them, etc.) If you "add a duck" and the PM ends up missing the legitimate concerns as a result, everyone loses. The add-a-duck attitude fundamentally assumes that the dev/designer knows what's best for the end product and the customer, and while that happens some of the time, the reason the PM role exists in the first place is because that's not always true. :)
snowwrestler 12y ago
> The point here is that some PMs feel that if they're not demanding changes, they are not necessary / not doing their job / etc. If there's nothing wrong with the completed work, such a PM will demand unnecessary changes, in order to justify themselves. Is that the point? Or is the point that some developers/designers don't like to get edited, so they tell themselves that their PM is pathological? There's more than one valid perspective on things, and in my experience professional relationships work better when everyone realizes that. edit: spelling

Elepsis 12y ago

The problem is that it's not uncommon for a dev/designer/etc. to not understand some of the reasoning for why a PM is requesting changes be made. We all snicker at the incompetent PM who just wants to "make their mark" on a project, but very often the demand that may appear that way is motivated by entirely legitimate concerns. (And yes, the PM should bring the dev along with them, etc.) If you "add a duck" and the PM ends up missing the legitimate concerns as a result, everyone loses. The add-a-duck attitude fundamentally assumes that the dev/designer knows what's best for the end product and the customer, and while that happens some of the time, the reason the PM role exists in the first place is because that's not always true. :)

snowwrestler 12y ago

> The point here is that some PMs feel that if they're not demanding changes, they are not necessary / not doing their job / etc. If there's nothing wrong with the completed work, such a PM will demand unnecessary changes, in order to justify themselves. Is that the point? Or is the point that some developers/designers don't like to get edited, so they tell themselves that their PM is pathological? There's more than one valid perspective on things, and in my experience professional relationships work better when everyone realizes that. edit: spelling