Feedback Loops in Workforce Planning

From WFM Labs

Feedback loops in workforce planning is a catalogue of the feedback structures that govern how a service workforce's capacity follows its demand: the balancing loops that keep it on course at each planning horizon, the couplings that let one horizon inform another, and the reinforcing loops that take over when the balancing loops are left open. It is the reference list behind Workforce Planning as a Control System, which sets out the reading; this page names each loop, gives its polarity and dominant delay, and records the signature by which it can be recognised in an operation's own data.

The vocabulary is system dynamics.[1] A balancing loop (B) moves a stock toward a goal and is the structure of every controller. A reinforcing loop (R) amplifies whatever direction it is already moving in and is the structure of every spiral. A loop's dominant delay sets its natural period: a balancing loop with a long delay and an aggressive correction oscillates at a period of several delays (two to four delays is a rule of thumb from the stock-management structure;[1] three in the companion simulation [estimated]), which is why the hiring pipeline is a frequent source of the cycles an operation blames on forecasting. In that simulation about half of the seasonal cost gap between the cascade and the closed loop is attributable to delay, the rest to forecast anchoring and churn smoothing [estimated].

The controller loops

The five controller loops stacked by horizon, with the couplings between them.

Five balancing loops, one per horizon. In a conventional cascade only the first is closed; the design intent is that all five are.

