The Question to Ask First

Most disagreements about scheduling are disagreements about who absorbs uncertainty. One question makes that explicit.

The question

When demand turns out different from the forecast, who carries it?

Ask it of any scheduling proposal, product or policy.

What the answers mean

"We cut shifts." The workers carry it, in lost income and a wasted day, and in covered jurisdictions you pay a premium for the privilege.

"We call people in." Same, in the other direction, and it requires people to keep days free.

"We run with a buffer." The business carries it, at a known and small cost.

"We flex the service level." The business carries it, by accepting a longer queue or a closed section — which is a legitimate decision and is rarely made deliberately.

"We have a standby list." Shared, voluntarily, which is the arrangement most worth building.

Why it works

It converts a debate about efficiency into a question about who pays, which is what it always was.

And the answer is usually a small, statable amount on one side and a large, diffuse amount on the other — which is why the diffuse side has been chosen by default.

The second question

What is the notice period we can actually hold?

Not the policy figure — the achieved one.

Publish that number, improve it by a week, and measure what breaks.

Almost everything else in this collection improves as a consequence.

Using both

The first decides the structure: buffer, standby list, flexible layer.

The second decides the discipline and produces the improvement people notice first.

Neither requires buying anything, and both are harder to answer than any question a vendor will ask.

The collection in one line

Decide deliberately who absorbs the uncertainty, publish as far ahead as you can hold, and put the constraints in before the optimisation.

Everything else here is the detail of doing that.

Ask it of features too

Not only of proposals.

Automatic rebuilding close to the day: who carries the variance? The workers.

On-call availability: who carries it? The workers.

A buffer: the business, at a known cost.

Run the question down a feature list and it sorts quickly into things that absorb uncertainty and things that redistribute it.

A practical implementation prompt

During configuration, use see how the workflow works to prompt questions about fields, ownership and output. Keep the written scheduling purpose in control and document every assumption.