Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try !politicaldiscussion@lemmy.world
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
I mean questioning as in second-guessing the people who actually know stuff. Not asking experts for their honest thoughts.
Management is one thing - C-levels is yet another kettle of fish.
In my experience C-levels rarely want the technical answer to a question, and will be personally insulted / defensive if the answer is something they don't understand. And they will ask their questions in such a way as to insult the expert. Two negative results that don't help the business in any way.
But Dept heads and the PM office will often be able to explain why certain choices were made, and how that aligns with the business needs, without the complexities that cause misunderstanding between two people of such wildly divergent skillsets.
Now if the CEO can also write the code, or run the wetlab instruments, and really does want the nitty-gritty, complex technical answer, that is a different story. And rarely the case in my career.
A C-suite executive isn't making decisions from a technical point of view. They have to balance their decisions across the counsel of several experts in their fields to choose the best option, with those recommendations constantly in conflict.
A C-suite executive is likely going to focus more on the impacts of the decision made, which can be a far different conversation than a technical expert is used to having.
I think we agree. CEO should not be making decisions from a technical point of view, so they should not be second-guessing the technical people.
I'm at the stage of my career that pretty much every job I take, I report directly to the CEO. And the difference between what they should do and what they actually do is why I made my statement at the top of this thread.