# Measuring Delivery Capability: The Metrics of an Organization That Delivers

Author: Marin Niehues, Niehues Consulting · Published: 2026-05-04 · Updated: 2026-11-16 · Delivery & Steering
Source: https://www.niehuesconsulting.com/blog/delivery-capability-metrics/

You measure the delivery capability of an organization with five metrics: lead time, on-time delivery, first-time quality, work in progress and benefit realization. Together they show how quickly a decision takes effect in the market, how reliably commitments are met and how much of the planned benefit actually materializes. Every company records costs and revenue precisely. Hardly any executive team measures how long an initiative takes from approval to impact. This article sets out the five metrics with their formulas, explains the measurement logic and describes how the executive team turns them into a management rhythm.

## What does delivery capability mean for an organization?

Organizational delivery capability is the ability to implement approved initiatives within the committed time and quality so that the planned benefit reaches operations or the customer. Measurement starts at the result. A metric such as utilization answers whether people are busy. A delivery metric answers what has actually arrived.

In logistics, the same term means something else. There, delivery capability refers to service from stock, measured as the service level: the share of customer demand met immediately from available inventory. Logistics distinguishes the event-based alpha service level, which counts how many demands are met without a shortfall, from the quantity-based beta service level, also known as the fill rate, which measures the share of quantity delivered immediately. This article deals with organizational delivery capability, meaning how reliably a company translates decisions into results. Logistics metrics remain important in manufacturing and retail, yet they describe the flow of goods and leave the path of a decision through the organization out of view.

The difference from utilization has practical consequences. An organization with high utilization has many initiatives open at the same time, and each of them frequently waits for a decision, an input or an approval. Capacity is tied up and results arrive late. Anyone who wants to manage delivery capability therefore looks at the flow of work and at the waiting times in between. The article [characteristics and metrics of a high-performing organization](/blog/high-performing-organisation/) places this view within the wider picture of an organization that delivers.

## Which metrics show delivery capability?

Five metrics cover the path from decision to impact, and each has an unambiguous formula. Only the formula makes values comparable across divisions and quarters.

- Lead time: date of first use minus date of approval, per completed initiative.
- On-time delivery: initiatives delivered on time divided by all initiatives due in the period, times 100.
- First-time quality: deliveries accepted without rework divided by all accepted deliveries, times 100.
- Work in progress: the number of approved but unfinished initiatives on a given date, per team or division.
- Benefit realization: benefit measured after delivery divided by the benefit planned in the business case, times 100.

Each metric answers its own leadership question. Lead time shows the speed of the organization. On-time delivery shows whether commitments are reliable. First-time quality shows how much capacity flows into rework. Work in progress explains the cause of many delays and is the lever that management influences most directly. Benefit realization closes the loop, because it tests whether the delivery has redeemed the business case.

**Delivery capability only becomes visible when speed and reliability are viewed together with the impact on the customer. A single metric distorts the picture; the combination of all five shows where the organization loses delivery.**

The metrics can be collected at every level, from the individual team to the entire portfolio. At team level they serve to improve ways of working, at division level to manage capacity and priorities, at executive level to decide on investments. The article on [managing delivery performance](/blog/managing-delivery-performance/) covers on-time delivery and quality at team level and gives target values, and the article on [measuring team performance](/blog/team-performance-metrics/) adds metrics beyond utilization.

## Little's Law explains the biggest lever

Average lead time equals work in progress divided by throughput. The operations researcher John Little proved this relationship for stable systems in 1961. Twice as many open initiatives at the same throughput mean twice the lead time on average. A company that starts more initiatives than it completes therefore inevitably lengthens the average lead time of all its deliveries.

**Worked example: the effect of a WIP limit**
- Starting point: 40 approved initiatives are open, and the organization completes an average of 10 initiatives per month.
- Average lead time: 40 divided by 10 gives 4 months.
- Measure: the executive team caps work in progress at 20 initiatives and approves new work only when an initiative is completed.
- Result at the same throughput: 20 divided by 10 gives 2 months. Each initiative takes effect two months earlier on average, with no additional capacity.

The most effective single measure is therefore to limit the number of initiatives running at the same time, because it reduces lead time without requiring additional capacity. In Kanban this cap is called a WIP limit.

Flow efficiency shows where the time is lost. It relates the active working time on an initiative to its total lead time: active working time divided by lead time, times 100. An initiative that is under way for 30 working days and actively worked on for 6 of them has a flow efficiency of 20 percent. The remaining 80 percent is waiting for decisions, inputs or approvals. There is no reliable industry benchmark, because organizations record start, end and active time differently. For management purposes a clear rule applies: below 50 percent, most of the lead time is spent waiting, and the lever lies in decision paths and WIP limits. Working faster then does little to shorten lead time.

## Measurement logic: start, end and the 85th percentile

The metrics become meaningful through clean definitions. Three decisions determine whether the values are comparable and reliable.

First, every metric needs an unambiguous start and end point. For lead time, the clock starts with approval by the deciding body and stops with the first actual use, regardless of interim internal milestones. This framing makes visible what a customer experiences, and it exposes waiting times that remain hidden in team statistics.

Second, the mean says little about an organization whose initiatives vary widely. The median and the 85th percentile of lead time are more informative. The 85th percentile is the time span within which 85 percent of completed initiatives were finished. If it stands at twelve weeks, the organization can commit to twelve weeks with high reliability. The gap between the median and the 85th percentile shows how well the organization can plan. Where the 85th percentile is less than twice the median, commitments are well plannable. Above that, the spread points to disruptions in the workflow that need resolving before any targets are set.

