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

> He simply can't say he was getting information from a small number of direct underlings - he should have been in the trenches talking to the developers, testers and beta users and getting feedback directly.

True enough, but my point is that there is a bigger problem: He ran an org in which nobody tackled him in the hallway and said "WTF This is a piece of crap! We can't release such a POS, and if you do I quit!"

An organization is not fixed by chopping only one head, there are no doubt lieutenants that need to be axed.



He ran an org in which nobody tackled him in the hallway

Do you know that they didn't? And there is a lot of gray area between tackling and release that a good manager should be able to dive into.


> Do you know that they didn't?

I know that they either didn't tell him, or didn't tell him in a manner that he listened.

It's really not rocket science: An organization is not fixed by chopping only one head.


Clearly, removing everyone involved in failure is the route to success.


Try seeing at least one shade of gray, you'll go farther.


Wait how do you know he wasn't told this?




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: