The delivery ratio — are most of your people actually creating value?

The delivery ratio — are most of your people actually creating value?

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 does value actually come from?

Financial value (revenue) is created outside the organisation. A customer pays for a product. A service is delivered. An outcome is realised. That external transaction is the moment when the organisation's costs become revenue.

Everything inside the organisation is a 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.

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

The four categories

To answer that 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. Necessary, often genuinely so, but not directly connected to value creation.

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 uncomfortable pattern

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 value creation. At worst, it was actively slowing value down — adding layers of approval, generating reports that nobody acted on, creating meetings to coordinate the coordination.

This is not a people problem. The individuals in categories three and four are often talented, well-intentioned, and working hard. It is a system design problem. The organisation has accumulated a structure that serves its own internal coherence rather than its external purpose.

And the compounding effect is significant. The more layers added between an idea and the people building it, the slower value moves (and the more it costs). Decisions stall while they travel upward for approval. Priorities shift while they wait for alignment. Energy dissipates in the gap. Every additional layer of management adds cost not just directly — through salary — but indirectly, through the friction it creates in everything around it.

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 creating value are outnumbered by the people organising them.

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, 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 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. The organisation is spending more energy on itself than on the work. You have an Idea to Value problem, and it is structural.

The ratio is not a precise science. Some organising is essential — teams need coordination, work needs planning, complexity needs management. The question is not whether categories three and four exist but whether they have grown beyond what the delivery requires.

From control to flow

The shift is not about cutting management for the sake of it (ironically, in our experience, many people who were "building" the products found the reporting and governance overhead too demanding, so moved to an organising role out of need - and away from a direct value role). It is about reorienting the structure toward the work.

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 judgment 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 delivery (purpose of creating value) rather than substituting for it.

When you rebalance toward delivery and flow, 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.

Control feels safe. Delivery creates value. The organisations that confuse the two build elaborate systems for watching work — and lose the ability to do it.