Decision-Making at the Cell Level

Overview

• What you’ll learn: The decision-making framework for amoeba units and how to use proximity to the problem as a structural speed advantage.
• Estimated reading time: 10 minutes

Introduction

The Grand Historian observes that the battle is often won not by the general with the superior strategy but by the lieutenant who makes the right decision five minutes before the opportunity closes. Organizations are no different. The competitive advantage that the amoeba system builds is, at its core, a decision-speed advantage: the person closest to the problem has the information, the authority, and the accountability to make the decision now, rather than waiting for it to travel up the hierarchy and return as a directive.

Morita frames this as one of the amoeba system’s most powerful practical contributions: a corporate organization that takes three days to resolve a pricing question loses the deal to the competitor that resolves it in three hours. The three-day organization is not slower because its people are less intelligent. It is slower because each decision must be approved by someone who was not present when the problem arose, does not have the specific context, and must be briefed, must deliberate, and must issue a response — all of which takes time that the market does not provide.

The amoeba decision framework is simple in structure but demanding in practice. If a decision affects only this amoeba — pricing to a specific client, resource allocation within the unit, a process change that touches only this cell’s operations — the amoeba leader decides now. The decision is recorded in the unit’s log and reflected in the following month’s numbers. If the decision affects other amoebas — shared resources, internal transfer pricing, cross-unit coordination — it is escalated immediately, not queued for the next scheduled meeting. Fast escalation is not a failure of autonomy; it is the correct boundary condition that allows autonomous decision-making to function without creating organizational chaos.

Key Principles

• Proximity principle: The person closest to the problem has the best information for solving it. Decision authority should follow information, not organizational rank.
• Internal-only threshold: If the decision’s effects are contained within the amoeba, make it now. Log it, implement it, review it in the next meeting.
• Cross-amoeba escalation: If the decision affects other units, escalate immediately — not at the next scheduled review, but now. Fast escalation preserves both autonomy and coordination.
• Speed as competitive advantage: Decision speed is measurable and directly affects the amoeba’s revenue opportunities and cost management.

In Practice

Maintain a standing list of decision types that the amoeba can make independently, with the criteria that define each. When a new situation arises, the first question is: does this fall within the internal-only category or the cross-amoeba category? The answer determines the path in seconds, not minutes. The list should be reviewed quarterly as the amoeba’s scope and relationships evolve.

Key Takeaways

• Amoeba decision speed is a structural competitive advantage: three hours versus three days.
• Internal-only decisions: make now, log, review next meeting.
• Cross-amoeba decisions: escalate immediately, do not queue.
• Decision authority should follow information proximity, not organizational rank.