From headcount to workload
Every area has a driver that explains its load: invoices processed, orders fulfilled, tickets resolved, active customers, points of sale. Once the driver and the productivity per person are known, headcount stops being a negotiation and becomes a calculation that can be discussed with data.
What to do with areas that have no obvious driver
Legal, strategy, or communications aren't sized by volume. For them, a portfolio approach works: how many simultaneous initiatives the company can sustain and what capacity each one requires. If the portfolio shrinks, so does capacity.
Sizing only holds if it's reviewed
A one-time exercise erodes within two budget cycles. What sustains it is building the driver into the annual budget: any headcount growth must be explained by growth in the driver or by an explicit change in service level.
Key takeaways
- Every area needs an explicit, measurable demand driver.
- Areas without volume are sized by their portfolio of initiatives.
- The driver must remain part of the budget process so it doesn't erode.
NS frameworks and reference sources
- Proprietary NS framework · S2S·NS — methodological notes from the Organizational Design practice
- NS project base: anonymized cases by sector and geography
- Open market evidence and academic literature, recalibrated with client data
- Bain & Company — Spans and Layers benchmarks
- McKinsey — Organizational Health Index
- Deloitte — Global Human Capital Trends
This article develops proprietary NS Business Strategy frameworks, drawing on our project base and on public industry literature and studies cited above. Figures are reference ranges; each project is measured against the client's actual data.