Talking About It Without Making It Worse

The same policy, announced two ways, produces different behaviour. This is not a presentation problem; it is the whole of it.

What the announcement is read as

"We think you are stealing from us" — which is how a crackdown framing lands regardless of the wording.

Or: "the clock keeps failing and we are fixing it" — which is how a structural framing lands.

People respond to the first by protecting themselves: punching early to be safe, not reporting faults, absorbing minutes quietly.

Which produces worse records and less recovered time than doing nothing.

The framing that works

Lead with what you are fixing. The terminal queue, the break room walk, the rota notice period.

State the tolerance, which most people did not know existed.

State the pay sentence: if the system fails, you are paid.

Then state the expectation, which by that point is reasonable and reads as reasonable.

What to avoid saying

"Time theft," in an announcement to everyone. It accuses the whole workforce of something almost none of them are doing.

An industry statistic, which people recognise as not being about them.

"We will be monitoring closely," which produces the protective behaviour above.

Anything implying the minutes matter more than the work, which in most operations is not true and everyone knows it.

Saying both directions

"We looked at both. Here is what we found in each. Here is what we are changing."

This is the single most effective thing available, and almost nobody does it.

It makes the first column credible, and it removes the objection everyone was about to raise.

Who says it

Someone who can change things, not a notice on a board.

In person where possible, with questions.

And the supervisors briefed first, so they are not hearing it with their teams.

Afterwards

Report what changed, including the fixes.

Publish the anomaly rate.

And when someone reports a fault, fix it visibly — which is the demonstration that the framing was honest, and the thing that determines whether the next fault gets reported.

Brief supervisors first

A sequencing detail with a large effect.

They should not hear it alongside their teams.

Because the first question will come to them, and "I don't know either" tells the team what the change is worth.

Give them the tolerance, the pay sentence and the four checks, a day ahead.

And tell them what to do when someone reports a fault, which is the interaction that sets the tone.

Connect policy and data

The choices in this note can be compared with the scheduling reference. Keep the written purpose in control and enable only the information needed at this boundary.