How Amazon's decentralized operating structure and small, independent teams that use common internal systems, are integral to the company's unending scalability
Benedict Evans : Tweets: @grady_booch , @bwertz , @jamescham , @grady_booch , and @roundtrip Tweets: Grady Booch / @grady_booch : “ Amazon buys TV shows to get you to buy toilet paper.” @BenedictEvans http://www.ben-evans.com/... Boris Wertz / @bwertz : “Amazon is hundreds of small, decentralized, atomized teams sitting on top of standardised common internal systems.” - @BenedictEvans on the Amazon Machine http://www.ben-evans.com/... James Cham / @jamescham : Too often ignored in the Amazon story: the difficulty and investment in standardised common internals systems http://twitter.com/... Grady Booch / @grady_booch : And it all began with the architectural decision that @JeffBezos made several years ago, that everything should be made a service (and this was long before Services Were Cool); from this much goodness flowed. http://twitter.com/... Science-Based Greg Lloyd / @roundtrip : “Amazon at its core is two platforms - the physical logistics platform and the ecommerce platform. Sitting on top of those, there is radical decentralization. Amazon is hundreds of small, decentralized, atomized teams sitting on top of standardised common internal systems.” +++ http://twitter.com/...
Context & Ripple Effects
Benedict Evans's 'Amazon Machine' argument reframes a company usually described as a bundle of businesses as hundreds of small, autonomous teams sitting on standardized common internal systems — with James Cham adding that the hard, expensive part everyone skips is building those shared internals. The piece lands mid-arc in our coverage: months earlier, TechCrunch described how Amazon exposes its internal operations to external competition to kill inefficiency, and two years later The Register documented the same philosophy inside cloud infrastructure as the Away Team model, where one team builds a service another team needs.
Why it matters: if the operating structure is the product, then everything else in the corpus follows from it — the R&D-heavy moat behind Amazon Go, the proposal to turn a standardized employee healthcare interface into a marketplace for other employers, and even the counterpoint from BuzzFeed News that Amazon can run logistics at planetary scale while being surprisingly bad at its retail website.
First-order effects
- Small independent teams own their services end-to-end against common internal systems, so scaling comes from adding teams rather than adding coordination layers — the mechanism AWS institutionalized with the Away Team model.
Second-order effects
- Internal systems built for atomized teams become sellable external products, which is how AWS converts an org chart into a business — and why, as the anonymous AWS engineer explained, migrating in is easy while leaving is hard.
Third-order effects
- If the pattern holds, competitive advantage shifts from what a company sells to how it is structured: rivals must either rebuild their internals around small teams on shared platforms or accept a structural cost-and-speed disadvantage they cannot buy off the shelf.
The trend: Corporate scalability is migrating from centralized planning to federated small teams on standardized internal platforms, with the platform layer becoming both the moat and the product.