How do large organizations like Amazon and AWS maintain innovation despite their enormous scale?
Answered at 10:00 in Ep.188 -The CEO Playbook: Start-Ups, Scale-Ups and Successful Exits · The Conference Room with Simon Lader
How do large organizations like Amazon and AWS maintain innovation despite their enormous scale?
Large organizations stay innovative by applying the two-pizza rule—keeping teams small enough to feed with two pizzas (under 12 people), a principle AWS used to launch S3 and transform cloud storage. Success also depends on writing the press release before building the product, granting autonomy between functions, and avoiding dependencies that slow decision-making.
Scale typically stifles innovation because bureaucracy, approval chains, and interdependencies slow execution. Yet companies like Amazon and AWS have cracked a different code: they treat innovation as a structural problem, not a cultural one. Etchew observed this firsthand while working with these organizations on encryption and cloud technologies.
The two-pizza rule emerged as a core organizing principle inside AWS. As explained in the episode, when AWS launched S3—arguably the foundational service that enabled modern cloud computing—they did it with only 12 people on the core team. That constraint forced clarity: what's essential, and what isn't? Small teams make faster decisions, own accountability completely, and sidestep the lengthy consensus-building that hamstrings larger groups.
Writing the press release before building the product
Another counterintuitive practice Etchew highlighted is beginning with the customer perspective. Instead of building first and writing marketing copy second, teams write the press release—the public-facing narrative of what the customer will experience—before a single line of code is written.
This disciplines the entire effort around what actually matters to the user, not what's easiest to build internally. It forces honest conversations: Is this feature worth building? Does it solve the problem we claim it solves? A product built backward from the customer promise is less likely to be a technical achievement that nobody wants.
Full answer and detailsRead the whole answer, key facts and every other question from this episode
In short
Large organizations stay innovative by applying the two-pizza rule—keeping teams small enough to feed with two pizzas (under 12 people), a principle AWS used to launch S3 and transform cloud storage.
David Etchew · Ep.188 -The CEO Playbook: Start-Ups, Scale-Ups and Successful Exits · The Conference Room with Simon Lader · answer at 10:00
Key takeaways
- Success also depends on writing the press release before building the product, granting autonomy between functions, and avoiding dependencies that slow decision-making.
- Scale typically stifles innovation because bureaucracy, approval chains, and interdependencies slow execution.
- The two-pizza rule emerged as a core organizing principle inside AWS.
- Another counterintuitive practice Etchew highlighted is beginning with the customer perspective.
- This disciplines the entire effort around what actually matters to the user, not what's easiest to build internally.
The full answer · about 3 min
Large organizations stay innovative by applying the two-pizza rule—keeping teams small enough to feed with two pizzas (under 12 people), a principle AWS used to launch S3 and transform cloud storage. Success also depends on writing the press release before building the product, granting autonomy between functions, and avoiding dependencies that slow decision-making.
Scale typically stifles innovation because bureaucracy, approval chains, and interdependencies slow execution. Yet companies like Amazon and AWS have cracked a different code: they treat innovation as a structural problem, not a cultural one. Etchew observed this firsthand while working with these organizations on encryption and cloud technologies.
The two-pizza rule emerged as a core organizing principle inside AWS. As explained in the episode, when AWS launched S3—arguably the foundational service that enabled modern cloud computing—they did it with only 12 people on the core team. That constraint forced clarity: what's essential, and what isn't? Small teams make faster decisions, own accountability completely, and sidestep the lengthy consensus-building that hamstrings larger groups.
Writing the press release before building the product
Another counterintuitive practice Etchew highlighted is beginning with the customer perspective. Instead of building first and writing marketing copy second, teams write the press release—the public-facing narrative of what the customer will experience—before a single line of code is written.
This disciplines the entire effort around what actually matters to the user, not what's easiest to build internally. It forces honest conversations: Is this feature worth building? Does it solve the problem we claim it solves? A product built backward from the customer promise is less likely to be a technical achievement that nobody wants.
More answers from this episode
- 5:05What advantages does cross-functional leadership experience provide compared to deep specialization in a single domain?
- 7:05What operational capabilities do small companies have relative to larger enterprises?
- 19:00What is the relationship between acceptable failure rates and high-performing team culture?
- 20:00How should organizations frame learning from unachieved goals and missed targets?
- 24:30What is the primary challenge for employees transitioning from acquired small companies into larger organizations?