3 min read

You Do Not Have a Delivery Problem. You Have a Decision System Problem.

When execution slows down, the reflex is almost always the same: increase pressure, add tracking, introduce new rituals, and ask for more alignment. Yet very little of this addresses the root cause, because delivery is not where problems start. It is where they become visible.
You Do Not Have a Delivery Problem. You Have a Decision System Problem.

Most organisations do not have a delivery problem. They have a decision system problem.

1. The Illusion of a Delivery Problem

When execution slows down, the reflex is almost always the same: increase pressure, add tracking, introduce new rituals, and ask for more alignment.

Yet very little of this addresses the root cause, because delivery is not where problems start. It is where they become visible.

Upstream, something else is happening. Teams wait more than they build, decisions are delayed or revisited, and ownership becomes progressively blurred. What should be a clear direction turns into a chain of approvals, dependencies, and negotiations, each adding a small but cumulative cost.

From the outside, it looks like a delivery issue. From the inside, it feels like friction.

Execution degrades when decisions do.

2. When Decision Systems Are Not Designed

In many organisations, the decision system is not intentionally designed. It emerges through habit, pressure, and local optimisation.

Authority is distributed without clarity, accountability is shared without ownership, and decisions are pushed upward for safety before being pushed downward for execution.

The result is rarely dramatic at first. Decisions take slightly longer, or arrive slightly later than needed. Over time, however, they become too large to adjust safely, or too diffuse for anyone to be truly accountable.

In response, teams compensate. They introduce alignment loops, checkpoints, and additional communication to reduce uncertainty.

Each of these mechanisms adds latency, until coordination gradually replaces decision as the primary driver of execution.

3. Recognising a Weak Decision System

A weak decision system rarely announces itself. It reveals itself through patterns that become visible only when they accumulate.

Ownership is unclear where decisions should be made, and authority does not match responsibility. Teams escalate what should remain local, while leaders decide without proximity to the problem.

Trade-offs remain implicit, which makes alignment fragile and reversible. Decisions are treated as isolated events rather than as part of a coherent system.

The consequences are structural. Execution slows, roadmaps become unstable, and trust erodes between teams. Performance becomes increasingly unpredictable, not because effort decreases, but because clarity does.

4. Why Fixing Delivery Does Not Work

At this stage, organisations often attempt to fix delivery directly. They introduce new frameworks, reorganise teams, or redefine processes. These interventions can create temporary momentum, but they rarely hold if the decision system remains unchanged.

Delivery is downstream of decisions. If decisions are slow, execution slows. If they are unclear, execution drifts. And when decisions are too large, execution becomes inherently risky, regardless of the effort applied.

Improving speed does not begin with doing more. It begins with deciding better.

5. What Strong Decision Systems Look Like

Strong decision systems are characterised by clarity and proportion. Ownership is explicit, and decisions are taken where the information resides.

Authority and responsibility are aligned, which reduces the need for escalation and reinforces accountability at the right level.

Trade-offs are made visible, allowing decisions to be understood, challenged, and adjusted when needed. Most importantly, decisions are kept small enough to remain adaptable. Reversibility is not an afterthought but a design principle.

A system that cannot adjust accumulates risk silently, until it reaches a point where change becomes both necessary and dangerous.

6. From Effort to Clarity

This perspective changes how organisations operate. Instead of seeking perfect alignment, they prioritise clear ownership and timely decisions.

Large, infrequent decisions give way to smaller, continuous ones, reducing both risk and inertia.

Rather than pushing decisions upward, organisations enable them downward, closer to where information and context exist. Speed then emerges as a by-product. Not of increased effort, but of reduced friction and improved clarity.

7. Signals from Organisations That Got This Right

Some organisations did not begin by optimising delivery. They first clarified how decisions should be made.

Amazon distinguished between reversible and irreversible decisions, allowing speed where it was safe and control where it was necessary.

Toyota aligned decision authority with proximity to the problem, ensuring that issues could be addressed immediately rather than escalated.

Netflix reduced approval layers by replacing control with context, enabling faster and more accountable decisions.

In each case, performance improved not because people worked harder, but because decisions became clearer, faster, and better placed.

8. Final Thought

You cannot scale execution if you cannot scale decisions.

Until decisions scale, nothing else truly does. This perspective changes how organisations operate. Instead of seeking perfect alignment, they prioritise clear ownership and timely decisions.

Large, infrequent decisions give way to smaller, continuous ones, reducing both risk and inertia.

Rather than pushing decisions upward, organisations enable them downward, closer to where information and context exist.

Speed then emerges as a by-product. Not of increased effort, but of reduced friction and improved clarity.