Amazon vs. Toyota: Which of the 5 Management Functions Drives Real Scale?

The 5 Functions of Management Are the Same Everywhere — Except How Amazon and Toyota Execute Them Is Worlds Apart

Every business school teaches Henri Fayol’s five functions of management: planning, organizing, commanding, coordinating, and controlling. They sound universal. They sound neutral. But the way Amazon and Toyota have operationalized these five functions reveals something most management textbooks completely miss — the functions themselves are not the competitive advantage. The sequence and emphasis you apply them in is.

Function 1: Planning — Top-Down Narrative vs. Bottom-Up Signal

Amazon’s planning function is famously built around the “working backwards” memo culture. Before a product exists, a press release is written. Planning starts from the customer outcome and reverses into operations. Toyota’s planning function, by contrast, is rooted in nemawashi — the slow, consensus-building approach where planning emerges from the factory floor upward. Amazon plans for disruption. Toyota plans for elimination of waste. Both are rigorous. Neither resembles the other.

Function 2: Organizing — The Two-Pizza Rule vs. The Andon Cord

Amazon organizes around autonomous, small teams that own entire business outcomes — the famous two-pizza rule. Each unit operates almost like a standalone business model. Toyota organizes around interdependence. The Andon cord — where any worker can stop the entire production line — means the organization is structured so that no single node hides a problem. Amazon’s organizing principle accelerates speed. Toyota’s organizing principle accelerates quality. These are fundamentally different bets on where value gets created.

Function 3: Commanding — Bezos’s 1-Way vs. 2-Way Door Framework

The commanding function — often criticized as outdated — is where both companies quietly shine. Amazon’s leadership distinguishes between one-way and two-way door decisions. Irreversible decisions get escalated. Reversible ones get delegated fast. Toyota’s commanding structure uses jidoka, giving machines and workers alike the authority to halt operations autonomously. In both cases, the commanding function is not about control — it is about clarifying decision rights at every level of the organization.

Function 4: Coordinating — APIs vs. Kaizen Events

Amazon coordinates through APIs and internal platforms. Teams coordinate by consuming each other’s services, not by attending meetings. Toyota coordinates through scheduled kaizen improvement events where cross-functional teams physically solve one problem together for a defined period. Amazon coordinates asynchronously at scale. Toyota coordinates synchronously at depth. Both approaches work. Neither would survive if transplanted wholesale into the other company’s business model.

Function 5: Controlling — Real-Time Dashboards vs. Weekly Gemba Walks

Amazon’s controlling function is data-first — leadership reviews real-time metrics dashboards before any human report. Toyota’s controlling function is presence-first — the gemba walk requires managers to physically observe the actual place of work. One model trusts abstraction. The other trusts observation.

Which Approach Actually Wins?

The honest answer is that neither Amazon nor Toyota is executing Fayol’s five functions better in absolute terms. They are each executing them in ways that are inseparable from their underlying business model. Amazon’s model monetizes speed and selection. Toyota’s model monetizes reliability and precision engineering. The five functions of management do not determine competitive advantage. How deeply they are embedded into the business model architecture does. That is the lesson most strategy frameworks still refuse to teach.

For a deeper breakdown of how the five functions of management apply across business models, see the full analysis at FourWeekMBA.