Why not consult the people who actually know their stuff?
I mean questioning as in second-guessing the people who actually know stuff. Not asking experts for their honest thoughts.
Don’t you think that management could use your help and advice to make good strategic decisions in the long term?
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.
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.