My operating philosophy fits in four words: simplicity scales, complexity fails. Everything else I do — the 80/20 analysis, the one-page strategies, the five-lever growth bridge, the fixed meeting agendas — is just that sentence applied with discipline. In thirty years of running companies, from a couple hundred million to two billion in revenue, across industries and continents, I have never seen an exception. Not one. Simple companies grow, compound, and sell for premiums. Complex companies stall, burn cash, and confuse their own management teams. This post is the philosophy stated plainly, defended honestly, and translated into things you can do on Monday.
The Philosophy, Stated and Defended
Let me be precise about the claim, because it is a strong one. I am not saying simple businesses are easier to run, or that simplicity is nice to have. I am saying simplicity is the causal engine of scale. A simple company can be understood by the people running it, so decisions are fast. It can be explained to new hires, so it grows without diluting. It can be audited by a buyer, so it commands a premium. Complexity attacks all three: it slows decisions, garbles onboarding, and makes diligence a horror show.
I currently run a $1.5 billion PE-backed industrial company and chair another near a billion. Before that I ran a business at two billion. At every size, the pattern held. When we simplified — fewer SKUs, fewer initiatives, fewer reports, fewer layers — performance improved, and it improved faster than any model predicted. When we let complexity creep back, performance sagged before the financials even showed it. You could feel it in the meetings first. Meetings are the canary.
The defense is empirical, not aesthetic. I have watched this movie from every seat: CEO, chairman, board member, the guy sent in when the plan fell apart. The companies in trouble were never in trouble because they were too simple. Nobody has ever handed me a turnaround and said the problem was excessive focus.
Where Complexity Hides
Complexity is a squatter. It never announces itself; it accumulates in the corners while everyone watches the front door. After a few dozen operating reviews you learn exactly which corners to check:
- SKUs. The product catalog grows and never shrinks. Half the SKUs in a typical industrial catalog produce under five percent of revenue and consume a wildly disproportionate share of inventory, changeovers, and quality escapes.
- Customers. The bottom of the customer book — small, sporadic, price-sensitive, service-hungry — soaks up sales time and factory flexibility that the top quartile is quietly paying for.
- Meetings. Standing meetings without owners, decisions, or endings. If nobody can say what a meeting decides, it is not a meeting. It is a habit.
- Reports. Every crisis in a company’s history leaves behind a report someone still produces. Nobody reads most of them. Nobody will admit that until you cancel one and count the complaints.
- Org layers. Layers added for retention, for optics, for a reorganization three CEOs ago. Every layer subtracts truth from what reaches the top and speed from what comes back down.
- Initiatives. The strategic plan with nineteen priorities. Nineteen priorities is zero priorities wearing a costume.
None of these look dangerous individually. That is the trick. Complexity compounds the same way interest does — quietly, relentlessly, and always in the same direction unless something forces it back.
A quick illustration. At one business I ran, we counted the catalog on my second week: north of twelve thousand active SKUs. The bottom eight thousand produced under four percent of revenue and, once we loaded in changeovers, expedites, and obsolete inventory reserves, they produced negative profit — every single year, for a decade. Nobody had killed them because each one had a defender: an engineer who designed it, a rep whose one customer ordered it every other spring, a plant manager who hated writing off the tooling. We cut the catalog by more than half over three quarters. Revenue dipped less than two percent. On-time delivery went up nine points, and margin followed. The Right-to-Grow math told the same story from the other direction — the surviving product families cleared the 2.0 threshold on material margin per employee cost, and the deleted ones never had.
Why Smart People Manufacture Complexity
Here is the uncomfortable part. Complexity is not an accident that happens to organizations. It is a product organizations manufacture, and the smartest people are the most productive factories. There are three reasons, and none of them is stupidity.
First, complexity feels like work. A dense model, a forty-slide deck, a new dashboard with drill-downs — these produce the sensation of rigor. Deciding to kill a product line produces no sensation at all except fear. Smart people gravitate toward the work that feels sophisticated, and simplification never does. It feels like loss. It is actually judgment, which is scarcer than sophistication.
Second, complexity justifies headcount. Every layer, report, and process is somebody’s job description. An organization staffed to manage complexity will defend that complexity as though defending its life, because it is. I do not say this cynically; it is simply an incentive doing what incentives do. When you simplify, you must deal honestly with the fact that some roles existed only to manage what you just deleted.
Third — and this is the big one — complexity is how organizations avoid hard choices. Serving every customer means never ranking them. Nineteen initiatives means never telling seventeen sponsors no. A strategy document nobody can summarize means never committing to anything specific enough to fail. Complexity is procrastination with a budget line. The 80/20 discipline offends people precisely because it forces the ranking everyone has been dodging.
The Simplicity Disciplines
Philosophy without mechanisms is a poster in a break room. Here are the four disciplines I install in every company I run, usually within the first hundred days.
One page per strategy. If the strategy does not fit on a page, it is not a strategy; it is a hedge. One page forces the choices: which customers, which products, which levers, in what order, and — the part that hurts — what we will stop doing. I have watched leadership teams fight longer over the one-pager than they fought over the eighty-slide plan it replaced, which tells you which document was real.
One report per company. A single operating report, same format every month, that answers the questions that matter: are we growing where we chose to grow, is price holding, is the top quartile getting more of our capacity, is cash where it should be. Everything else is available on request and produced on demand. When I cancel the report zoo, the protest lasts about three weeks. The clarity lasts for years.
Five levers, not fifty initiatives. Every EBITDA plan I run is built on the same five-lever bridge — price, mix, share, M&A, cost. Every proposed initiative must name its lever and its number, or it does not get funded. This one rule kills more complexity than any reorganization, because most initiatives cannot answer either question. They exist because someone senior liked them, which is a sponsorship model, not a strategy.
Fixed agendas. The monthly operating review runs the same agenda, in the same order, every month, in every business I touch. Same pages, same owners, same definitions. It sounds rigid. It is the opposite: when the format never changes, the content becomes impossible to hide. Variance has nowhere to dress up. The most creative thing a struggling manager can do is redesign the deck, and a fixed agenda takes that pen away.
The Company With 47 KPIs
A war story. I stepped in as chairman of an industrial products company — call it a few hundred million in revenue — that measured everything. The monthly package tracked 47 KPIs. Beautiful package. Color-coded, trend-lined, produced by a talented team that spent the first week of every month assembling it. The board loved it. It looked like control.
In my first operating review I asked one question: do we make money on our largest customer? Not revenue — real profit, with freight, service, tooling, engineering hours, payment terms, and rush changeovers loaded in. Forty-seven KPIs, and not one could answer it. The room went quiet in that particular way rooms go quiet when everyone realizes the same thing simultaneously. It took the team six weeks to build the answer, and the answer was no. Our largest customer — the account the whole factory bent around, the logo on the first slide of every investor deck — was underwater on a fully loaded basis, and had been for years.
Forty-seven measurements and zero understanding. That is what complexity does: it produces the feeling of control while dismantling the substance of it. We cut the package to a dozen numbers, built customer-level profitability into the monthly rhythm, repriced the big account over two negotiations, and the business added several points of margin inside eighteen months. Nothing about the market changed. We just replaced measurement with understanding.
How Simplicity Compounds
The case for simplicity is usually made in cost terms — fewer SKUs, less inventory, smaller overhead. Fine, all true, all secondary. The real return is compounding, and it shows up in four places.
Faster decisions. In a simple company, the facts fit in one head, so decisions happen in the meeting instead of spawning three follow-ups. Decision speed is the closest thing to a master metric I know: companies that decide in days beat companies that decide in months, even when the slow company decides slightly better. The market pays for tempo.
Cleaner handoffs. Complexity taxes every interface — sales to operations, plant to plant, company to acquirer. Simple businesses hand off cleanly because there is less to explain and less to drop. This is also why simple companies integrate acquisitions well: the acquired team can learn the operating model in a week, because it fits on a page.
Easier hiring. A simple company can make a new leader productive in a month, because the model is teachable. A complex company needs a year, because the real operating model lives in the folklore of people who have survived it longest. Guess which company can grow faster than its bench.
Better exits. Buyers pay premiums for what they can understand and audit, and discount everything else. I have sat on both sides of that table. A business that runs on one report, one page of strategy, and five levers walks through diligence in weeks and earns full credit for its numbers. A complex one leaks value at every management meeting, because every question takes three people and a reconciliation to answer. Simplicity is not just an operating advantage. It is a multiple.
But Our Business Is Genuinely Complex
Every leadership team says this to me, usually in the first week, always with the same wounded sincerity. Our industry is different. Our customers demand customization. Our regulatory environment, our supply chain, our technical requirements. I have heard the speech on four continents, in a dozen industries, at every revenue size. The speech is always sincere and almost always wrong.
Here is my answer. Yes, your product may be complex — I have run businesses that make genuinely intricate engineered products for unforgiving applications. Product complexity is real and sometimes it is exactly where your margin comes from. But product complexity does not require organizational complexity. The company that makes the complicated thing does not itself have to be complicated. In fact it cannot afford to be: complexity in the product consumes so much organizational attention that everything around it must be brutally simple, or the whole system chokes. The most sophisticated products I have ever shipped came out of the simplest operating rhythms I ever ran. The complexity budget was spent where customers paid for it, and nowhere else.
So when a team tells me their business is different, I ask for the one-page strategy, the one report, and the fully loaded profitability of the top ten customers. If those exist, maybe the complexity is truly structural. In thirty years, they have never existed. The complexity was never in the business. It was in the way people had chosen to run it.
Simplicity Is a Leadership Act, Not a Process One
Here is where I part company with the process-improvement industry. You cannot delegate simplification, and you cannot kaizen your way to it, because complexity is not a process defect. It is an accumulation of unmade decisions, and only leadership can make decisions. Every SKU you kill disappoints an engineer. Every report you cancel bruises an analyst. Every initiative you stop embarrasses a sponsor. Every layer you remove has a name and a family. A black belt cannot absorb that pain for you. The CEO signs those orders or nobody does.
This is why simple companies are rare even though the philosophy is free and the evidence is overwhelming. Simplicity requires a leader willing to be, briefly and repeatedly, the least popular person in the building — someone who will say no to seventeen good ideas so two great ones get real resources, and keep saying it every quarter as the complexity tries to grow back. It always tries to grow back. Entropy does not take a quarter off.
The reward for that discomfort is a company that can actually be led. Decisions move fast because the facts are visible. People know what matters because only what matters survives. And when the day comes to sell, the buyer sees a business they can understand in an afternoon — and pays accordingly. I wrote The 80/20 CEO, From Panic to Profit, and The Rule of Three as field manuals for exactly this work, because the philosophy takes four words but the practice takes a career. Simplicity scales. Complexity fails. Choose deliberately, because your organization is already choosing without you — and it never chooses simple.
Frequently Asked Questions
What Does the Phrase Simplicity Scales, Complexity Fails Actually Mean?
It means simplicity is the causal engine of growth, not a stylistic preference. Simple companies decide faster, onboard people faster, and survive diligence better, so they compound. Complex companies stall because nobody — including management — can fully understand them. In thirty years across industries and continents, I have never seen an exception at any company size.
Where Should a CEO Look First for Hidden Complexity?
Six places: the SKU count, the bottom of the customer book, the standing meeting calendar, the report inventory, the number of org layers, and the initiative list. Start with customer and product profitability on a fully loaded basis — that single analysis usually exposes most of the other five, because complexity clusters around unprofitable work.
Is Simplification Just Cost Cutting Under Another Name?
No. Cost cutting shrinks the P&L you have; simplification changes how the company works. The primary returns are faster decisions, cleaner handoffs, easier hiring, and a higher exit multiple — the cost savings are real but secondary. Some simplifications, like killing 47 KPIs in favor of a dozen, save little money and enormous amounts of clarity.
How Do You Simplify Without Losing the Customization Customers Pay For?
Spend your complexity budget where customers pay for it and nowhere else. Product complexity that commands margin is an asset; organizational complexity is always a liability. The companies that ship the most sophisticated products need the simplest operating rhythms, because the product consumes all the attention the organization can spare.
Why Do Most Simplification Efforts Fail?
Because they are delegated. Complexity is an accumulation of unmade decisions — which customers to rank, which initiatives to stop, which layers to remove — and only leadership can make decisions that disappoint specific people. Process programs can map complexity, but a CEO has to kill it, and then keep killing it, because it always tries to grow back.
