Philip Soriano

Bezos redesigned work to create a system of independent, decoupled teams who were guided by a set of hows dramatically different from prior practices at Amazon and other large tech companies. For example, most software companies require teams to utilize one another’s code to increase efficiency. To increase velocity and reduce dependency, Amazon does the opposite: Its software teams are mostly free to choose whether they use common services or create their own building blocks of code. This results in duplicative work and some inconsistencies in the user experience, but Bezos justifies it by saying he’d “rather have two than none.”

Some of Amazon’s managerial innovations have become celebrated. For example,

1. teams adhere to the “two-pizza rule,” limiting team size to only as many people as can be fed by two pizzas (typically eight or fewer).

2. PowerPoint presentations are forbidden because they lull participants into passivity; instead, Amazon requires every proposal to be written in a narrative memo of six pages or fewer, to deliver more detailed thinking than is typically found in slide presentations.

3. After all the meeting attendees read the memo closely, they have a nonhierarchical, no-holds-barred debate. The goal is to interrogate everything thoroughly, and vigorous dissent is encouraged. Before stepping down as CEO, Bezos participated in hundreds of these meetings himself. Instead of sitting back and waiting for the CEO to make the decision, everyone at Amazon is expected to speak up and disagree—even with Bezos or his successor, Andy Jassy. Once a determination is made, the CEO supports the path forward, knowing that most conclusions are provisional and can be revisited as new information comes in—what Amazon calls “two-way-door decisions.”

This is what we mean when we say leaders architect the way work gets done. It’s not about changing org charts. It’s about shifting decision rights closer to the front lines—and equipping those teams with the tools and frameworks that allow them to act. Those include customer-value metrics, structured memos, and experimentation protocols. It’s difficult work because it often requires leaders to give up control—to redistribute authority, remove approvals, and reduce the frictions that slow teams down. When done well, it promotes speed, clarity, and autonomy—which is why Amazon, a giant company, continues to launch innovative products and services quickly.

All four leaders we studied recognized that frontline teams are key to creating and delivering value for customers, whether they are internal or external. They made it their personal mission to design work processes so that employees are empowered with the tools and support they need and don’t hit obstacles that slow them