Conflict, Grievances and the Things That Fester

People work in close proximity, under pressure, for long shifts. Friction is normal and its handling is not.

What it looks like

Two people on a shift who cannot work together.

A team that has closed against a newcomer.

Allocation of the unpopular task, perceived as unfair.

Overtime distributed by favour rather than by rule.

Banter that one person experiences differently from the others.

And a supervisor perceived to have favourites, which is the most common and most corrosive.

Why it festers

Nobody raises it because raising it is a formal act with consequences.

The informal route is the supervisor, who is frequently part of it.

The formal route is a grievance, which is heavy, slow and adversarial.

And there is nothing in between, which means a problem stays small and unresolved until it becomes large and formal.

The missing middle

Somewhere to raise something without triggering a process.

A named person outside the line — a shift manager, an HR contact, a union representative where one exists — who can have a conversation and change something.

Which resolves the majority of these before they become anything.

Its absence is why operations see few grievances and high attrition, and read the first as evidence that nothing is wrong.

Handling the common cases

Two people who cannot work together: separate them by area or shift, early and without adjudicating who was right, unless conduct is involved.

A closed team: the supervisor's job, and a sign the team has been left alone too long.

Task and overtime allocation: a stated rule, published, applied. Most of the perceived unfairness here is the absence of a rule rather than a bad one.

Banter that has gone wrong: taken seriously the first time, which is both an obligation and the only way to stop it.

Where it is harassment or discrimination

General orientation, not legal advice.

A different category with legal obligations attached, and the informal route is not appropriate for it.

Which means the middle route needs to know when to escalate and the person receiving the concern needs to be trained on that line.

Do not resolve informally something that requires investigation, and do not investigate formally something that a conversation would fix.

Getting that judgement right is the whole skill.

The agency worker's position

Least secure, least likely to raise anything, and frequently the target.

With no grievance route in your organisation, because they are employed elsewhere.

Which needs stating explicitly: an agency worker on your site raises concerns through your route, and you deal with them.

Otherwise the mechanism is that they stop being sent, and you never find out why.

Records

A note of what was raised, by whom, when, what was done.

Brief, factual, and kept.

Because a pattern involving one person or one shift is only visible in the aggregate, and because in a later formal matter the absence of any record of earlier concerns is itself a problem.

The measure

Concerns raised informally, which should not be zero.

Time to first response.

Formal grievances, which should be low and which are not a success measure if the informal route does not exist.

And attrition by team, again, which is where unresolved friction shows up before anything else does.

The middle route, named

One person outside the line, named and known, who can hear something and change it.

Published: here is who, here is how, here is what happens.

Its absence is why operations see few grievances and high attrition.

How it fails in practice

There is nothing between silence and a formal grievance, so problems stay small and unresolved until they become large and formal.

Low grievance numbers are read as evidence that nothing is wrong.

The check

Count concerns raised informally.

If the number is zero, the route does not exist rather than the workforce being content.