|
|
|
|
|
by siruncledrew
2192 days ago
|
|
There's this tendency, particularly in U.S. management, to put off bad news as long as possible and then try to avoid acknowledging the bad news during a generic-sounding announcement like a third-party wrote it. I think it's better to announce the bad news on the horizon before it arrives - if possible. People are more likely to find solutions to problems when the problem are laid out. If the CEO comes out and says, "Our Q1 numbers really plummeted in 2020, and we need to innovate if we want to make it past Q3 intact", then sure it will get reactions of "I should update my CV", but it also gets people in the problem-solving mindset and willing to put in effort if they have a stake in the outcome. As opposed to delivering the bad news when nothing left can be done, at which point it seems like all the recent work was in vain, and people are 'slapped in the face' with the news. Saying "This ship's sailing great! ... as long as we throw half the crew overboard" isn't the most motivating speech. -
On an aside: This also relates to the "announcer's" personal skills as a leader/manager. Some people hate giving bad news because they think it means they will be negatively received, and some leaders/managers are just very bad at taking criticism. It's a tough job, but it comes with the territory, and denying bad news is a reality is just "blissful ignorance". |
|
My experience with bad news especially is that too many managers have linked their self worth to their company's success and so bad news equates to them being bad and thus avoided.
I was remarkably fortunate to take a job at Intel as my first job out of college during the Andy Grove years. While there are arguments to made on the pluses and minuses of "constructive criticism", the leadership culture under Andy was that problems were there to provide something for the rest of us to work on. When they came up they got pounced on as they were often how people were measured in their reviews.
I did not realize at the time this was different than other companies in the valley. Intel focused on the people who saw the problems, came up with solutions or workarounds, and kept moving. As opposed to the people who "simply" delivered their milestones on time.
It was much later in my career when I found myself in a company that was actively ignoring problems. That struck me as so foreign I had a hard time dealing with it.