Work enters faster than it leaves
Incoming work volume consistently outpaces completion, so queues, context switching, and churn grow silently.
- Where you see this
growing teamsmatrixed organizationsstakeholder-heavy environments
- Not necessarily a problem when
- a deliberate short-term surge is being buffered and explicitly managed
- Often mistaken for
- a bigger backlog means stronger demand and therefore health
- Time horizon
- near-term
- Best placed to act
managerproduct leadportfolio owner
The signal
What you would actually notice
Unbounded intake creates hidden delay, quality erosion, and loss of focus.
Field observation
Backlogs expand, WIP grows, priorities churn, and teams feel busy without feeling done.
Also observed
- We finished a lot, but the board still looks worse.
- We keep adding work faster than we can close it.
Primary reading
What it usually indicates
Most likely underlying patterns when this signal shows up. Not a diagnosis, a starting hypothesis.
Usually indicates
Most likely underlying patterns when this signal shows up.
- weak intake discipline
- too many priorities
- underestimated dependency cost
- work decomposition problems
Stakes
Why it matters
Unbounded intake creates hidden delay, quality erosion, and loss of focus.
Inspection
What to check next
Deliberate steps to confirm or disconfirm the primary reading above. Not a checklist. An order of inspection.
- WIP levels
- cycle time trends
- queue age
- intake paths
Diagnostic questions
Questions to ask the team, or yourself, before concluding anything.
- Who controls intake?
- Which work is entering without displacing other work?
- Are we underestimating how long work truly stays open?
Progression
Under the signal
Where this pattern tends to come from, what's holding it up, and where it goes if nothing changes.
Leading indicators
What tends to show up first.
- backlog grows despite strong effort
- people carry too much WIP
- interruptions routinely displace in-flight work
Common root causes
What is usually sitting under the signal.
- weak prioritization
- stakeholder overload
- poor work slicing
- hidden dependency costs
Likely consequences
What happens if nothing changes.
- delays
- burnout
- quality drops
- ticket theater
Look-alikes
Not what it looks like
Patterns that can be mistaken for this signal, and 'fix' attempts that make it worse.
- a bigger backlog means stronger demand and therefore health
Anti-patterns when responding
Responses that feel sensible and usually make the underlying pattern worse.
- adding capacity targets without reducing intake
- treating backlog growth as normal demand capture
Context
Context and ownership
Where this signal surfaces, who sees it first, who can actually act, and how much runway there usually is before escalation.
Where it shows up
- growing teams
- matrixed organizations
- stakeholder-heavy environments
Who sees it first
Before it escalates.
- delivery lead
- engineering manager
- scrum master or equivalent
Who can move on it
Not always the same as who notices it.
- manager
- product lead
- portfolio owner
near-term
How much runway there usually is before the signal hardens into the underlying pattern.
AI impact
AI effects on this signal
How AI-assisted and AI-driven workflows tend to amplify or hide this signal.
AI amplifies
Ways AI tooling tends to make this signal louder or more common.
- AI can make work creation easier than work completion, increasing ticket and artifact inflow.
AI masks
Ways AI tooling tends to hide this signal, so it keeps growing under the surface.
- Productivity-looking output can hide queue expansion.
Relationships
Connected signals
Related failure modes, decisions behind the signal, response playbooks, and neighboring red flags.