> The Prisoner's dilemma is the reason. It's not that simple. A bigger org is slower often because it does bigger things. No, you can't just buy a tractor eve

> The Prisoner's dilemma is the reason. It's not that simple. A bigger org is slower often because it does bigger things. No, you can't just buy a tractor even though it'll be cheaper and faster for your project than to do all the work to do internal billing to rent the tractor the company already owns. Because if everyone did that then we'd have a thousand tractors and there's nowhere to put them, and we don't have time to sell them, nor do we know how to sell them. And your button on your website is not a one-line change because you're contracting with the US government and the contract has ADA clauses, and it needs 34 language translations. And no you can't make that change because last time someone improvised in this space we got dragged in front of congress and were made to promise to not do that again. So you need to follow procedures, and talk to product councel for exemptions. And you can't change that API because 6000 developers rely on that, and they need to launch before cyber monday. Sure, in that last case that's prisoners dilemma misalignment, but to be clear it's you who are misaligned with the goals of the business, so don't do it. It's not reasonable to suggest a solution of "why don't everyone just stop and do what I want". If you want to tell 10k people to stop what they're doing to work on your thing, then it'd better be right. Which means you'd better know what those 10k people were already doing. And you don't. And you can't just do it alone because it's 100 human-years worth of effort even if nobody's in your way, and you need to launch within 2 years or it's pointless to launch at all. That's what hard about making large changes in large orgs. Actually, correction: it's not even that simple.