The delivery ratio — where is your structure actually pointing?

I once worked with a client who had a delivery problem. Work wasn't moving. Value wasn't reaching customers. Leaders were frustrated. They had talented people, reasonable budgets, and no shortage of activity.

So I suggested a simple audit — not of people, but of roles.

Where financial value actually comes from

Financial value — the money that keeps the business alive — is generated outside the organisation. A customer pays for something worth paying for. An outcome is realised. That external transaction is the moment the organisation's costs are matched by incoming revenue.

Everything inside the organisation is cost until that moment. Every salary, every meeting, every dashboard, every governance process exists in service of the activity that eventually reaches the customer and creates something worth paying for. (The full argument for why this asymmetry matters sits in a companion piece — The only money that matters is someone else's — which is the natural read before this one if you haven't already.)

This framing matters because it forces a question most organisations never ask directly: how many of our people are working on the thing that directly generates financial value — and how many are working on everything else?

All four categories produce value. The ratio is a different question.

Before going any further, one thing needs naming clearly.

Every category of role inside an organisation produces real value. Building produces financial value directly. Supporting enables it. Organising structures the work that produces it. Administration keeps the business operating. Nobody reading this piece should feel their work doesn't count. It does. All four categories matter, and organisations cannot function without all four.

The delivery ratio is not asking which categories count. It is asking a different, structural question: has the proportion of people whose work directly touches the external transaction — the thing a customer pays for — drifted too far from the proportion needed to keep the business funded?

That is a question about organisational shape. Not about personal contribution.

The four categories

To answer the ratio question, I group every role in an organisation into four categories.

The first category is people who build the product or service — the work that directly creates what customers pay for. Engineers, designers, writers, consultants, craftspeople. The people whose output is the thing itself.

The second is people who support delivery — customer care, pre-sales, operations, technical support. They do not build the core product, but they are essential to getting it to customers and keeping it working once it arrives.

The third is people who organise other people and their work — managers, coordinators, project managers, programme leads, planning teams. Their output is not the product; it is the organisation of the people producing it.

The fourth is administration — finance, reporting, legal, compliance, back-office functions. Genuinely necessary and producing real enablement value — but not directly connected to the external transaction.

This is not a people problem, and it is not a hierarchy of worth. It is a structural observation. The individuals in every category are usually talented, well-intentioned, and working hard. What the ratio reveals is not whether those individuals are doing good work. It is whether the shape of the organisation — the proportions — is pointed at value creation or at something else.

The pattern in large organisations

In healthy, growing organisations — startups, small teams, companies still close to their purpose — most people sit in categories one and two. The ratio makes intuitive sense. The organisation is lean in the direction of the work.

In large, established organisations, the numbers often invert. Categories three and four grow. Categories one and two shrink as a proportion of headcount. The organisation becomes, by slow accumulation, more focused on organising and reporting the work than on doing it.

The breakdown I found in that client's organisation was not unusual. Roughly twenty percent of people were building the product. Ten percent were supporting delivery. Sixty percent were organising people and work. Ten percent were in administration.

Most of the salary bill was being spent on work that was, at best, one or two steps removed from the activity that produced financial value. Some of that organising work was genuinely necessary — large organisations need coordination, planning, and alignment. But the ratio had drifted far beyond what the delivery required, and the effects were everywhere: decisions stalled while they travelled upward for approval, priorities shifted while they waited for alignment, energy dissipated in the gap between ideas and the people who could build them.

Every additional layer between an idea and the people building it adds cost — not just directly, through salary, but indirectly, through the friction it creates in everything around it.

The people doing the organising were often the builders

One pattern worth naming explicitly, because it changes how the whole ratio should be read.

In my experience, many of the people now in organising and administering roles were originally building. They were engineers, designers, writers, practitioners. They did the work directly. Then, as the organisation grew, the reporting demands grew. The governance expanded. The coordination overhead compounded. And at some point, they stopped building because the weight of everything around the building became too much to carry alongside the craft itself.

Most of them would rather be building again.

This is not a criticism of the people now organising. It is an observation about the structural pressure that organisations exert on their best builders — pulling them out of the work they chose and into the work that someone had to do as the organisation scaled. The ratio problem is often the consequence of that pressure, not a failure of judgement by the people involved.

It is also why the question is structural, not personal. No individual chose to create the ratio. The ratio accumulated.

Why this happens

Organisations do not set out to become top-heavy. They become that way through a series of individually reasonable decisions that are collectively unreasonable.

A manager is hired to handle a growing team. That manager eventually gets their own manager. A programme becomes complex enough to warrant a programme office. A project office spawns a portfolio office. Compliance requirements generate reporting requirements, which generate analyst roles to produce the reports, which generate management time to review them.

Each decision makes local sense. The cumulative result is an organisation where the people directly generating financial value are outnumbered by the people organising and supporting them — and often by a wide margin.

Control feels productive because it is visible. Dashboards, governance meetings, status reports — these produce artefacts that can be pointed to. Delivery, especially creative or complex delivery, often feels uncertain and messy. The instinct of leadership is often to resolve that uncertainty with structure. And structure, in organisations, usually means management.

What often gets built instead is what we call Watermelon Reporting — green on the outside, red on the inside. The governance systems designed to surface problems instead produce the appearance of control, while the actual delivery deteriorates beneath the surface.

Running the audit

The diagnostic is simple.

List every role in your team, department, or organisation. Assign each one to a category: building, supporting, organising, or administering. Count the ratio.

If most people are in categories one and two — your structure is pointed toward the work that directly generates financial value. The organisation is doing what it exists to do, with appropriate support and organisation around it.

If most people are in categories three and four — your structure is pointed toward control and coordination rather than toward the external transaction. The organisation is spending more energy on itself than on the work that funds it. You have an Idea to Value problem, and it is structural.

The ratio is not a precise science, and no single number is universally correct. Some organising is essential. Some administration is load-bearing. Complex delivery genuinely requires planning, coordination, and governance. The question is not whether categories three and four exist. It is whether they have grown beyond what the delivery actually requires — and whether the organisation is honest enough with itself to ask the question.

From control to flow

The shift is not about cutting anything for the sake of it. Most of the people now organising are there because something in the system pulled them out of building — and many would rather be back in the work. The shift is about reorienting the structure so the pressure that pulled them out of building is relieved.

That means starting with clarity — a compelling shared direction that makes organising easier because everyone already knows what they are working toward. It means identifying the problems that are slowing delivery and removing them, rather than adding more management to work around them. It means delegating genuine responsibility to the people closest to the work, training their judgement rather than replacing it with approval processes.

Oversight still matters. Accountability still matters. The goal is not an organisation without structure — it is an organisation where structure serves the work of generating value rather than substituting for it.

When the ratio rebalances, work moves faster. Customers feel it. The organisation becomes lighter and more capable of responding to what is actually happening rather than what the dashboards say is happening. Many of the people who had been organising find their way back to building, which is often where they wanted to be all along.

The close

Control feels safe. It produces visible artefacts and tells leaders what they want to hear. It also produces real enablement value — organisations need structure, and some of that structure is load-bearing.

But only the work that reaches a customer produces the financial value that funds everything else. The organisations that confuse the two — that mistake the visibility of control for the evidence of value — build elaborate systems for watching work, and lose the ability to do it.

The ratio is a mirror. It tells you where your structure is actually pointing — and whether the shape of the organisation is the shape you meant to build.