Hacker News new | past | comments | ask | show | jobs | submit login

100% yes.

Fundamentally, the C-level/senior executives are rarely connected with what's actually going at the ground level. And IME a lot of them simply don't care. They make decisions without understanding the impacts to the rest of the organization, and when objections or concerns are raised, they're filtered or attenuated at the middle management layer (due, usually, to a culture of fear) or dismissed at the top levels.

Put another way: When the decision makers don't feel the consequences of their decisions, those consequences will be ignored. It's a kind of corporate negative externality.




> dismissed at the top levels.

The issue, IMO, is the only accountability C levels face is from either a board or stock prices. Otherwise, nothing they do has any real impact on them personally.

Another major problem is the effects of their decisions are long delayed. Do something that slows development to a crawl and you still have a functional product for years (even if you can't add new features to it). Tying the original decision to the impact on the org is hard, and even harder since whoever made that decision isn't likely to want to take responsibility for it.


From my management experience the leaders are actually doing their job when they do this. Leaders at that level are expected to make strong decisions and to stick with them. It is thought better to have a leader make the wrong decisions firmly and adjust later with a well planned change than the business wobling down the road. So the senior executives are actually doing what the board expects/tasked them to do, keep the direction stable until the next planned/controlled correction. That is why it feels like you are talking to a wall. You are. What you see as a 'bug' the board sees as a 'feature' and the expected output of a C-level.

Bad analogy (I'm old) the light at the intersection is going to stay red until it is time to turn green, even though it would make more sense right now for it to turn green for you because you are the only one at the intersection. Bigger picture, having the lights on timers works better than everyone having a stop sign, even though it looks/feels stupid waiting at a red light with no one else there. The lights seem stupid sometimes, but it scales better than a bunch of stop and go stop signs. (Yes, I know that now lights have sensors, bad analogy now like I said).

TLDR; What if it's not a bug, but it's actually the output the board wants.


That's a misunderstanding.

What should be kept stable are the goals the company wants to reach, not the details in execution.

When you notice your navigation app is sending you down a cliff, do you still follow that route? Of course not.

It's the same with organizations, except a lot of organizations are not intelligent and agile enough to course-correct. Just imagine what they could accomplish with better leadership.


> When you notice your navigation app is sending you down a cliff, do you still follow that route? Of course not.

Good point. A person or organization has to be careful about blindly following or being blind to the situation they are in.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: