Chasing Revenue, Paying for Complexity — Global Growth Dynamics and the Twenty Percent That Actually Earns the Growth

01

Chasing revenue is not the same as choosing where to invest

Most growth stories are revenue stories. The objective is set on the top line, the plan is built to reach it, and every route to that number is treated as roughly equivalent: another customer, another market, another channel, another partner, another product family, another factory, another acquisition. Each move is defensible on its own. Together they answer the wrong question — how do we get bigger — instead of the one that decides whether growth is worth having: which twenty percent of markets, customers and products will carry eighty percent of the profitability and the growth we actually want?

When revenue is the primary objective, the vital few and the trivial many are funded on the same terms. Capacity, engineering attention, working capital, leadership time and system complexity flow to whatever closed most recently. Nothing is stopped, because nothing was chosen. That is how a business ends up serving four times as many combinations as it can be excellent at, and paying for all of them.

The build below is the original Global Growth Dynamics slide, recreated. It is worth advancing one stage at a time, because the order matters: growth decisions first, local absorption second, global inconsistency third, and only then the two lines at the bottom — margins down, return on sales and return on investment down. Nobody signs up for the last stage. Everybody signs up for the first three.

I learned to draw this cascade 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. The growth-dynamics teaching and the breakthrough posture are his. What Compass has built around them is the rest of this article.

Revenue answers how much bigger. Allocation answers whether bigger is worth having.

02

Run the build and watch the vector change

The slide was never meant to be read as a static picture. In slideshow mode each click added another decision and the direction of the business visibly changed with it. The exhibit below runs it that way: a local-to-global plane, a revenue vector and a return vector sharing one origin, and every step applying that step’s consequences to both.

Advance it slowly. For the first three steps the two vectors barely separate, which is exactly why growth of this kind is so easy to defend — the top line responds immediately and the cost of the design has not arrived yet. The separation begins when each addition is absorbed locally rather than designed for, widens as components, vendors, SKUs, inventory and overhead accumulate, and becomes the whole story once global scale puts the inconsistency in front of the customer.

The indices are illustrative, not a measurement of any company. What is real is the shape: revenue can keep climbing while the return on it falls, and the gap between the two lines is the compound nobody priced.

03

Read the build as a condition, not a verdict

Every stage of that cascade is a reasonable decision taken in isolation. Local processes emerge because the local team has to ship. IT diversity appears because each addition arrived with a system. Regional overhead is added because somebody has to hold the interfaces together. SKUs and locations multiply because saying yes wins the order. The compound is not incompetence; it is the arithmetic of accumulation inside a design that was never revisited.

That arithmetic is why the financial pattern is so consistent. Revenue rises. Unit costs fall, at first, then reverse as scale volumes fragment across variants. Inventories rise. Fixed cost rises. SG&A rises. And the return on the growth quietly declines while the top line still looks excellent enough to protect the design that is causing it.

At a local footprint, coordination runs on proximity: the leadership team can hold the whole business in their heads. Somewhere in the regional band that stops being true — usually before anyone notices, because the people holding it together keep absorbing the difference personally. Global scale is where the absorbed difference comes due, in front of the customer: price, terms and service inconsistency across regions, a gray market that exists because the system permits arbitrage, and no single enterprise number that can be produced without reconciliation.

04

The answer is allocation: quads and quartiles on market, customer and product

Complexity created by undisciplined growth is not removed by working harder inside it. It is removed by deciding — line by line — what this business will be excellent at with the capacity it actually has. Front-to-Back 80/20 does that in two moves any leadership team can follow.

First the quartile: rank every market, customer and product family by contribution, not revenue, and see where the profit genuinely sits. Revenue ranks size; contribution ranks worth. In most portfolios the top quartile carries the majority of contribution and a minority of the coordination load, and the bottom quartile carries almost no contribution and a disproportionate share of the effort.

Then the quad: place each line on value against complexity to serve, and take the decision the position implies — invest and scale the high-value, low-complexity lines; keep the high-value, high-complexity lines and standardize the work around them; maintain the thin but cheap lines with efficiency rather than investment; and reprice, restructure or release the lines that consume both margin and capacity.

Two rules keep this honest. A commoditized or thin-margin line kept deliberately because it strengthens the system solution is a strategic enabler and belongs in the portfolio; the same line kept because nobody decided is a complexity trap. And evidence of simplification is recorded stop, defer and de-invest decisions with capacity visibly reallocated to the vital few — never a ranked priority list.

Revenue ranks size. Contribution ranks worth. The quad turns the read into a decision.

05

The mental strength to break through how we do business today

Here is the part no spreadsheet reaches. The design that produced today's revenue is the design the current leadership team built, defended and won with. It deserves respect. It got the business here. It also, in almost every case, will not get it to the next growth curve — and saying that out loud costs something personally.

So the allocation decision fails for reasons that are not analytical. Stopping a product family means telling the person who launched it. Repricing an account means risking a relationship somebody owns. Standardizing regional terms means removing discretion from leaders who earned it. Under that pressure, capable executives default to their habitual reactive patterns — control, avoidance, pleasing, hyper-rationalizing, restlessness — and the decision quietly becomes another initiative instead of a change in the design.

That is why mental fitness is treated here as operating capability, not personal development. The ability to stay curious rather than defensive when the evidence indicts your own design, to interrupt a habitual reaction before it becomes a decision, and to hold the year in which the old design is still paying the bills while the new one is being installed — that is what carries an allocation decision through to a result.

Respect what got you here and refuse to let it decide what comes next. Both at once. That combination is rare, it is teachable, and it is developed deliberately rather than discovered under pressure.

The current design deserves respect for getting us here. It rarely deserves the next decade.

06

Where the breakthrough posture attaches to the architecture

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 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 breakthroughs expose.

Read carefully, that is not a motivational list — every principle 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 difference between moving a result toward the limit of the current design and moving the limit itself. "Structured empowerment" is decision rights written down.

FOUNDATION is where the posture becomes possible at all: candour about the current condition, trust sufficient to say the design is wrong, and mental fitness under pressure. SIMPLIFY is where the cascade is answered by allocation. LEAD is where the few enterprise initiatives get value streams, owners, decision rights, standards and a cadence that survives the quarter. GROW is where the openings a breakthrough exposes are pursued deliberately instead of accumulating as unpriced additions to the map you just simplified. ARC — assess, refine, commit — keeps the new design from becoming the next ceiling.

A breakthrough posture with no architecture underneath 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.

07

The capability that carries it across the boundary

A design change of this size crosses every boundary that made the organization successful in the first place. Program and project management makes that 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.

08

What to do with this in the next thirty days

Advance the build against your own business honestly. 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 run the quartile and the quad on markets, customers and products, using contribution rather than revenue, and put a decision beside every line in the bottom half. Invest, simplify, maintain, restructure. Record what stops, what defers, what is de-invested, and where the released capacity goes.

And prepare the team for the conversation, not just the analysis. The numbers will indict decisions people in the room made and were right to make at the time. Answered together — allocation, architecture, program, change, transfer and the mental strength to hold the line — they move the limit rather than the result.