Adapting Amoeba for SMEs

Overview

• What you’ll learn: How to adapt amoeba management for a small or medium enterprise, what to simplify versus what to preserve intact, and the specific mistakes that SMEs most commonly make when attempting full-scale amoeba implementation.
• Estimated reading time: 10 minutes

Introduction

The Grand Historian notes an irony: the amoeba management system, which was invented at a 28-person startup and whose founder explicitly designed it to preserve the spirit of a small team at any organizational scale, is most commonly studied through the lens of large corporations — Kyocera at 80,000 employees, JAL at 47,000, KDDI at 50,000. The SME leader who reads the case literature and concludes that amoeba management is only suitable for large organizations has misread the evidence. The correct reading is: amoeba management was designed specifically for small teams, and the large-company implementations are the adaptation, not the original.

That said: the SME adaptation requires different decisions than the large-company implementation. Morita’s work with Chinese SMEs — companies ranging from 20 to 300 employees in manufacturing, service, and distribution — has produced a set of specific recommendations for SME implementation that differs in important respects from the Kyocera or JAL model.

Start Small: Two or Three Amoebas

The most common SME mistake is attempting to restructure the entire company into amoeba units simultaneously. This produces coordination chaos, measurement system overload, and cultural shock that the organization’s leadership capacity cannot absorb. The correct approach: identify the two or three units most suited to amoeba management — typically those with the clearest revenue models and the strongest existing leaders — and implement the system there first. Run the pilot for six months. Let the results speak. The rest of the organization will convert more readily when they can see a functioning example than when they are being asked to accept a theoretical promise.

Simplify Time Accounting

The full Kyocera time accounting system, with its detailed allocation conventions and monthly reporting cycles, is appropriate for a large organization with dedicated accounting staff. An SME with a three-person finance function cannot manage this complexity. The simplification: use weekly instead of monthly unit time profit calculations; allocate shared costs by a simple formula (e.g., headcount proportion) rather than detailed activity-based costing; and accept that the first year’s calculations will be approximate. A reasonable approximation that the team understands and uses is more valuable than a precise calculation that only the accountant can produce.

Culture Before Metrics

The SME is typically much closer to its founding philosophy than a large corporation — the founder is often still present, and the original values are still visible in daily behavior. Use this advantage. Before implementing any measurement system, run a series of philosophy sessions in which the founder and senior team articulate, explicitly and specifically, what the enterprise is for and how it treats its people. Do not assume that because the founder knows the philosophy, the team does. Document it. Make it discussable. Then install the metrics.

Key Takeaways

• Amoeba management was designed for small teams. Large-company cases are the adaptation, not the original.
• Start with 2–3 pilot amoebas. Avoid full simultaneous conversion. Let results drive adoption.
• Simplify time accounting for SME capacity: weekly cycles, simple allocation formulas, accept approximation in year one.
• Culture before metrics: document and discuss the founding philosophy before installing the measurement system.