What an Aging Breach Is Really Telling You

In Kanban systems, aging is often misunderstood.

Teams notice work items getting “old,” discussions follow, and attention turns to explanations: blockers, dependencies, unexpected complexity.

But aging is not just a symptom.

An aging breach is a diagnostic signal.

It tells you something very specific about the system.

Aging Is a Leading Indicator, Not a Failure Signal

When work exceeds its expected time in progress—its Service Level Expectation (SLE)—the system has moved outside its normal operating range.

That matters because:

  • Late discovery removes options

  • Risk compounds silently

  • Governance becomes reactive instead of corrective

Aging surfaces problems before delivery failure. That is its value.

What Causes an Aging Breach?

In practice, aging breaches almost always trace back to one (or more) of four causes.

1. Too Much Work Was Pulled Relative to Capacity

The most common cause is simple overload.

More work was admitted than the system could realistically complete.
As WIP increased, cycle time increased with it.

This is not a people problem.
It is a violation of admission control.

2. Capacity Was Displaced by Unplanned or Higher-Priority Work

Interrupts, expedites, or urgent requests consumed capacity that was already committed.

From a flow perspective, this is still overload.

WIP effectively increased without reducing existing commitments.

3. An Unforeseen Dependency Materialized

External approvals, shared services, integration constraints, or environmental issues blocked progress.

Aging reveals these dependencies early, while corrective action is still possible.

Late discovery would have turned a dependency into a delivery failure.

4. The Work Item Was Too Large or Poorly Shaped

Hidden scope, unclear acceptance criteria, or late discovery of complexity expanded the effective batch size.

This is not “bad estimation.”

It is bad work design.

The Common Thread

Across all four causes, the root issue is the same:

Work was admitted under assumptions that were no longer valid.

That is why aging is the correct trigger for action.

Not because someone failed —
but because the system needs correction.

Why This Matters

Organizations often respond to lateness by:

  • Replanning

  • Adding coordination

  • Increasing oversight

None of these address the cause.

Aging breaches point upstream, to:

  • Admission control

  • WIP limits

  • Capacity assumptions

  • Work sizing

Fixing those restores flow.

Closing Thought

Aging does not exist to explain delays.

It exists to prevent them.

When you treat aging as a control signal—rather than a performance metric—you stop asking “why is this late?” and start asking the far more useful question:

“Why did we start this when we did?”

That question is where real improvement begins.

Scroll to Top