Strain appears
The team feels busy and slow.
Capacity
Headcount is the most expensive way to buy capacity.
A new role can hide the leak without fixing the workflow.
Death to the Org Chart does not argue against hiring. It argues against using hiring as the default response to operating drag, because the real constraint is often the recurring work underneath the role.
The next hire looks obvious
A role is proposed before the workflow is redesigned.
The drag remains
The new person absorbs coordination rather than removing it.
Concise answer
Capacity is not only people.
Capacity can come from a better workflow, a built-in AI system, or a clearer decision path before it comes from another layer.
Hire for judgement
Bring in people when the work requires taste, relationships, accountability or leadership.
Automate the tax
Remove repeated reporting, copying, chasing, summarising and status work.
Then scale
Once the workflow is clear, every hire has more leverage.
Questions
Hire after the workflow is honest.
Why is headcount the most expensive way to buy capacity?
Headcount is expensive capacity when a company hires around a broken workflow instead of redesigning the recurring work that creates the bottleneck.
When should a company hire?
A company should hire when the workflow is clear and the human work genuinely requires judgement, taste, accountability or relationships.
What should leaders do first?
Audit the workflow causing the strain, then decide which parts belong to AI, which need a human in the loop and which should stay human end to end.
The book
Death to the Org Chart starts before the next hire.
The book gives leaders a workflow-first way to find the real constraint.