Third, every value needs a benchmark. The most effective benchmark is the organization's own development over several quarters. External comparison values serve as orientation when industry and type of initiative correspond and measurement points are defined identically, and that correspondence can rarely be demonstrated.

**Checklist for defining a metric**
- Which event starts the measurement, and who confirms it?
- Which event ends it, and where is it recorded?
- Which initiatives are included, and which are excluded?
- Who is responsible for data quality, and how often is it checked?

## How does an executive team introduce the measurement?

The executive team introduces the measurement in three stages: establish the baseline, set target ranges, embed the rhythm. Measured values change an organization only when they are built into a fixed rhythm of decision-making.

The first stage is the baseline. The organization collects the five metrics for a defined area over six to eight weeks and records where data is missing or inconsistent. This inventory alone exposes bottlenecks. The article on [bottlenecks in value creation](/blog/finding-bottlenecks-in-the-value-chain/) describes a method for finding them.

In the second stage, management sets target ranges and measures. Target values derive from the baseline and the market requirement. The WIP limit comes first, supplemented by clear decision paths that shorten waiting times.

The third stage is the rhythm. The metrics appear in a fixed report that is discussed monthly by the executive team and weekly in the divisions. Every deviation triggers a defined response: clarify the cause, set a measure, check the effect in the next cycle. This turns a measurement into a management instrument.

**Management approaches compared**
Criterion | Management by utilization | Management by delivery metrics | With Niehues Consulting
Leadership focus | Occupation of teams | Impact with the customer and in operations | Metrics with decision logic for the executive team
Typical result | Many open initiatives, long waiting times | Limited work in progress, short lead time | WIP limit and decision paths with a fixed rhythm
Statement on commitments | Low | On-time delivery and the 85th percentile evidence reliability | Commitments based on measured distributions
Link to the business case | Loose | Benefit realization closes the loop | Benefit as a management variable from business case to impact

## Niehues Consulting as a partner for delivery metrics

[Niehues Consulting](/) supports executive teams and division heads in measuring the delivery capability of their organization and raising it in a targeted way. The delivery perspective is central: what must an organization do so that a decision actually arrives and works. In delivery management and organizational design, Niehues Consulting defines the measurement points and organizes roles and decision paths. As delivery manager, project manager or product owner, Marin Niehues takes on the management of initiatives himself and anchors the metrics in day-to-day business.

The approach follows the Niehues Delivery Model with its phases Understand, Build and Introduce. Three of its review questions matter most for delivery metrics. In the Understand phase: what is the baseline, and how do we measure success? In the Build phase: which roles, decision paths and interfaces do operations require? In the Introduce phase: which metric shows after 90 days that the solution is landing? Marin Niehues works on projects from VC-funded scale-ups to DAX 40 corporations and has been deployed in 20+ countries on six continents. The free initial consultation lasts 30 minutes and clarifies which metrics will yield the greatest insight for your organization: [book an initial consultation](/#kontakt).

**What decision-makers should take away**
Five metrics make visible whether an organization delivers, from lead time to benefit realization. They work when definitions are unambiguous, the median and 85th percentile are reported instead of means and a fixed rhythm translates deviations into decisions. The biggest lever is limiting the number of initiatives open at the same time.

**Sources**
- Little: A Proof for the Queuing Formula L = λW, Operations Research, 1961

## Frequently asked questions

### What metrics measure an organization's delivery capability?

Five metrics cover the path from decision to impact: lead time, on-time delivery, first-time quality, work in progress and benefit realization. Together they show the speed and reliability of the organization as well as its impact on the customer.

### What does delivery capability mean in logistics, and how is it different?

In logistics, delivery capability means service from stock, measured as the service level or fill rate, that is the share of demand met immediately from inventory. Organizational delivery capability measures how quickly and reliably a company turns approved initiatives into impact. Both views complement each other in manufacturing and retail, yet they answer different leadership questions.

### How do you measure lead time correctly?

Measurement begins with approval by the deciding body and ends with first use by the customer or the business unit. The median is reported together with the 85th percentile. The gap between the two shows how well the organization can plan.

### What is the 85th percentile of lead time?

The 85th percentile is the time span within which 85 percent of completed initiatives were finished. It is a sound basis for commitments, because it accounts for the spread of initiatives. A mean conceals this spread and therefore regularly leads to deadlines that are too tight.

### What is flow efficiency, and what is a typical value?

Flow efficiency is the share of active working time in the total lead time of an initiative. There is no reliable industry benchmark, because organizations record active time differently. What counts is your own baseline: below 50 percent, most of the lead time is spent waiting, and that is where management should intervene.

### What is Little's Law?

Little's Law states that average lead time equals work in progress divided by throughput. Halving work in progress at the same throughput halves lead time on average. The relationship applies to averages in a stable system.

### What is the difference between utilization and delivery capability?

Utilization indicates how busy employees are, while delivery capability indicates what arrives with the customer, in what time and at what quality. High utilization frequently goes together with many open initiatives and long waiting times. Both lengthen lead time.

### How should an executive team start measuring delivery?

The entry point is a defined area for which the five metrics are collected over six to eight weeks. From the baseline, management derives target ranges and sets a fixed reporting rhythm. The method can then be extended to further areas.
