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

I mean it’s not unreasonable to think they needed those people then, but now they don’t. If you’ve got 40,000 people worth of work and 70,000 people some of them aren’t going to be productive. Just because you had 70,000 people worth of work last year doesn’t mean they’re still productive this year.


Then say that and don't blame employee laziness for poor planning.


I didn’t see them call the employees lazy. They said they weren’t productive. And again calling a conscious decision to hire people you won’t need in a couple years isn’t necessarily poor planning. If being the first to release a product gives you a big advantage it’s probably a good idea to hire all those people in the right situation.


If the employees were not being productive, that would show up in their KPIs and reviews and they would be fired. That process already exsists so you can't use it as a scapegoat. This is squarely about leadership's poor planning.




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

Search: