May 19, 2026
5 min read
Flow metrics
Arrival Rate vs Throughput
The difference between arrival rate and throughput, and why teams that ignore the gap between them often end up feeling permanently overloaded.
Why this comparison matters
Teams often talk about overload as if it were mysterious. In many systems, it is not mysterious at all. It is the predictable result of work entering faster than finished work is leaving.
That is why arrival rate versus throughput matters. It gives overload a clearer system shape instead of leaving it as a vague feeling of permanent pressure.
Balance check
Arrival rate versus throughput tells you whether the system is taking in work faster than it finishes it.
Intake pressure
Trouble starts when new work enters faster than the team can complete it for any meaningful stretch of time.
Backlog and WIP grow
The system begins carrying more unfinished work, which usually makes flow less stable and less trustworthy.
Throughput stays flat
Teams often feel busy under this pattern even though the rate of actual finished work does not improve.
Instability follows
Queueing, overload, and longer waits usually appear once intake pressure outpaces real delivery capacity.
Balanced flow
A healthier system either finishes more work or admits less new work so the flow can stay believable.
What arrival rate actually shows
Arrival rate measures how quickly work enters the system. That includes planned work, interrupts, defects, support tasks, and anything else the team accepts into active flow.
It is the intake side of the system. If the team keeps allowing new work in faster than it can finish current work, pressure will build even if nobody explicitly names the cause.
What throughput actually shows
Throughput measures how quickly finished work exits the system. It is the outflow side: what the team actually completes over time.
That makes throughput useful for understanding real finishing capacity instead of optimistic intake habits.
What the imbalance looks like
When arrival rate stays higher than throughput for long enough, the result is predictable. WIP grows, ageing items increase, blocked work becomes harder to clear, and priorities become noisier because too many things compete for movement at once.
- WIP rises faster than it drains.
- Old items linger longer.
- Context switching increases.
- The team feels permanently behind even while staying busy.
What teams can do about it
The usual answer is not working harder. It is reducing intake pressure, tightening priority discipline, or improving how work is sliced and finished so throughput can stay healthier relative to demand.
The system needs balance more than it needs motivational speeches.
TL;DR
- Arrival rate is how fast work enters the system.
- Throughput is how fast finished work leaves it.
- If arrival stays above throughput for long, overload is the predictable result.
- The symptoms usually show up as rising WIP, ageing work, and noisier priorities.
- Arrival rate versus throughput is a simple but powerful check on whether the system is absorbing work or quietly drowning in it.