Writing
The argument, in pieces.
These essays each work through one part of the operating argument: how I think about WFM, measurement, and the people running the floor. They are finished, and they are the fastest way to decide whether the rest of this site is worth your time.
Essays
Start with any of them.
Each one stands alone. Together they come at the same argument from different directions: what a metric hides once it becomes a target, what AI does to the numbers, what churn actually costs, where the next hire is already sitting, what WFM actually manages, and where the work a plan missed shows up first.
If you run a floor, start with the adherence essay. If you build the staffing plan, start with the inventory argument. If you approve the budget either one runs on, start with the cost of a no.
Read the trade, not the target.
A metric stands in for a reality the operation cannot see directly. Promote the number from signal to target and it starts buying its own improvement with the work underneath it.
AI changed the queue. The scorecard did not.
When automation takes the easy work first, every number on the legacy scorecard moves. Read literally, the movement looks like decline.
Adherence is a reading, not a leash.
Adherence measures how closely the day followed the plan. Most operations point it at people instead, and then quietly edit the plan until the number behaves.
Accountability is a claim you have to be willing to withdraw.
A number goes red and the room asks who owns it. That question wants a name. Accountability wants a standard, a record the person has already seen, and the nerve to take the claim back when the evidence turns.
Attrition is not the weather.
The replacement cost is the part that reaches the budget. The rest of the bill is paid inside the operation, months before anyone resigns.
The talent was already in the building.
A seat opens and the search goes straight to the outside market, past an agent two rows away already doing half the job. Internal-first is a search order, not a promise, and it submits to numbers a skeptic can check.
The cost of a no lands somewhere else.
Nobody deletes the work when the headcount is declined. The cost moves onto budgets the person who declined is not measured on.
The inventory is human attention.
Workforce management is treated as the scheduling department. Run it as strategic inventory management and every argument it needs to win becomes an argument it can actually make.
The missing work was visible from inside it.
The project view held the migration as a sequence of milestones. The operating view held it as a stream of changes. Both views were necessary. Only one of them could see the missing work.
Where next
Tell me what you think.
If one of these landed, or one of them is wrong, I would rather hear it than not.
I am also writing a longer series, The Development-First Contact Center, which works the whole argument out at length. None of it is available yet. When something is ready to read, it will be linked here, not announced before.