A business doubles its revenue over four years and the people running it notice something they did not expect. Everything is harder. Decisions that used to take a morning now take three weeks. Information that everyone simply knew must now be requested. The team is larger, more capable, and better resourced than it has ever been, and it is producing outcomes more slowly.
Nothing has gone wrong in the ordinary sense. No one is underperforming and no market has turned. What has happened is that the enterprise has accumulated complexity faster than it has accumulated scale, and complexity is consuming a growing share of the capacity that growth was supposed to provide.
This is among the most predictable difficulties in business and among the least prepared for, largely because it arrives disguised as success. Every individual source of the complexity was a good decision. The problem is only visible in aggregate, and nobody owns the aggregate.
Complexity Grows Faster Than Scale
The reason is arithmetic rather than management failure. What creates coordination work is not the number of parts but the number of connections between them, and connections increase far more rapidly than parts.
A business with four people who all need to stay aligned has six relationships to maintain. At ten people it has forty five. At twenty, one hundred and ninety. Headcount multiplied by five; the coordination burden multiplied by more than thirty. Nobody experiences this as a formula, but everybody experiences the result, which is that the informal alignment that used to happen without effort has quietly stopped working.
The same pattern applies to products, locations, customer categories, and systems. Adding a second location does not double operational complexity. It introduces the questions of consistency between them, allocation across them, comparison of one against the other, and the movement of people and work between the two. A third location does not add the same increment as the second; it adds more.
Understanding this changes the framing of a growth decision. The correct question is not whether the business can afford the new thing. It is whether the business can afford the connections the new thing creates, and those are considerably harder to price. Each commitment permanently enlarges what the organization must hold in view, a cost examined from the selection side in How Durable Enterprises Decide Which Opportunities to Pursue.
The Coordination Tax
In a small operation, coordination is nearly free. People overhear each other. Context is shared because everyone has been present for the same events. Alignment is a byproduct of proximity rather than an activity.
As an enterprise grows, that free coordination disappears and must be replaced by deliberate mechanisms: meetings, reports, planning cycles, updates, systems that hold shared information. Each of these is necessary. Each also consumes hours from the people who create the value, and the total is rarely calculated.
It is worth calculating occasionally, because the figures are usually startling. A weekly meeting of twelve people running ninety minutes consumes eighteen hours a week, nearly half a full time role, before any preparation. Repeated across a dozen such forums, an organization can find that a substantial fraction of its senior capacity is engaged in coordinating work rather than doing it.
The tax cannot be eliminated and should not be. What it can be is deliberate, examined periodically, and matched to what it actually produces. A useful test for any recurring forum is whether a decision is made in it. Forums that exist to share information are frequently better replaced by something written, which people can read in a fifth of the time and at a moment of their choosing.
Where Complexity Accumulates
Complexity is not evenly distributed. It gathers in a few places, and knowing them makes it possible to look deliberately rather than waiting for symptoms.
Variants in what the business offers
Almost every enterprise accumulates variety it never chose. A significant customer wanted something slightly different and it was agreed. A version was retained because two accounts still use it. A special arrangement was made during a difficult negotiation and never revisited. None of these was wrong. The total is a business supporting far more variation than it would design if starting today, and paying for that variation in inventory, training, error rates, and the attention of everyone who has to know which case applies.
Interfaces between internal groups
Every boundary inside an organization creates a place where work is handed over and where responsibility can become unclear. Reorganizations frequently move boundaries rather than reducing them, which relocates the friction without removing it. The number of internal handoffs a typical piece of work passes through is a good measure of accumulated complexity, and it is one very few businesses track.
Reporting that outlives its purpose
Reports are created in response to a specific question and then continue indefinitely after the question has been answered or has ceased to matter. A business ten years into its growth is usually producing several regular reports that nobody acts on, that someone spends real time preparing, and that continue because stopping them would require a decision nobody has been asked to make.
Too Many Priorities Is the Same as None
Growing enterprises tend toward priority inflation. Each area has objectives, each is defensible, and the combined list can reach twenty or thirty items described as important for the year.
The organization then does what any organization does with an unrankable list. It allocates attention by whatever pressure is most immediate, which usually means the item with the most persistent advocate or the nearest deadline. Effort is spread across everything, most things advance slightly, and few reach the point where they produce a result. At year end the list is reviewed and much of it is carried forward, which teaches everyone that the list is aspirational.
The correction is uncomfortable because it requires explicitly deciding that genuinely worthwhile things will not be done this year. That is a different statement from ranking, which preserves the fiction that everything will eventually be reached. Enterprises that manage this well tend to hold a very short list of things that will definitely happen, treat everything else as available capacity if it appears, and say so plainly rather than leaving people to infer it.
A related discipline is finishing. An organization carrying eleven partially completed initiatives is carrying eleven sets of coordination overhead and receiving the benefit of none. Completing four and stopping the rest frequently produces more value than continuing all eleven, and it returns capacity that had been invisibly committed.
Layers and the Distance From the Work
Growth adds management layers because spans of control have limits. Each layer solves a real problem and introduces two others: information degrades as it travels, and the people making significant decisions become further from the work those decisions concern.
The degradation is not usually dishonesty. It is compression. Each level summarises, and summarising means selecting, and selection reflects what the summariser believes matters and how their own area appears. Four layers of good faith summarising can produce a picture at the top that would not be recognised by the people at the bottom.
The distance problem is subtler. A senior person who has not observed the work directly for several years is making decisions using a mental model formed under earlier conditions. They are not less capable. They are working from a description rather than the thing, and descriptions omit exactly the friction that determines whether a plan will work.
Partial remedies exist and they are simpler than restructuring. Senior people spending regular time in the operation, with no agenda and no review attached. Some information travelling to the top without intermediate processing. Routine contact with customers by people who do not otherwise meet them. How this shapes the quality of oversight is developed in The Role of Governance in Keeping Enterprise Decisions Clear.
Complexity People Create to Protect Themselves
Not all accumulated structure is an accident of growth. A portion of it is deliberate, added by capable people responding sensibly to how the organization treats mistakes, and it will not respond to process review because the cause is elsewhere.
The mechanism is straightforward. Someone is held responsible for an error that arose from a judgment call, in a setting where the judgment was treated as carelessness. The rational response is to stop making that judgment alone. A second signature is introduced, a form is created, a step is added that documents that the decision was shared. Each of these is a small piece of insurance against being the person blamed next time, and each is entirely reasonable from where that individual is standing.
Multiply this across an organization over a decade and a substantial layer of protective process exists that nobody would defend on its merits and that everyone quietly relies on. Attempts to remove it meet resistance that appears irrational until the underlying incentive is understood. People are not defending the form. They are defending the cover it provides.
Removing this class of complexity requires changing what happens after a decision goes wrong. Where reasonable judgments that produced poor outcomes are examined for their reasoning rather than punished for their results, the demand for protective structure falls on its own, and the steps can be retired without a campaign. Where that does not change, every removal is resisted and the structure regrows in a slightly different form.
The diagnostic is simple enough. Ask why a step exists and listen for whether the answer describes a benefit to the work or a consequence to be avoided. The second answer points at something other than process.
Simplification Is a Permanent Job
Complexity accumulates continuously because every day contains small additions and almost no removals. Adding a step, a report, a variant, or an approval requires only a good reason. Removing one requires someone to notice it, take responsibility for the consequences, and expend goodwill on a change that will inconvenience whoever currently relies on it.
The asymmetry means that an organization with no deliberate simplification process will become more complex every year regardless of intent. Periodic reorganizations do not solve this. They tend to redistribute complexity while adding a period of disruption, after which accumulation resumes from the new baseline.
What works better is continuous and small. Some enterprises attach a removal requirement to additions, so that introducing a new report or approval means identifying one to retire. Some review a defined category each quarter, rotating through offerings, reports, forums, and processes over a couple of years. Some simply give one person the standing remit to ask why something exists, with the authority to stop it if the answer is thin.
The mechanism matters less than that removal has an owner. Complexity accumulates through the ordinary operation of a well intentioned organization. Only a deliberate counterforce reverses it, and it has to run continuously rather than being applied during occasional efficiency campaigns. Keeping this in view over long periods rather than reacting to it during difficult years is characteristic of the durable business thinking associated with Norm Ebenstein, where the shape of an enterprise is treated as something to be tended across decades rather than restructured under pressure.
What to Simplify First
Not all complexity carries equal cost, and attacking it indiscriminately wastes effort on things that are merely untidy.
The highest value targets are the ones that touch the most people and recur most often. A confusing approval process used weekly by forty people costs far more than an elaborate procedure used twice a year by two. Frequency multiplied by reach is a better guide than how complicated something appears.
Second are the places where complexity produces errors rather than merely effort. A variant structure that occasionally results in the wrong thing being supplied carries a cost well beyond the time it consumes, because each error generates correction, apology, and a small withdrawal from a customer relationship.
Third are the arrangements that exist to accommodate a situation that has ended. These are the easiest to remove and the hardest to see, since they have become the normal way of working. Asking why a particular step exists, and finding that the answer refers to a customer, a system, or a person no longer present, identifies work that can simply stop. Where the same resources should go once freed is a question of allocation, examined in Why Capital Allocation Is a Business Strategy, Not Just a Finance Decision.
The Ability to Remove
Businesses become good at adding because addition is what growth rewards and what gets recognised. Very few develop a comparable capability for removal, and the absence of it sets a ceiling on how large an enterprise can become while remaining effective.
The ceiling is real and observable. An organization reaches a size where the coordination required to operate consumes the additional capacity that size provides, and further growth produces more activity without more result. The businesses that pass through that ceiling are not the ones that grew fastest. They are the ones that kept removing while they grew, so that the coordination burden stayed proportionate to what the enterprise was actually doing.
This is why simplification deserves standing rather than being treated as housekeeping. An enterprise able to stop things, retire arrangements, decline variety, and hold a short list of priorities can keep growing without becoming slow. One that can only add will eventually be constrained by its own accumulated structure, and it will be a considerably less satisfying place to work while that happens. Maintaining the standards that make simplification possible without losing consistency is the operating discipline described in How Operating Discipline Protects a Growing Business.
