Most Businesses Are Built on Activities. Very Few Are Built on Systems.

There is a particular kind of exhaustion that comes not from doing too little, but from doing too much without it adding up to anything.

Most business owners know this feeling well. The team is working hard. Campaigns are running, salespeople are calling, content is being published, follow-ups are going out. The calendar is full. The dashboards show movement. And yet, quarter after quarter, the needle moves slower than the effort deserves.

This is not a productivity problem. It is an architecture problem.

The Difference Nobody Talks About

In 1986, the quality theorist W. Edwards Deming made a claim that most managers still haven't fully absorbed. He was talking about manufacturing. But the observation applies with equal precision to how businesses pursue growth.

The distinction Deming was pointing at — between the people doing the work and the structure within which they do it — is exactly what separates businesses that compound from businesses that grind.

An activity is a discrete action with a clear beginning and end. A campaign launches. A proposal goes out. An event is hosted. A post goes live. Each of these can be executed well. Each can produce a result. But without architecture connecting them — without a designed sequence of causes and effects — they remain isolated events. They don't build on each other. They don't get smarter over time. They require roughly the same amount of energy every cycle.

A system, by contrast, is a designed set of connected processes where the output of one step becomes the input for the next, and where the whole learns and improves with use. Clayton Christensen, the Harvard Business School professor whose work on disruption reshaped how business schools think about competition, spent years studying why capable companies failed. One of his most consistent observations was that most organisations are structured to optimise current activities rather than to build future capability. They are, in his framing, built to do — not built to compound.¹

What Activity-Driven Businesses Actually Look Like

They're not easy to spot from the outside. Activity-driven businesses can look very capable. They have teams. They have tools. They have strategies, decks, and quarterly plans. What they don't have is continuity.

The marketing team runs a campaign. It works, or it doesn't, and then they move to the next one. The sales team calls a list. They convert some, lose some, and then move to the next list. Each initiative is evaluated in isolation. There is no mechanism for the learning from one campaign to inform the design of the next. There is no feedback loop between what sales hears from prospects and what marketing says to them.

The management consulting firm McKinsey, in a 2019 study of over 1,800 companies globally, found that organisations which built interconnected capability across functions — rather than optimising each function independently — were 2.4 times more likely to achieve above-average growth.² The finding wasn't that they were smarter or worked harder. It was that their activities were wired together.

This distinction — wired vs. isolated — is what most strategic planning misses. You can have the right activities in the wrong structure and still produce mediocre results.

Why Most Businesses Default to Activities

There are reasonable explanations for why activity-orientation is so common, and they don't all reduce to bad management.

The first is that activities are measurable in ways that systems are not. You can count calls made, ads placed, events attended. You can report on them. You can hold people accountable for them. Systems, by contrast, produce results on a different time horizon. The feedback loop between building a system and seeing it perform can be months, not weeks. In an environment where quarterly results matter, systems-thinking loses to activity-thinking almost every time — not because it's wrong, but because it's slow to show up in the numbers.

The second is that activities create the feeling of progress. The psychologist Daniel Kahneman, in his work on how humans evaluate outcomes, has shown repeatedly that effort is used as a proxy for value — that people equate being busy with moving forward.³ In a business context, this translates to a culture where doing more is rewarded, even when it produces diminishing returns.

The third is that systems require coordination. Building a growth system means aligning marketing, sales, service, and operations around a shared logic. That is genuinely hard. It requires clarity about priorities, willingness to redesign processes, and the internal authority to make changes that cut across departments. Most businesses find it easier to add an activity than to redesign an architecture.

What Compounding Actually Requires

The businesses that scale without proportional increases in effort share a structural characteristic: their activities are designed to deposit into a cumulative asset.

A content programme that isn't connected to a lead intelligence system is an activity. The same programme, designed so that every piece of content tells you something about who engaged and why, which feeds into how you qualify and approach new prospects, which feeds back into what you write next — that is a system. The output of each cycle improves the input of the next.

The same logic applies to customer retention, pricing, sales processes, and operational delivery. In each case, the question is not "are we doing this?" but "does doing this make the next cycle better?"

The management theorist Peter Senge, whose 1990 work The Fifth Discipline introduced systems thinking to a mainstream business audience, described this as the difference between event-oriented thinking and structural thinking.⁴ Event-oriented thinkers ask: what happened, and how do we respond? Structural thinkers ask: what is the underlying design producing these events, and how do we change it?

Most businesses have no shortage of event-oriented thinkers. The rarer capability — and the more valuable one — is the ability to look at a growth problem and see the architecture beneath it.

A Diagnostic Worth Sitting With

If your growth requires roughly the same inputs every period to produce roughly the same outputs — if last quarter's revenue required roughly last quarter's effort — you are not running a system. You are running a treadmill.

That is not a judgment. Treadmills keep businesses alive. They produce revenue. They pay salaries. But they do not build towards anything. They do not get easier with time. And when something in the environment shifts — a channel becomes expensive, a competitor enters, a product needs updating — there is no accumulated advantage to draw from. You start from a similar position every time.

The businesses that navigate disruption most effectively are rarely those with the most resources. They are the ones, as the strategist Roger Martin has observed, that have built structural advantage — positions that are difficult to replicate precisely because they are the product of many connected decisions made over time, not a single clever move.⁵

That kind of advantage does not come from doing more. It comes from designing better.

In Closing

This is not an argument against effort. Hard work inside a good system is formidable. It is an argument against equating effort with strategy — against assuming that the answer to flat growth is more activity.

The most consequential question for any mid-sized business isn't "what should we be doing?" It is "what are we building, and does what we're doing today make tomorrow easier or harder?"

That question doesn't have a tactical answer. It has an architectural one.

References

1. The Innovator's Dilemma, Clayton M. Christensen, Harvard Business Review Press, 1997.
2. McKinsey & Company, The case for digital reinvention, McKinsey Quarterly, 2019.
3. Thinking, Fast and Slow, Daniel Kahneman, Farrar, Straus and Giroux, 2011.
4. The Fifth Discipline: The Art and Practice of the Learning Organisation, Peter M. Senge, Doubleday, 1990.
5. Playing to Win: How Strategy Really Works, Roger L. Martin & A.G. Lafley, Harvard Business Review Press, 2013.