Loop Polarity Stock controlled Lever Dominant delay Samples Frozen zone Closed today? (this wiki's characterisation)
B1 Interval correction B the queue or occupancy gap in the current interval real-time actions, skill flex, voluntary overtime and time off offers minutes every 15 to 30 minutes none; this is the committed step yes, through real-time management by people or automation; see Intraday Management
B2 Short-term reforecast B the hours gap in the next one to two weeks the hours band, overtime and time off, schedule trades, cross-skill routing days daily the published week partly; the forecast is refreshed but the schedule is rarely re-cut
B3 Pipeline-aware capacity B the rolling thirteen-week surplus or deficit by pool, net of the supply line moves, requisitions, the partner's band, class starts eight to sixteen weeks, the pipeline weekly roll, monthly decision the plan of record no; the gap is reconciled to the annual plan and the supply line is not counted
B4 Structural elasticity B the cost of variance; the share of the swing carried by the cheap levers contract bands, cross-trained groups, working-time averaging, location and automation mix; see Supply Elasticity Lever Inventory quarters quarterly contract notice rarely; elasticity is requested, not designed
B5 Finance envelope B spend against a rolling envelope the envelope, authority bands a month monthly the fiscal quarter no; the envelope is annual and fixed

The last column is the diagnosis. The signature of an open loop is a measurement that exists but changes nothing until the next planning event.

The couplings

Five couplings carry state between the loops. Without them the loops are five separate controllers that fight; with them they are one system.

Coupling Direction Mechanism What it needs
L1 Vintage learning up forecast error, measured by the horizon at which the forecast was made, retunes the model or assumption that owns that horizon a version on every forecast (Forecast Vintages); coherent forecasts across horizons (Hierarchical Forecasting)[2]
L2 Assumption ledger up the annual plan held as named assumptions, each a stock with a tolerance band, so that the plan is recomputed rather than re-signed a definitions register that the ledger reads from; see Assumption Ledgers and the Continuous Annual Plan
L3 Variance routing across each component of a gap is assigned to the slowest loop whose delay matches its persistence; nothing persistent is allowed to live in B1 variance decomposed by cause; see Variance Routing by Horizon
L4 Envelope feed-down down a rolling envelope and authority bands inside which B3 acts without escalation a commitment ledger separate from the forecast
L5 Anticipation down each slow loop carries a model of how the fast loop will respond, so that its plan arrives feasible the fast loop's levers and their limits known to the slow loop[3]

The pathology loops

Four of the seven pathologies as a causal-loop diagram: R6, R2, R3 and R4.

When the controller loops are left open, reinforcing loops take over. Each has a published pedigree and a signature in operational data.

Loop Polarity Chain Source Signature in the data
R1 Plan defence R gap against the annual plan ↑ → explanation effort ↑ → decision latency ↑ → gap ↑ policy resistance;[4] the "lock erosion" failure mode in Capacity Planning Cycle decision latency rising with the size of the gap; re-forecasts that move toward the budget
R2 Understaffing spiral R gap ↑ → occupancy and overtime ↑ → attrition ↑ → gap ↑ the field's own; Systems Thinking, Recruiting Pipeline and Capacity Planning attrition rising a quarter after sustained overtime
R3 Quality erosion R pressure ↑ → handle time squeezed ↑ → repeat contacts and rework ↑ → workload ↑; and the quality aspiration follows the squeezed handle time down Oliva and Sterman's "Death Spiral" (R2) and "Goal Erosion" (R1) loops, with "Corner Cutting" (B1) as the balancing relief that feeds them[5] handle time falling while repeat rate rises; the handle-time standard revised downward "to reflect performance"
R4 Capability trap R firefighting ↑ → improvement time ↓ → planning capability ↓ → firefighting ↑ Repenning and Sterman's "Shortcuts" (B3) and "Reinvestment" (R1) loops, alongside their "Work Harder" (B1) and "Work Smarter" (B2)[6] the share of planner time spent on exceptions rising; improvement projects that never start
R5 Forecast credibility R forecast bent toward the budget → misses ↑ → trust in the forecast ↓ → manual overrides ↑ → misses ↑ the budgeting critique[7] and the plan-to-budget bias practitioners describe in sales and operations planning[8] the share of forecast values overridden rising with the age of the forecast
R6 Hiring oscillation B3 with its delay: a balancing loop that oscillates, listed among the pathologies though it is not reinforcing gap → hire → the pipeline lands late → surplus → freeze → attrition drains the surplus → gap the beer game: decision-makers ignore the supply line and overshoot[9] headcount deviation with a period of several pipelines once the calendar is removed (about three in the simulation [estimated]); requisitions opened and cancelled in alternate quarters
R7 Cohort rollover a delayed echo, reinforcing only where the next wave is sized to the last wave's attrition wave hiring → wave ramp → wave plateau → wave attrition → wave hiring, larger the laddered-tenure argument in The Case for Adaptive Workforce Management attrition concentrated at one tenure band; classes that are all the same size

Service supply chains have their own amplifier: with no inventory to buffer, backlog can only be managed by changing capacity, and capacity-adjustment delays amplify variance upstream. Uniform targets across stages make it worse; the backlog is best held nearest the customer.[10] A cascade that pushes one target through every tier is a uniform-target chain, and workload amplification with quality decay past a threshold has been observed in a multi-stage service chain.[11]

Reading the loops in one application

The ablation ladder: cost per contact relative to the cascade as one switch at a time turns it into the closed loop, in a seasonal world. Index only [estimated].

A weekly stock-and-flow model of the five loops, run under the conventional cascade and under the closed-loop design on the same synthetic demand, gives the loops a shape [estimated]. Three observations about the model's structure follow.

  • The fast loops hide the slow loops' failure. With a free real-time absorb, an overtime band, a share of deferrable work and some room to squeeze handle time, a sustained shortfall in capacity is survivable for many weeks at a cost that shows up as overtime and repeat contacts rather than as missed service; in the simulation the overtime band and the real-time absorb carry about six-tenths of the weekly gap-hours under either policy. That would explain why a cascade's open loops are rarely seen as the cause of anything.
  • Counting the supply line is necessary but not sufficient. Adding the supply-line term to the hiring rule reduces the ringing after a step only modestly while the whole gap is still being hired each month; the ringing goes when the adjustment is slowed to about eight weeks on a twelve-week pipeline and only persisted variance is released. The literature says the same: oscillation depends on the supply-line weight and on the stock-adjustment time relative to the delay, together.[1]
  • The ladder is not monotone. Turning the cascade into the closed loop one switch at a time, some switches hurt until the ones after them are thrown, and the routing and frozen-zone switches lose under fast upward shocks and with long pipelines, where waiting for a gap to persist costs more than it saves. The switches are a system.

Limitations

The catalogue is a design, not a survey: no organization has been observed running all five controller loops, and the couplings are the least tested part. The pathology signatures are proposals for what to measure, not validated diagnostics. The loop names inside the cited papers are reproduced from their published figures; the controller and coupling names are this wiki's. The quantitative observations come from one illustrative model and should be read as structure, not as effect sizes.

Maturity Model Position

The catalogue reads across the WFM Labs Maturity Model™. At lower levels B1 is the only closed loop and R2 is the dominant pathology. Level 4: Planning in Distributions closes B2 and B3 and introduces L1. Level 5: Adaptive Orchestration runs the interaction-level loop that B1 becomes when the handler is chosen per contact, and the couplings L3 and L5 are what connect it to the planning loops above it.

See Also

References

  1. ↑ 1.0 1.1 1.2 Sterman, J. D., Business Dynamics: Systems Thinking and Modeling for a Complex World, McGraw-Hill, 2000; the stock-management structure is in chapter 17 and the labor supply chain in chapter 19.
  2. ↑ Athanasopoulos, G., Hyndman, R. J., Kourentzes, N., Petropoulos, F., "Forecasting with temporal hierarchies", European Journal of Operational Research 262(1), 2017, pp. 60–74.
  3. ↑ Hax, A. C., Meal, H. C., "Hierarchical integration of production planning and scheduling", in Geisler, M. A. (ed.), Studies in the Management Sciences, vol. 1: Logistics, North-Holland, 1975.
  4. ↑ Sterman, J. D., "System dynamics modeling: tools for learning in a complex world", California Management Review 43(4), 2001, pp. 8–25.
  5. ↑ Oliva, R., Sterman, J. D., "Cutting corners and working overtime: quality erosion in the service industry", Management Science 47(7), 2001, pp. 894–914; the loops are named in their Figure 4.
  6. ↑ Repenning, N. P., Sterman, J. D., "Nobody ever gets credit for fixing problems that never happened: creating and sustaining process improvement", California Management Review 43(4), 2001, pp. 64–88; the loops are named in their Figures 4 and 5.
  7. ↑ Jensen, M. C., "Corporate budgeting is broken—let's fix it", Harvard Business Review 79(10), 2001, pp. 94–101.
  8. ↑ Ling, R. C., Goddard, W. E., Orchestrating Success: Improve Control of the Business with Sales and Operations Planning, Wiley, 1988.
  9. ↑ Sterman, J. D., "Modeling managerial behavior: misperceptions of feedback in a dynamic decision making experiment", Management Science 35(3), 1989, pp. 321–339.
  10. ↑ Anderson, E. G., Morrice, D. J., Lundeen, G., "The 'physics' of capacity and backlog management in service and custom manufacturing supply chains", System Dynamics Review 21(3), 2005, pp. 217–247.
  11. ↑ Akkermans, H., Vos, B., "Amplification in service supply chains: an exploratory case study from the telecom industry", Production and Operations Management 12(2), 2003, pp. 204–223.