Too often, the response to perceiving someones incompetence is the perceiver shutting down, instead of taking a rising-tide-raises-all-boats attitude. I'ts a cultural failure to keep people that only try and make people (they self select as competent) better.
In the case of the op story. It was clear management, maybe the business, not technical leadership, asked for a new product. Saying "our old product does that" is missing the forest for the trees. It's evaluating the idea too quickly. It's rowing upstream, when they are asking everyone else to row down. When they are looking for momentum, and the details come later, that person can derail the process. The reason they started working in secret, where everybody in the company but op knew, is that op was disruptive to the culture of trying. They were too pragmatic, too literal, too technical. Sit down, listen to what management is asking for, then go work on a pitch, where your delivery is "we can deliver what you are asking for (and also reuse most of our old work, saving you time and money!) Be on their team, not in opposition to it.
Replace but with yes, and at the beginning of sentences.
Companies need a few skeptics around to put the brakes on crazy ideas. I’ve seen far more half-baked money pit projects than risks that paid off in my career. In tech in general there is way too much optimism and ignoring inconvenient facts/constraints until disaster is clear. Someone who can EFFECTIVELY steer teams away from horrible decisions is worth their weight in gold.
In the OP’s case, he simply couldn’t effectively communicate this, and failed to notice the rampant nepotism up his management chain, but his heart was in the right place.
Absolutely. And not just crazy ideas, but maybe we'll intended ideas that are misaligned with each other or the overall goals and strategic roadmap. Too many autonomous silos that are all high functioning tend to not like a skeptic saying, "this is great in isolation but the sum of these parts don't fit coherently." They also don't like "this works, but it's an MVP at best, and isn't sustainable." Skeptics cognizant of technical debt, may meet unwelcomness in an org not willing to acknowledge it.
Don't blame the subordinate calling foul for being "too pragmatic". That's not how hierarchical management works.
Frankly, as someone who leads a team myself, yeah I've had to take colleagues aside and say "this isn't how we do things" but I certainly wouldn't just bin their entire point without consideration to save "face."
Up to a certain point, of course. But all this talk of how to deliver information so the recipient feels nice about receiving bad feedback (shit sandwiches and such) shouldn't matter.
Nothing at all to do with feelings.
This is entirely possible but in the case of OP, and in the larger scope, it's irrelevant. If you have a product manager, for example, who's job it is to oversee the development of a product, they can be the best damn communicator, they could be the nicest person, they could be financially minded and have great marketing skills, they could have excellent personal hygiene and be fantastic husbands. All of that means precisely nothing if they are so bad at managing the product that they cannot deliver that product. I'm not saying that everybody like OP's boss here should be fired, per se, there's probably a place in the organization for them. But once they become entrenched in a place they don't belong in the organization, again, it's cancer. And it's fatal.
> Too often, the response to perceiving someones incompetence is the perceiver shutting down, instead of taking a rising-tide-raises-all-boats attitude.
Except this assumes a rising tide. If the tide falls, perhaps because your captain is not good at gauging tides, you're beached.
> It was clear management, maybe the business, not technical leadership, asked for a new product. Saying "our old product does that" is missing the forest for the trees.
Or it's recognizing that the problem management is trying to solve has already been solved. This can mean one of many things, but the two that spring immediately to mind is that a competitor (or competitors) have already solved this problem, and that management just wants a slice of that pie too, failing to consider that simply offering isn't enough, you need to have a differentiator. See, for example, all the game developers who chased the various trends like Battle Royale, and before that Military Shooters, and before that MMO's, and all the failed businesses that those trends left in their wake. Alternately, and this seems to be the situation where OP was, their own business had already solved this need; this is a good place to be, and wanting to increase revenue by providing a new product is a damn hard, borderline arcana level task to do without either A) alienating existing customers or B) cannibalizing the users of an existing product.
I don't think management is by default full of shit, and must prove themselves wrong. That said, I have never seen a healthy business that stays afloat long term where the response to criticism of decisions being made is to simply ostracize employees. If I have questions you're damn right I'm going to ask them, and I want answers commensurate with a level of respect that I'm sure my given boss would expect from me. And if your answer is to out me as a nonbeliever, I'm sending out resumes. I have no interest in finding out how this place is going down.
100% agree with that line. If negative upward feedback is a dead end or met with retribution, an organizations communication structure and culture is broken.
The choices, as I see them: own responsibility for making sure the recipient understands our communications. If they don't, that's on me. If they do, but don't do what I want... I can either accept their decision or move on.
I know changing jobs is hard, but all I can control is to communicate better (differently! and with compassion/empathy!) or leave.
What we need is more training and culture around feedback at work.
Our upper management is incompetent because they are so removed from what we actually do, and show no interest in learning about it.
But my immediate manager is very far from incompetent.
I'm not sure I agree with having the technical guy be the personal manager, but when they only have a couple direct reports a good percentage seem be able to herd the cats semi competently.
That isn't to say there aren't plenty of disasters, but when it works, it works fairly well. I guess you just have to be willing to throw away some of your best technical people when it turns out they don't make good managers, or they turn into just another layer of middle mgmt that needs to be cut in a few years.
My team, boss included, is one of few reasons keeping me at this company.
These people are like a cancer, and just like a cancer, as their influence grows and their power grows, the patient, the business, suffers. Sometimes businesses can last years, decades, with a number of these tumors if they're controlled, or if the business is just so healthy that it can take the strain they put upon it. But in my mind, as soon as competence takes a back seat to who you know, as soon as that line is crossed by any member of the company leadership, then that's the end. It's not a matter of if, it's a matter of when.
And this one I don't know how to solve. Were I a C level executive in a company, I'd constantly have my eyes out for this kind of shit, and excise it as soon as I could. But it seems most C-levels don't care all that much. Maybe I wouldn't if I was at that level.