Operational Excellence Is a System Not a Culture
Companies that sustain operational excellence do not rely on hiring the right people or fostering the right vibes. They build explicit, repeatable systems that make excellence the default behavior.
"Conglomerates can evolve over time: acquisitive companies can also divest what isn't working, so they often end up with a business completely unrelated to where they started. They're worth studying for two reasons: first, the good ones have gotten very good at capital allocation... And second, when they do something beyond pure capital allocation, and apply it to many different industries, it can probably be applied to other companies, too." Byrne Hobart
Danaher is the clearest modern example. The Danaher Business System (DBS) is a codified set of lean management tools, continuous improvement practices, and performance metrics that the company applies to every acquisition it makes. Danaher acquires middling industrial companies, installs DBS, and systematically improves margins, quality, and throughput. The system works across wildly different industries from dental equipment to water treatment because it operates at the level of process, not product knowledge. Culture alone could not survive this level of transplantation. A system can.
This maps onto what the Software Engineering at Google book calls the distinction between programming and software engineering: "Programming is the immediate act of producing code. Software engineering is the set of policies, practices, and tools that are necessary to make that code useful for as long as it needs to be used." Google does not rely on hiring geniuses who intuit the right thing. It builds code review systems, style guides, testing infrastructure, and deprecation policies that make good engineering the path of least resistance. The system scales; individual heroics do not.
The Japanese quality revolution followed the same logic. Deming's insight was not "hire better workers" but "build statistical process controls into the workflow so that defects are caught structurally." Quality became free, as Crosby argued, because the system prevented errors cheaper than fixing them after the fact.
Takeaway: If your excellence depends on specific people rather than specific processes, you do not have operational excellence you have luck.
See also: Systems Beat Goals Every Time | One Percent Improvements Compound | Single Threaded Ownership Gets Things Done