Because it is meant as an offense. It is designed to make it plain that our input is not welcome.
The whole idea is to belittle someone else, and stop them from coming to you, with their ideas.
To be fair, there are people who get waaaaayyyy too obsessed with "not a problems." I have worked with many of them, over the years. In fact, I just got off a video call with one that suggested that we scrap our entire, near-ship-ready app, because we are not sure how well it will scale for millions of users, and it is highly doubtful that it will have more than a few thousand users, for the next three or four years.
This is an app that has been under development for two years, and is looking very good.
I completely understand why what I said to Marketing was not received well. Part of it was practicality. Changing course is difficult, expensive, and risky. Even a high-level person would be crazy to do it on a whim.
But the bigger part was ego. I know the people involved. In this community, tecchies are valued and listened to, but, if you are a small, technical team, in a marketing/sales/service company, you get used to being treated like Moss and Roy.
What is a good idea, though, is to evaluate who is bringing the news, and what it would take to start examining the issue. If my company had done that, then they would have been well-prepared.
That's something that many companies are spectacularly bad at.
Instead, they stuck their fingers in their ears, and sang "La-la-la-I-can't-hear-you."
The whole idea is to belittle someone else, and stop them from coming to you, with their ideas.
To be fair, there are people who get waaaaayyyy too obsessed with "not a problems." I have worked with many of them, over the years. In fact, I just got off a video call with one that suggested that we scrap our entire, near-ship-ready app, because we are not sure how well it will scale for millions of users, and it is highly doubtful that it will have more than a few thousand users, for the next three or four years.
This is an app that has been under development for two years, and is looking very good.
I completely understand why what I said to Marketing was not received well. Part of it was practicality. Changing course is difficult, expensive, and risky. Even a high-level person would be crazy to do it on a whim.
But the bigger part was ego. I know the people involved. In this community, tecchies are valued and listened to, but, if you are a small, technical team, in a marketing/sales/service company, you get used to being treated like Moss and Roy.
What is a good idea, though, is to evaluate who is bringing the news, and what it would take to start examining the issue. If my company had done that, then they would have been well-prepared.
That's something that many companies are spectacularly bad at.
Instead, they stuck their fingers in their ears, and sang "La-la-la-I-can't-hear-you."