Qualified capacity shortage
Clean, prioritized work waits because too few people have the required skill or authority.
Headcount decision
Before approving another hire, check what the team is waiting for.
A full workload can reflect a real capacity shortage, excess active work, incomplete inputs, rework, priority changes, or an approval path. Each cause requires a different response.
Plausible causes
Overload is the symptom. The response depends on the cause.
Compare the causes before increasing payroll or moving work between teams.
Too much active work
The team splits attention across more work than the shared step can finish.
Incomplete inputs and rework
The scarce skill spends time returning, clarifying, or repairing work.
Priority or approval delay
Ready work waits for a choice, handoff, or authority rather than productive capacity.
Evidence
Ask for the queue attached to the result.
A headcount case becomes stronger when the team can connect demand, waiting, qualification, and affected results.
| Review | Evidence | Possible response |
|---|---|---|
| Ready demand | Clean prioritized items, queue depth, average wait, affected commitments | Protect or add qualified capacity. |
| Active work | Work already started, switching, aging, competing projects | Pause, resequence, or limit release. |
| Input quality | Returned items, missing information, rework, blocked reasons | Repair intake and readiness rules. |
| Authority and policy | Approval age, decision owner, repeated handoff delay | Change ownership or approval path. |
Hiring may still be the correct decision.
The evidence should show that qualified demand remains waiting after priorities, release, inputs, rework, and approval delay have been tested.
Action
Name the role, skill, queue, work protected, and demand the new capacity should absorb.
Baseline
Record queue depth, average wait, active work, completed work, and affected results.
Follow-up
Check whether waiting and the exposed result changed after capacity arrived.
Bring one result that is late or at risk.
We will map the work behind it, compare plausible causes, identify missing evidence, and define one management action worth testing.