What This Subject Is Not

Workforce management is sold and discussed in ways this collection does not follow. The differences are deliberate.

Not a product category

The phrase names a market, and the market is organised around modules.

The failures are at the boundaries, which no module owns and no feature list describes.

Which is why this collection is organised by join rather than by function.

Not an optimisation problem

Most of what is offered is optimisation: better forecasting, better rota generation, better analytics.

All of which sit on top of a chain that in most organisations does not reconcile.

Optimising on unreliable inputs produces confident wrong answers faster, which is worse than the slow uncertain ones.

Not a technology project

Identity mastering, rule ownership and reconciliation are organisational decisions implemented in systems.

The three-week investigation crossing three departments is not a technical failure.

And a project treating it as one will deliver interfaces into the same organisational gap.

Not a source of individual measurement

The chain assembles a detailed picture of a person's working life, which makes per-person analysis technically easy and statistically unsupportable.

The errors of four modules multiply at individual level and average at site level.

That is a property of the data, not a policy position, and it happens to coincide with the right policy position.

Not finished at go-live

Every module upgrades, every reorganisation moves reference data, every new site or country adds a path.

The joins need an owner permanently, and treating them as a project is precisely how they become unowned.

What it is

Four boundaries, each with a defined payload, a mechanism, a failure mode and an owner.

Two masters underneath them: identity and reference data.

A register saying which system applies which rule.

And a monthly comparison that catches the silent failures.

Everything else in this collection is the detail of those four things.

Why the framing matters

Because it determines what gets bought.

A subject framed as a product category produces module comparisons and a purchase.

Framed as a set of boundaries, it produces a register, a reconciliation and an owner — which cost less and address the failures that actually occur.

The framing is chosen before the first meeting, usually by whoever wrote the brief, and it is worth changing there.

Follow the difficult record

Use the booking workflow example to frame one representative case. The useful evidence is the record created when a value is corrected, approved and exported.