Org Chart vs. Amoeba Map

Overview

• What you’ll learn: Why the traditional org chart is the wrong tool for amoeba design, how to draw an amoeba map, and what the map reveals that the org chart cannot.
• Estimated reading time: 10 minutes

Introduction

The Grand Historian records: The map that shows mountain ranges and river systems tells you where armies can march. The map that shows only administrative prefecture boundaries tells you who is nominally in charge of what. These are different maps. An army that confuses them loses. The traditional organizational chart is a prefecture boundary map. The amoeba map is the terrain.

The org chart answers one question with great precision: who reports to whom. This is useful for HR administration. It is nearly useless for amoeba design, because reporting relationships and value flows are often orthogonal. The CFO reports to the CEO. But in terms of value flows, the CFO’s team may provide services to every other department, receive its “revenue” through internal pricing, and have a cost structure completely different from what its hierarchical position suggests.

The amoeba map replaces hierarchy with economics. It shows: where does revenue enter the system? Through which amoebas does it flow before reaching the company’s P&L? What internal transfers occur, at what prices, between which units? Where are the P&L boundaries? Who is accountable for each boundary?

How to Draw an Amoeba Map

1. Start with external revenue sources: Draw boxes for external customers and the amoebas that receive revenue from them. These are the “revenue entry points” of the system.
2. Trace internal flows: For each revenue-receiving amoeba, identify which internal units supply it — and draw arrows with the internal transfer price for each arrow.
3. Draw P&L boundaries: Circle each group of activities that shares a single P&L. This circle IS the amoeba.
4. Name the leader: Write the accountable leader’s name on each circle. If you cannot name a single person, the boundary is not yet valid.
5. Mark support flows: Internal functions (HR, accounting, IT) that serve all amoebas should be shown with dotted arrows and their internal charge-out rate labeled.

What the Map Reveals

When drawn honestly, the amoeba map typically reveals: units that appear separate on the org chart but are economically inseparable; units that appear unified on the org chart but could be more accountable if separated; support functions whose costs are invisible to the units that consume them; and revenue flows that no one had traced end-to-end before.

Key Takeaways

• The org chart shows reporting hierarchy. The amoeba map shows value flows and P&L boundaries.
• Drawing the amoeba map is the first and most important exercise in amoeba design.
• The map reveals economic realities that the org chart systematically obscures.
• Every circle on the map must have a named accountable leader before the design is complete.