Hierarchy is not only there for 'telling X to do ABC', but also to make clear who takes responsibility. If there's no leader, who's responsible for decisions taken? A random person who happens to be in a team who did something which turned out to be very stupid? All of them? No one? When a decision is made by X, the people who execute it didn't decide on it, X did, which means X takes responsibility, not the people who execute the decision.

Another aspect which is overlooked in the article is: to get things done, you have to make unpopular decisions sometimes: i.e. cut features to make a deadline, to ship a version, to stop adding stuff and work towards a release. No-one wants to make those, they're called 'unpopular' for a reason. But you have to make them to avoid a state where things aren't ready and never will be. There's a difference between 'being able to ship' and 'being able to ship a usable product'.

Funny that they refer to Valve with the text:

> At the video-game maker Valve, new employees are told not to expect instructions, because even the managing director “isn’t your manager,” says the employee handbook. “You have the power to green-light projects. You have the power to ship products.” And so they do.

I'd like to mention 'Half Life 3'. ;)