Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This isn't a reactive problem resolution as you describe, it is a proactive endeavor. The tactic used could have been improved significantly, but the priority is very high for the CEO. There is a big difference in response from ignoring a lazy CEO/manager that jumps from fire to fire shouting, "This is the priority! This is the priority!" and one that wants to ensure his management team is focusing on employee contentment.


That's a false dilemma, and the CEO is the person who let it get to the point where the only option was to threaten to fire someone by surprise. I'm not sure how we can say that this was a high priority before Ben noticed it. Aren't the management team employees too?


A CEO can only act on information they have. Primarily directives are carried out by being followed down the chain. By not following something the CEO felt was important, the employee (manager is this case) is creating a problem. First they are ignoring desired direction. As a person in a management role, this basically means that they are not doing their job. Second, they are demonstrating that following direction doesn't matter. This was a serious issue for the CEO and it had to be dealt with.

The executive should have been made aware that this was an issue or fired, not threatened. That was a stupid move. If you have to threaten your employees, you have already failed as a leader.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

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

Search: