# Lean Management in Knowledge Work

Author: Marin Niehues, Niehues Consulting · Published: 2026-08-06 · Updated: 2026-11-16 · Delivery & Steering
Source: https://www.niehuesconsulting.com/blog/lean-management-knowledge-work/

Lean management in knowledge work means making work visible, limiting work in progress and steering flow instead of utilization. The concept comes from Toyota's production system and follows the same laws in finance, sales, procurement or project work. There, delays arise mainly from waiting time between steps. This article shows how executive management measures that waiting time, assesses it with a worked calculation and shortens it in a targeted way.

## What are the five lean principles?

The five lean principles are value, value stream, flow, pull and perfection. James Womack and Daniel Jones derived them in their 1996 book “Lean Thinking” from the Toyota Production System, which Taiichi Ohno had built up from the 1950s onwards.

Translated into knowledge work, the principles mean the following:

- Value: what the internal or external customer actually needs, such as an approved costing or a signed contract.
- Value stream: every step from the receipt of a request to the delivery of the result, including the time items sit idle.
- Flow: an item passes through the steps without interruption and without queries.
- Pull: new work starts only when the next stage has free capacity.
- Perfection: a fixed rhythm in which the team reviews and improves the workflow.

On a factory floor you can see material piling up in front of a machine. In knowledge work the pile-up stays invisible, because it consists of emails and open decisions as well as half-finished drafts. That is why lean has such a large lever there: most organizations do not know how long an item sits before anyone works on it.

## What is lean office?

Lean office is the application of lean principles to administrative and indirect functions such as finance, HR, procurement or project organization. In substance it covers the same ground as lean management in knowledge work.

The difference lies in emphasis. Lean office programs often begin with workplace organization and process standards, for instance applying the 5S method to digital folders. Lean management in knowledge work starts with the flow of items: how many requests are open at once, how long do they sit, and where do they queue? For functions with many similar items, such as invoice checking or contract approvals, both approaches pay off. For project work and analyses with highly varied items, flow management brings the larger gain.

## What types of waste exist in the office?

The office shows the same seven types of waste that Taiichi Ohno described for manufacturing, plus an eighth: the unused skills of employees. Jeffrey Liker added this eighth type in “The Toyota Way” in 2004. The following mapping serves as a test grid for knowledge work.

**Checklist: The eight types of waste in the office**
- Overproduction: reports and analyses that nobody reads.
- Waiting: a draft sits with the decision-makers until a slot becomes free.
- Transport: handovers between units, each with queries and loss of information.
- Over-processing: rounds of alignment and approvals that do not improve the result.
- Inventory: many started items that tie up attention without delivering value.
- Motion: searching for files, switching between systems, switching context between tasks.
- Defects: rework caused by unclear requirements or outdated data.
- Unused skills: specialists keying in data instead of preparing decisions.

Waiting accounts for the largest share. Measurements of flow efficiency in knowledge work regularly show that an item spends by far the greater part of its lead time waiting and only a small fraction being worked on. Targeting improvement where work sits therefore achieves more than pushing the people doing it. The article [Finding bottlenecks in value creation](/blog/finding-bottlenecks-in-the-value-chain/) covers which points in a workflow create these queues.

## Why does high utilization lengthen lead time?

High utilization lengthens lead time because every additional item lands in a queue, and waiting time grows disproportionately as utilization rises. Two results from queueing theory demonstrate this.

The first is Little's Law. In 1961 John Little proved that in a stable system, on average, lead time equals work in progress divided by throughput. At constant throughput, every additional task started lengthens the lead time of all the others.

The second concerns utilization. In the simplest queueing model, the average waiting time before processing equals utilization divided by spare capacity, multiplied by processing time. John Kingman showed in 1961 that the same effect holds in general queues and is amplified by variable arrivals and processing times. Knowledge work varies strongly, so the effect is particularly pronounced there.

**Worked calculation: lead time and utilization**
Little's Law: a team has 60 open items and completes an average of 20 per week. Lead time is 60 divided by 20, so three weeks. If the team caps open items at 30 and holds throughput, lead time falls to one and a half weeks.

Utilization: an item needs one day of processing. At 50 percent utilization it waits one day on average (50 divided by 50). At 80 percent it waits four days (80 divided by 20), at 90 percent nine days, at 95 percent 19 days.

Question for executive management: how many items are open in your area at the same time, and how many are actually completed each week?

**Exhibit 1 (Schematic): Above 80 percent utilization waiting time jumps, at 95 percent to nineteen times the processing time**

| Label | Value |
| --- | --- |
| 50% utilization | 1 day |
| 80% utilization | 4 days |
| 90% utilization | 9 days |
| 95% utilization | 19 days |

Schematic illustration, not measured data.
Source: Worked example in the article
Source: Approximation after Kingman, 1961
Note: Average waiting time of an item with one day of processing
Graphic: [SVG](https://www.niehuesconsulting.com/blog/lean-management-knowledge-work/grafik-1.svg) · [CSV](https://www.niehuesconsulting.com/blog/lean-management-knowledge-work/grafik-1.csv) · [JSON](https://www.niehuesconsulting.com/blog/lean-management-knowledge-work/grafik-1.json) · Niehues Consulting, [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/deed.en). Data: Approximation after Kingman, 1961; the source's terms apply.

A team that is fully booked has no room for deviations and pushes every disruption into the following week. A calculated reserve is therefore the precondition for reliable deadlines. Planning utilization at around 80 percent keeps waiting time in the calculation at four times the processing time instead of nineteen times.

**Lead time falls when less work runs at the same time. Executive management steers flow, and utilization follows from it.**

**Steering utilization or flow**
Criterion | Steering by utilization | Steering by flow | With Niehues Consulting
Guiding question | Is everyone fully occupied? | How fast does an item get through? | Which business outcome should change through shorter lead time?
Metric | Utilization rate per person | Lead time, flow efficiency, on-time delivery | Lead time with baseline and target value after 90 days
Handling new requests | Every request is accepted | New work starts when capacity is free | WIP limits per stage, prioritization by a named role
Effect on deadlines | Long and volatile lead times | Short and predictable lead times | Predictable deadlines, proven on real items
Suitable when | Work is uniform and plannable | Items pass through several stages | Several units are involved and delivery is to improve measurably

## What is the difference between lean and kanban?

Lean is the overarching management philosophy, while kanban is a method for putting lean principles into practice in knowledge work. Lean describes what an organization should focus on: value, flow and the avoidance of waste. Kanban describes how a team actually manages flow.

At Toyota, kanban was originally a card used as a replenishment signal, implementing the pull principle in manufacturing. In his 2010 book “Kanban”, David Anderson turned it into a method for knowledge work. Its core practices are: make work visible, limit work in progress and thereby create a pull system, manage flow, make policies explicit and improve collaboratively at regular intervals. Introducing kanban therefore means implementing lean. Introducing lean means using kanban as one of several tools, alongside value stream mapping and standard work.

## Four levers to start with

The start succeeds with four measures that build on one another in this order.

- Make work visible: every item appears on a board, organized by the stages of the workflow.
- Set a WIP limit: each stage has a fixed ceiling for simultaneous items (WIP stands for work in progress).
- Pull instead of push: a new item starts only when capacity becomes free at the next stage.
- Improve regularly: a fixed rhythm in which the team reviews lead time and queues.

The WIP limit has the greatest impact. A sound starting value is the number of people in a stage multiplied by one to two. After four to six weeks the team adjusts the value on the basis of measured lead time. The limit forces leadership to set priorities instead of accepting every request. Whoever reaches the ceiling either finishes something or decides deliberately what waits. A diffuse sense of overload becomes a visible decision.

## What executive management should measure

Lean in knowledge work needs four metrics that business units can collect themselves.

- Lead time: the time between receipt and completion of an item.
- Flow efficiency: the share of lead time in which work is actually done on an item.
- Items in progress: how much work is open at the same time.
- On-time delivery: the share of items completed by the promised date.

Together these measures give a picture of delivery capability. A sample is enough for flow efficiency: the team records, for 20 completed items, the days of actual processing and divides them by lead time. How the measures fit into a steering system is shown in the article [Steering delivery performance](/blog/managing-delivery-performance/). An analysis by unit reveals at which handovers time is lost. The overall framework of structure and delivery is set out in the article [characteristics and metrics of a high-performing organization](/blog/high-performing-organisation/).

## Introduction as an organizational initiative

The tools are simple, but introduction touches habits. Whoever used to answer every request now sets priorities, and whoever saw utilization as proof of performance is measured on results. Introduction therefore starts with responsibilities and decision paths and complements them with training. A pilot area of 8 to 15 people with a clearly defined item type delivers robust before-and-after figures within eight to twelve weeks.

[Niehues Consulting](/) supports lean introductions in knowledge work using the Niehues Delivery Model with its phases understand, build and introduce. Three test questions decide success. At the outset: which business outcome should change measurably, such as the time to quote or to month-end sign-off? Next: what is the baseline lead time, and how will success be measured? At the close: which metric shows after 90 days that the new workflow has taken hold? With these questions the value stream of a unit is mapped, a pilot is built on real items, and operations are designed with clear roles and WIP limits so that the unit delivers reliably. The entry point is the [free 30-minute initial consultation](/#kontakt).

**What decision-makers should take away**
Lean in knowledge work steers the flow of work. Make items visible, limit simultaneous work with WIP limits and measure lead time and flow efficiency. This shortens waiting times without additional capacity and makes deadlines reliable.

**Sources**
- Anderson: Kanban. Successful Evolutionary Change for Your Technology Business, Blue Hole Press, 2010
- Kingman: The single server queue in heavy traffic, Proceedings of the Cambridge Philosophical Society, 1961
- Liker: The Toyota Way, McGraw-Hill, 2004
- Little: A Proof for the Queuing Formula L = λW, Operations Research, 1961
- Womack, Jones: Lean Thinking, Simon & Schuster, 1996

## Frequently asked questions

### What does lean management mean in knowledge work?

Lean management in knowledge work means looking at work from the standpoint of customer value and shortening everything that delays that value. These are mainly waiting times and handovers. The tools are a visible work board and WIP limits, combined with a regular rhythm of improvement.

### What is the difference between lean and kanban?

Lean is a management philosophy and kanban is a method for implementing it. Lean sets out the five principles from value to perfection. Kanban puts them into practice in a team with a board, limits on work in progress and explicit policies.

### What is lean office?

Lean office is the application of lean principles to administration and indirect functions. Typical starting points are process standards and shorter approval loops. The largest lever is limiting the number of items open at the same time.

### How do you set a WIP limit?

A WIP limit starts at the number of people in a stage multiplied by one to two. Once the limit is reached, a new item starts only when another has been completed. After four to six weeks the team adjusts the value based on measured lead time.

### Which metrics show whether lean works in knowledge work?

Lead time, flow efficiency and on-time delivery are the informative metrics. In addition, the number of items in progress shows whether the WIP limit is taking hold. If lead time falls at constant throughput, the improvement is proven.

### What is Little's Law?

Little's Law is a relationship from queueing theory that John Little proved in 1961. In a stable system, on average, lead time equals work in progress divided by throughput. For management this means that less simultaneous work at constant throughput shortens lead time.

### Is lean suitable for functions outside IT?

Yes, lean suits any function in which items pass through several stages. Examples include invoice checking or contract approvals. The precondition is that the workflow can be described and every item can be shown on a board.

### How long does it take to introduce lean in a unit?

A pilot unit shows robust before-and-after figures after eight to twelve weeks. The first four weeks are used to measure the baseline and set up the board, after which WIP limits and the improvement rhythm take effect. Roll-out to further units then follows one unit at a time.
