2 ms·
In every team I've observed, there has been a steady stream of comments from staff about how one manager or other keeps asking for changes they see as pointless
by vidarh 10y ago
In every team I've observed, there has been a steady stream of comments from staff about how one manager or other keeps asking for changes they see as pointless or negative, often accompanied by further complaints about how the manager in question never thinks their work is good enough.
I've seen this be the primary reason for high performing team members quitting. I think you underestimate substantially how much negative feelings this type of thing can produce.
It's not that you can never make suggestions. It's about making sure that you don't always make suggestions, and to avoid making suggestions unless the change you're asking for is important enough.
It's also not about people not being able to "handle a little nitpicking" but that even though they'll handle it, it often creates resentment and feelings of not being appreciated. And the team members that takes the most pride in their work are often most likely to be annoyed by this, and most likely to have plenty of options to move on.
Constantly giving people feedback that says "your work wasn't good enough for me as is" does not build trust. If you want to demonstrate that you trust their judgement, then do that by letting their judgement stand.
- deleted 10y ago[deleted]
- ojosilva 10y ago> Constantly giving people feedback that says "your work wasn't good enough for me as is" That's what I mean by giving reasonable feedback. Constantly being a dick is definitely counterproductive. > resentment and feelings of not being appreciated That is a symptom of a broken framework for managing a team, not a result of giving natural, reasonable feedback to the output of a person.
- vidarh 10y ago> That's what I mean by giving reasonable feedback. Constantly being a dick is definitely counterproductive. But it's not about being a dick. The point is that even feedback that is totally reasonable in isolation sends all the wrong signals if they become a constant factor. By restraining yourself to asking for changes when there are actual, important reasons for them you minimise that. As a bonus, when it is clear that the changes you ask for are actually important, people tend to take them a lot more seriously. > That is a symptom of a broken framework for managing a team, not a result of giving natural, reasonable feedback to the output of a person. I agree with this, with the caveat of what I have written above: If you have to give constant suggestions for change once someone comes to you with something they believe is ready, I don't see that as reasonable, no matter how reasonable each individual piece of feedback is. I believe that in that case, either the suggestions aren't all necessary, or if they are necessary the team is badly managed as the staff clearly does not understand what areas they need to collect feedback on during the process, and don't understand when the work is actually complete and/or doesn't have access to the necessary skills and resources. Note that there is also a clear difference between someone coming to you and asking for feedback or asking you to make a choice or suggestion during execution of a task vs. you giving unsolicited suggestions for changes when they come to you with what they believe is a finished piece of work. The former is generally, if given well, welcomed and appreciated in my experience. It is the latter which often produces negative responses.