02
Simplify Before You Scale
Complexity is the tax a business pays for decisions it never revisited. Scale collects that tax with interest.
From adding capability to removing the complexity that consumes it · 8 minute read
Volume amplifies whatever the architecture already is
Adding customers, headcount, locations, or products to a business with unclear ownership and an overloaded portfolio does not create leverage. It creates more instances of the same friction, now harder to see and more expensive to unwind.
The second curve is usually narrower than the first, not wider. It rests on a smaller set of offers, a clearer customer definition, and fewer simultaneous priorities — because that is what allows a leadership team to move at speed.
Most organizations arrive at the top of the first curve carrying a decade of accumulated commitments: legacy products kept for one customer, reports nobody reads, approvals installed after a single bad outcome, meetings that were once necessary. Each was rational. Together they consume the capacity the second curve needs.
Every complexity in an organization was once a reasonable answer to a question nobody is still asking.
Priority is proven by what gets removed
A list of twelve priorities is a statement that the organization has not decided. Teams then allocate attention by proximity to authority rather than by importance, and execution starts to look like heroics.
Real focus is visible in the calendar, the budget, and the reporting pack. If nothing was stopped, nothing was prioritized. This is why 'we need better execution' is so often a misdiagnosis: the execution is fine, the load is impossible.
Simplification is also how a business becomes transferable. A company that only works because a small group of people hold the exceptions in their heads cannot be scaled, delegated, or sold at full value.
Cut load, clarify ownership, then add volume
Begin with the portfolio: which offers, customers, and projects actually earn their place once you load them with the true cost of attention. Expect to find a meaningful share of activity producing revenue but destroying margin and focus.
Then repair ownership. Every outcome that matters gets one accountable owner, and every recurring decision gets a defined level at which it is made. Ambiguity here is the single largest driver of upward decision drift.
Then rebuild the cadence so commitments are made, tracked, and closed in a predictable rhythm, with the shortest possible path from a problem being visible to a decision being made. Only after those three are in place does adding volume produce leverage rather than noise.
Capacity that did not exist before
The first result of simplification is recovered executive time — usually the scarcest resource on the second curve. The second is faster decisions, because fewer things compete and ownership is unambiguous.
Margin follows, but it follows structurally: complexity removed once does not come back the way a cost-cutting exercise does.
Design moves for this transition
- Load every offer and major project with its true attention cost, then rank by contribution.
- Retire or reprice the bottom of that ranking before adding anything new.
- Assign one accountable owner per outcome that matters — no shared ownership.
- Define the level at which each recurring decision is made, and hold it there.
- Cut the reporting pack to the measures that trigger a decision.
Signals this part is your current work
- Revenue is growing while margin is flat or falling.
- The leadership calendar is full of discussion and short on decisions.
- Exceptions are handled by a few people who know the history.
- Adding people has not produced proportional capacity.
A simplified system is ready to be scaled — but only if the leadership team can hold the wider authority the new design gives them. That is the third part.
Run the diagnostic on this transition
Score what is holding the complexity.
Complexity is usually a decision-rights problem wearing a process costume. The diagnostic opens on decision rights and board architecture — the two dimensions that decide how much the system has to carry.
Opens on Decision rights and Board architecture · 18 practices · Executive Report PDF