The Warlock of Staff Reduction
Every AI initiative is measured by what it replaces
The Warlock of Staff Reduction has made a pact. On one side: lower headcount, a leaner org chart, and the satisfaction of being the leader who modernized. On the other side: everything the headcount analysis cannot measure — stability, trust, and institutional knowledge.
Symptom
AI initiatives are framed exclusively in terms of headcount reduction, never capability gain. The business case leads with 'we can eliminate X positions.' The warlock does not ask 'what can we build now?' They ask 'what can we stop paying for?'
Why It Matters
The Warlock equates human labor to token volume. If a person processes fifty requests a day and a model processes five hundred, the Warlock sees a ten-to-one ratio and reaches for the layoff button. What the ratio does not capture is that the person was doing forty other things the model cannot do.
What the Chapter Gives You
Why token volume is not labor, how to require every efficiency proposal to include a capability section, and the question that reveals who pays the cost the Warlock ignores.
Want the full chapter? Grab the free cheat sheet, read an excerpt, or get the book.
Recognize this one in your codebase?
Free cheat sheet, excerpts, and interactive diagnostics.