Growth Adds Dots. It Multiplies Lines. — What Actually Happens to an Organization as It Goes Local, Regional and Global

The growth nobody prices

Growth arrives as a sequence of good decisions. New customers. New channels. New partners. New markets. A broader product line to serve them. Components sourced in more places. Another factory, or an acquisition that comes with its own. More SKUs in more locations, priced in more currencies, promised on more service terms.

Each of those decisions is made on its own merits, and each one usually is meritorious. What is almost never made explicit is the second effect: every addition multiplies the number of distinct paths work can take through the organization, and every new coordinating node adds interfaces that somebody has to hold together.

That is why the financial pattern of scaling is so consistent. Revenue rises. Unit costs fall, at first. Then inventories rise, fixed cost rises, SG&A rises, overheads multiply, margins compress and return on sales and return on investment drift down while the top line still looks excellent. Nobody made a bad decision. The organization simply outgrew the design it was making decisions inside.

I learned to draw this picture years ago working alongside Bill Davidson — chairman of the Mesa Research Group, formerly a tenured professor of strategy at the University of Southern California and global practice head at Deloitte & Touche, and between 1985 and 1995 the most widely cited academic in international management. His growth-dynamics teaching, and his insistence on a breakthrough rather than incremental posture, sit underneath the exhibit below and the argument that follows. The credit is his; the architecture Compass has built around it is what the rest of this article is about.

Revenue grows in a line. Complexity grows in combinations.

Read the exhibit as a condition, not a verdict

Move the footprint from local to regional to global in the exhibit and three things happen at different speeds. Coordinating nodes rise roughly in step with the business. Interfaces — every pair of nodes somebody has to hold — rise with the square of that number. Decision paths, the combinations of market, channel and product family, rise faster still, and then multiply again by currency, language and system instance.

This is not a judgement about anyone's capability. It is the arithmetic of combination, and it applies equally to a well-run business and a badly run one. What it explains is a symptom leaders describe constantly and rarely diagnose correctly: that the organization is working harder than it ever has, on the same things it used to do easily, and producing less per unit of effort.

At a local footprint, coordination can run on proximity. The founder or the leadership team can hold the whole system in their heads, and informal authority resolves what a process would otherwise have to. Somewhere in the regional band, that stops being true — usually before anyone notices, because the people who were holding it together keep holding it together for a while by absorbing the difference personally.

Global scale is where the absorbed difference comes due: price, terms and service inconsistency across regions; a gray market that exists because the system permits arbitrage; IT diversity that makes one number impossible to produce; regional overhead layered on to manage what was never designed; and a broader line whose tail consumes the capacity the vital few needed.

The breakthrough mindset, expanded

Bill Davidson's breakthrough principles were deliberately uncomfortable: pursue outrageous objectives; focus on the future rather than defending the present; lead with customer knowledge, care and relationship rather than cost reduction; prefer process innovation over the improvement of existing activity; use advanced technology to drive operating excellence; concentrate on a few critical initiatives that span the whole enterprise; use people in genuinely new ways with structured empowerment; and exploit the growth openings that breakthroughs themselves expose.

Read carefully, that is not a motivational list. Every one of those principles is a statement about design. "A few critical initiatives that span the entire enterprise" is a capacity-allocation decision. "Process innovation over improvement" is the distinction between moving a result toward the limit of the current design and moving the limit itself. "Structured empowerment" is decision rights written down. "Advanced technology to drive operating excellence" is a management system that a system can actually enable.

So a breakthrough mindset is not optimism, and it is not appetite for risk. It is the willingness to change the design rather than to work harder inside it — held by a leadership team, at the same time, with the discipline to carry it through the year in which the old design is still paying the bills. That combination is rare, and it is teachable.

It is also where mindset alone fails. A breakthrough posture with no architecture underneath it produces a wave of ambition, a portfolio of unfinished initiatives, and a leadership team quietly concluding that transformation does not work here. The posture has to be attached to something that can carry it.

A breakthrough mindset is not optimism. It is the willingness to change the design rather than work harder inside it.

Where the mindset attaches to the architecture

FOUNDATION is where a breakthrough posture becomes possible at all. Outrageous objectives require candour about the current condition, trust sufficient to say the design is wrong, and mental fitness under pressure — because the first months of a design change feel worse than the status quo. Without FOUNDATION, ambition is punished and the organization learns not to try.

SIMPLIFY is where the exhibit's arithmetic gets answered. Front-to-Back 80/20 is the disciplined allocation of scarce capacity to the vital few markets, customers, products, capabilities and initiatives — with stop, defer and de-invest decisions recorded, capacity reallocated and load analysed. A ranked priority list is not evidence of simplification. A commoditised product family kept because it strengthens the system solution is a legitimate strategic enabler; the same family kept because nobody decided is a complexity trap.

LEAD is where the few critical enterprise initiatives get value streams, owners, decision rights, standards and a cadence that survives the quarter. This is where "structured empowerment" stops being a phrase: people can move at the speed the market requires because the boundaries of their authority are explicit rather than negotiated case by case.

GROW is where the openings a breakthrough exposes are pursued deliberately — new markets, new channels, adjacencies, capability built rather than bought — instead of accumulating as unpriced additions to the map you just simplified.

ARC is what keeps the new design from becoming the next ceiling. Analyze, refine, commit — on a schedule, with evidence — so the operating system is renewed on purpose rather than replaced in a crisis every seven years.

The capability that carries it across the boundary

A design change of this size is delivered across every boundary that made the organization successful in the first place. That is precisely the work no single function can complete, and it is why a breakthrough agenda lives or dies on three capabilities that most organizations under-build.

Program and project management makes cross-boundary work deliverable: a chartered unit of work with a sponsor and success tests, a schedule with logic so you know which slippage matters, single-point accountability per activity, priced options instead of assertions when a date is under pressure, and gates that pass on evidence.

Change and transformation management makes the new design survive contact with the people who have to run it: awareness of why the current design cannot produce the next result, desire built by leaders who are visibly committed, knowledge and ability installed through training and role playbooks, and reinforcement so the old path is not quietly reopened.

And transfer, which is the part most firms skip. The capability has to end up in named internal hands — the framework documented, the role playbooks written, the cadence owned, the ARC review scheduled — or the organization has bought a project instead of an operating system.

What to do with this in the next thirty days

Draw your own footprint honestly, using the exhibit. Not the aspiration — the current count of sites, markets, channels, families, locales and system instances. Most leadership teams discover in that exercise that they disagree about the count, which is itself the first finding.

Then separate the two questions that get conflated. What is the vital few this business will be excellent at, given finite capacity? And what has to be true about the design — decision rights, standard work, systems, roles, cadence — for the organization to be excellent at those things in every region it operates?

Answer the first without the second and you have a strategy nobody can execute. Answer the second without the first and you have installed discipline around complexity you should have removed. Answered together, with program, change and transfer capability underneath, they are what moves the limit rather than the result.