I was a Sr Manager for about 4 years, two different "teams", one IT based, one QA based. Regardless, perhaps we need to define the word "Manager", mainly becaus

I was a Sr Manager for about 4 years, two different "teams", one IT based, one QA based. Regardless, perhaps we need to define the word "Manager", mainly because your example said: > Creating entire new groups of engineers and then hiring them to solve specific problems of moving traffic between regions. Albeit admirable, like heck yeah that was a great outcome, it's not a manager decision. Most likely it was a VP or Sr Director decision. Perhaps a manager brought it up as an idea. So if we are talking about Sr Director's+ then yes, their decisions can absolutely bring down a business. Granted I am not familiar with Netflix's org chart so perhaps it works differently, from some basic reading it looks like Netflix follows a decentralized command of sorts. My beef with the original poster was the implication of risk. Both managers and devs have risk with their decisions. It's not just a manager thing. In the end, when Netflix went down where did the mistake come from? A manager or an architecture decision? Probably it was both.