“Do we have enough people?” sounds like one question. The answer depends on what needs doing, when it needs doing, and which capabilities have to be present.

Retail: which demand signal matters?

In a store, transactions are a useful starting point, but they do not describe every task. Replenishment, service enquiries and opening routines may create work outside transaction peaks.

A useful workshop question is: what work becomes invisible if we plan only from sales? Start by listing the activities, then examine whether the chosen demand signal represents them. Avoid adding multiple workload measures together without checking for double counting.

Logistics: what has to happen before the cutoff?

Imagine a dispatch operation with a fixed collection window. A daily volume can look manageable while the work required before the cutoff is concentrated in a short period.

Ask whether a forecast is grouped into intervals that reflect the actual operating decision. Then examine handoffs: a well-staffed packing station cannot remove a constraint upstream if the right work has not reached it.

Healthcare: which capabilities need to be present?

In a care setting, headcount alone cannot explain coverage. Role, capability, workload and locally defined requirements all matter.

The workforce design question is how the relevant operational and professional owners define required coverage, and how that definition reaches the people planning the roster. Those owners must validate the requirements for their setting.

The shared thread

Begin with the service or operational outcome. Make the assumptions visible. Identify the people who can validate them. Only then choose the metric and the system behaviour that support the decision.

For discussion: what does a headcount report leave out in your industry?