A bi-weekly dispatch for the operations leaders, CFOs, and workforce strategists who refuse to run capacity on averages and hope.
The test: most operations run two, maybe three, of the five layers that make a workforce plan compound. Can you name the last time your forecast was measured at the interval, not the day? If not, you are carrying Shrinkage Debt — over-staffing the quiet hours and under-staffing the peak.
Not a headcount problem. An architecture problem.
Symptoms of skipping it: three teams, three numbers, and a meeting spent arguing about whose spreadsheet is right.
The free tool that turns occupancy, AHT, and shrinkage into the one number your CFO reads. Get it, run your number.
Get the Engine — free→The full engine — probabilistic, interval-level, built to drop straight into your stack.
Get Engine Pro→Seven WFM metrics, translated into the language Finance already speaks — one move at a time.
Get the Calculator→Send your plan’s assumptions and recent data. Get back a written review of what to fix first, read against your own numbers. Async, no calls required.
Request a review→The same raw data can report two different Service Level numbers, depending on one policy choice nobody states out loud. Watch it move.
See your number — free→The first 15 numbers to track before you build anything else — grouped by owner, with the lead-time warnings most teams only learn the hard way.
Get the Dashboard — free→If you got handed workforce management with zero training, this is the order to learn it in — a week-by-week map, not a topic list.
Get the Map — free→A 12-chapter guide for anyone handed workforce management with zero training — the architecture, the vocabulary, the math, and the conversation skills the first 90 days actually run on.
Get the Blueprint→Grade your forecast against actuals, catch the days it quietly broke, and put the error in staffing dollars. One verdict your finance team can read. Excel or web app, same math.
Twenty years across BPO and contact-center operations — leading ops, the floor, training, and hiring, not just WFM. Four seats, one industry, and eleven-plus of those years building workforce systems. That cross-seat view is why I read workforce as architecture, not scheduling. The work speaks; the builder stays in the background.
Bi-weekly. Free. No fluff, no pitch — just the architecture, one layer at a time.