The First Quarter After a Change

Whatever changes — the pattern, the notice period, the tool — the first quarter determines whether it is believed.

Watch weekly

Notice actually achieved, which is the promise being tested.

Employer-initiated changes, which should fall.

Swap volume, which spikes initially and should settle.

Constraint breaches, which should be zero.

Complaints, formal and informal, which arrive before they arrive formally.

Be present

Be there when the first rota under the new arrangement goes out.

Ask five people whether it works for them.

You will hear about the shift that misses the bus, the pattern that breaks a childcare arrangement, the slot nobody wants — none of which appears in a report.

Fix one thing visibly

Change something people named, quickly, and say you did.

"You told us the Sunday early doesn't work with the bus, we've moved it to nine" does more than any briefing.

Speed matters more than elegance in the first month.

Be generous with swaps

Volume will be high while people adjust.

Approving them readily keeps the record accurate; restricting them produces informal swaps you cannot see.

Tighten later, once the pattern has settled and an ordinary swap is distinguishable from a signal.

Hold the notice period

One late publication in the first quarter undoes the announcement.

If it cannot be held, say so before the day rather than after, and say why.

Publishing the achieved figure weekly is what makes the commitment credible, including when it slips.

The review at week twelve

The six measures, before and after.

What was fixed.

What people say when asked directly.

And one honest question: is anyone worse off under the new arrangement? Usually somebody is, and finding out early is what prevents it becoming the story of the change.

Ask who is worse off

The honest question at week twelve.

Under any new arrangement, somebody usually is.

The person whose old pattern suited them and whose new one does not.

Finding out early is what prevents it becoming the story of the change, and it is usually fixable with one adjustment that costs nothing.

A practical implementation prompt

During configuration, use the boundary-testing example to prompt questions about fields, ownership and output. Keep the written scheduling purpose in control and document every assumption.