Operations
Batch effects in service queues
Friday cut-offs and Monday sweeps create phantoms that look like staffing gaps.
Service organisations across Great Britain still run on quiet batch rules: invoices leave on Tuesdays, site visits book in weekly waves, approvals pause after 15:00. Business analytics for process efficiency mapping must treat those rules as first-class citizens on the diagram.
How batches disguise themselves
Averages rise near the cut-off. Leaders see a “slow team.” The map, if honest, shows a gate with a calendar icon — not a skill deficit. Without that icon, every chart becomes a morality play.
Plot the wave, not just the mean
Overlay arrival counts by hour and day against departure counts. When departures clump while arrivals are smooth, you are staring at policy, not effort. Bring that overlay to the same workshop as the efficiency map so debate stays concrete.
Decide whether the batch earns its keep
Some batches protect quality or reduce switch costs. Others survive from a printer schedule written in 2011. Mapping does not auto-delete the batch; it forces a named owner to defend it. That conversation is often the highest-ROI hour in a Flow Studio cohort.
Document the choice
If the batch stays, annotate the map and adjust SLAs so customer promises match reality. If it goes, update the wait-segment sheet the same week — otherwise analytics will keep measuring a ghost.