The First Quarter After a Change

Whatever you change — a tolerance, a terminal, a whole system — the first quarter determines how it is understood afterwards.

Watch weekly, not quarterly

Anomaly rate by site.

Corrections submitted and cleared.

Punch-to-shift distribution, which should tighten if the causes were addressed.

Grievances and informal complaints, which arrive before they arrive formally.

Anything unresolved at week three becomes the story of the change.

Be present

Stand at the door at shift change in the first week, at the busiest site.

Time ten people.

You will see the queue, the reader that misfires, the entrance that nobody uses, and none of it appears in a report.

Be generous at first

Approve corrections without scrutiny for the first month.

Volume will be high because everything is new, and querying them teaches people not to submit and to absorb the minutes instead.

Tighten later, once the anomaly rate has settled and an ordinary correction is distinguishable from an unusual one.

Fix visibly

Change one thing people named and say you did.

"You told us the back reader was slow, we have replaced it" does more than any briefing.

Speed matters more than elegance in the first month.

Say the pay sentence again

People will not believe it until it happens.

When the first person is paid normally after a system failure, confirm publicly that it worked — without naming them.

That is the moment the arrangement is accepted or not.

The review at week twelve

The four measurements, before and after.

Both columns.

What was fixed.

And one honest question: is anyone punching early to be safe? If yes, the tolerance is too tight or the system is unreliable, and it is fixable now rather than after it becomes habit.

Watch for early punching

The signal that something is wrong with the change.

Is anyone clocking in from outside, or earlier than they need to, to be safe?

If yes, the tolerance is too tight or the system is unreliable.

Both are fixable in the first month and much harder once the habit forms.

Ask people directly. At that point their answer is more reliable than the distribution.

Reproduce the workflow

For another way to make this requirement testable, consult the service-desk example. Reproduce the case with real roles, codes, failures and recovery steps.