Repeatable Systems

McDonald's is not in the food business. It is in the systems business. Ray Kroc did not invent the hamburger. He did not invent the french fry, the milkshake, or the drive-through window. What he invented — or more precisely, what he extracted from the McDonald brothers' original San Bernardino operation and scaled to 40,000 locations across 100 countries — was a system so precisely documented, so relentlessly standardised, and so thoroughly repeatable that a sixteen-year-old working their first job could execute it to the same standard as a thirty-year veteran. The food was the output. The system was the product.

The principle is structural: any process that depends on individual talent, judgment, or memory to produce consistent results will fail at scale. A process that is encoded into a repeatable system — documented steps, defined sequences, explicit standards, built-in quality checks — can be executed by anyone trained on the system, at any location, at any time, with predictable output. The constraint on growth shifts from "can we find enough talented people?" to "can we deploy the system to more locations?" The first constraint is linear and fragile. The second is exponential and robust.

Atul Gawande's The Checklist Manifesto (2009) demonstrated the principle in the highest-stakes environment imaginable: surgery. The World Health Organization developed a nineteen-item surgical safety checklist — confirm patient identity, mark the surgical site, verify allergies, count instruments before closing — and tested it across eight hospitals in eight countries, from wealthy institutions in Seattle and Toronto to under-resourced facilities in Tanzania and India. Major complications fell by 36 percent. Surgical mortality dropped by 47 percent. The intervention was not new technology, not additional training, not better surgeons. It was a checklist. A system that made the critical steps explicit, sequential, and non-skippable — removing the assumption that skilled professionals will remember everything under pressure, because they will not. They are human.

Amazon runs on Standard Operating Procedures. Every warehouse process, every customer service interaction, every software deployment follows a documented playbook. Jeff Bezos did not build Amazon by hiring people who could improvise brilliantly. He built it by creating systems that made improvisation unnecessary for routine operations — freeing human judgment for the genuinely novel problems where it is irreplaceable. The SOPs are not bureaucracy. They are infrastructure. They are the reason a fulfilment centre in Poland operates at the same efficiency as one in Kentucky — because the system, not the individual, carries the knowledge.

The deeper principle is that repeatable systems are a form of encoded knowledge. When an expert performs a task, the knowledge lives in their head. When that expert leaves, the knowledge leaves with them. A repeatable system extracts the knowledge from the individual and embeds it in the process — in the documentation, the sequence, the checklist, the template, the standard. The knowledge becomes organisational rather than personal. It persists regardless of who executes it. It improves through iteration rather than degrading through turnover. Every company that has scaled past a hundred people has done so by converting individual expertise into repeatable systems, whether they called it that or not.