One question I’ve heard repeatedly from managers moving towards agile ways of working is this:
“But what happens if someone finishes their task early?”
On the surface, it sounds like a practical concern.
Underneath, it’s often something else entirely.
What’s really being expressed is anxiety about visibility, value and safety in an uncertain system.
Over time, I’ve come to see this as a clash between two different value systems.
The traditional management model
In many organisations, the implicit model looks like this:
- Value = people always being busy
- Risk = idle time
- Safety = visible activity
- Control = assigning work
In this world, a person without a task looks like a problem.
Busyness becomes a proxy for productivity, and visible motion feels reassuring.
This model makes sense in environments where:
- work is tightly scoped
- accountability is individual
- scrutiny comes from above
- mistakes are punished more than learning is rewarded
The agile model
Agile and flow-based working quietly invert those assumptions:
- Value = finished work
- Risk = work in progress
- Safety = shared responsibility
- Control = system constraints
Here, the danger isn’t that someone finishes early.
The danger is having lots of half-done work that never quite makes it over the line.
“You can’t ship in-progress,” as someone put it.
When someone completes their part of a task, the highest value activity is often not pulling new work, but:
- helping someone else finish
- QAing or sense-checking
- pairing or unblocking
- reducing risk before it materialises
From the outside, that can look like “less activity”.
In reality, it’s how quality and predictability improve.
Why this tension keeps resurfacing
Until this difference in value systems is named, managers will keep circling back to “but what if someone finishes early?”
Not because they don’t understand agile concepts, but because busyness has historically kept them safe.
In psychologically unsafe environments, visible utilisation feels like protection. Slack feels risky. Stillness feels exposed.
The shift that actually helps
The real shift isn’t from ‘assigning work’ to ‘doing Scrum properly’.
It’s from managing people’s time to managing the flow of work.
When the focus moves to:
- finishing rather than starting
- reducing WIP (work in progress)
- making quality a team responsibility
…the pressure to keep everyone constantly busy starts to ease.
And paradoxically, delivery becomes calmer, faster and safer.
A question worth sitting with
If someone finishing early makes us anxious, what does that say about the system we’re asking them to work in?
