Occupational Violence and Aggression (OVA) Tolerance Isn't a Policy Gap — It's Who You Protect When It Counts

AI Summary

This article examines a pattern in occupational violence and aggression (OVA) response: organisations that appease an aggressive customer or complainant while implicitly criticising the staff member who absorbed the incident. Using the 3W of Human Performance™ (Work, Worker, Workplace) and 3P of Organisational Performance™ frameworks, it argues prevention must address task design and organisational response, not staff training alone. Mind Logistics — The Business Psychologist offers OVA training and Psychosocial Risk & Protection Review services for organisations addressing this pattern.

Here's a pattern I keep seeing, in organisations of every size — from the servo on the corner to health and community services providers running trauma-informed practice on paper. Someone is abused, threatened, or intimidated by a customer or client. And the organisation's very next move is to manage the person who caused it, and quietly critique the person who copped it.

A small retailer compensates an aggressive customer to make her leave, keeps the CCTV footage, and considers the matter closed. The staff member who was screamed at gets a sick day and nothing else. A community services team has a complaint escalate, and the feedback that filters back to the staff isn't about the aggression they absorbed — it's "the team should have done better." Different scale, same mechanism: the person who caused the harm gets managed. The person who absorbed it gets reviewed.

Nothing says "we've got your back" quite like a fruit basket for the person who screamed at you and radio silence for you.

"Retrain the worker" is answering a third of the question

There's a lens I use with clients for exactly this moment — the 3W of Human Performance™: Work, Worker, Workplace. It's a simple way of asking where risk actually sits when something goes wrong (though it's an even more powerful tool used the other way around — as a prevention framework, applied before an incident happens, not just diagnosed after one). It's almost never only one of the three. And it's almost never the one that gets addressed first.

Worker is the individual — their skills, their resilience, their capacity to de-escalate, and often, their experience. Work is the task itself — was someone rostered alone on intake with no way to call for backup? Is there a clear point at which staff are authorised to end an interaction? Workplace is everything around the task — and it's more than the response system. It's whether a client can get within arm's reach of a worker with nothing between them. Whether there's an actual escape path, or whether the layout puts the exit behind the person causing the problem. And separately — once an incident is reported, whether anything changes, or the report just gets logged and filed.

"The customer's always right" is worth sitting with for a second, because it's done a lot of quiet work over the last hundred-plus years. It's widely credited to early department-store retailers as a sales philosophy — reassure the customer, build trust, keep them coming back. It was never written as an instruction to absorb abuse. But it's been carried forward, largely unexamined, into settings it was never designed for — including ones where the "customer" is a person in crisis, in pain, or in the middle of the worst day of their life. Decades of that mantra sitting quietly in the background is part of how we got here: a default that treats the person receiving the service as the one whose comfort matters most, even when they're the one causing the harm.

(Worth a quick check before publishing: the Selfridge-era origin of "the customer is always right" is the commonly cited version, but I don't have live access to confirm it — "widely credited to early department-store retailers" is the safer phrasing if you don't want to name a specific person.)

"Retrain them to de-escalate better" and "build more resilience" are Worker-only interventions. Neither is wrong exactly — de-escalation skill genuinely helps, and resilience isn't a dirty word — but they answer a third of the question, and it's the third that quietly implies the person on the receiving end could have prevented it if they'd just handled it differently. In the community services example, the Work (lone intake work, no backup protocol) and the Workplace (a layout with no real escape path, and a response that read as "the team should have done better") both went unexamined. The training budget went to the Worker corner. The two corners actually driving repeat exposure stayed untouched.

It's also worth naming who's often standing in that Worker corner in health and community services: young people, in their first or second job, without the years of experience that make de-escalation feel instinctive rather than terrifying. Asking a 19-year-old on the front counter to "just handle it better" assumes a level of composure most people don't build until they've had a decade of practice — if they ever get it at all. That's not a criticism of the worker. It's a reason the Work and Workplace corners matter even more.

Occupational Violence and Aggression (OVA): Why the Appeasement response Costs More Than It Looks

This is where a second framework earns its place — the 3P of Organisational Performance™: two conditions, Psychosocial Safety and Psychological Safety, plus one mechanism, the Psychological Contract, which together determine whether performance is optimal or quietly eroding.

Psychosocial Safety is the organisation's actual, structural commitment to controlling hazards like OVA — not the policy document, the real controls. Psychological Safety is whether the team believes it can report an incident without that report being read as a personal failure. And the Psychological Contract is the implicit, unspoken deal underneath both: I show up, I do the work, and in return I can expect a baseline of protection.

A Worker-only response quietly damages all three at once. Psychosocial Safety doesn't improve, because nothing about the Work or Workplace has changed — the hazard is still there. Psychological Safety drops, because staff have just watched an incident get read as their own shortfall rather than a shared risk. And the Psychological Contract fractures the moment someone absorbs aggression as "part of the job" and then hears their own response, rather than the incident itself, being scrutinised.

What follows isn't usually a dramatic resignation. It's smaller and slower: people stop reporting, because reporting hasn't changed anything before, and engagement quietly declines.

There's a compliance layer underneath all of this, too. In most Australian jurisdictions, psychological harm arising from workplace violence and aggression is now an explicitly recognised psychosocial hazard under WHS law, and the duty on the organisation isn't just to reduce how often it happens — it extends to preventing and minimising its impact once it does. Failing to contain that impact isn't only a psychosocial-safety problem in the 3P sense. It's arguably a WHS obligation failure in its own right, and it's usually the first thing a regulator or an insurer will look for.

(Worth a verification pass before publishing: WHS psychosocial hazard obligations are broadly consistent across harmonised jurisdictions but do vary in wording and coverage by state, and I don't have live access to check the current code of practice text while drafting.)

It's rarely one incident, and rarely one bad response, that creates a claim. It's cumulative: repeated exposure to OVA — each instance "resolved" from the organisation's side and unresolved from the worker's — is what actually erodes the psychological contract over time. That accumulation, not the single dramatic incident, is what tends to drive psychological injury claims in this sector. It's also exactly the exposure a Psychosocial Risk & Protection Review is built to surface before it reaches that point.

(There's a related idea in institutional betrayal research — harm caused not by an incident itself, but by an institution's failure to respond to it adequately, sometimes called secondary victimisation. I don't have live access to a citation database while drafting this, so that reference is worth a quick verification pass before it goes live.)

What actually changes it — across all three

Prevention has to reach all three corners of the 3W, or it isn't prevention. It's paperwork.

Work

• Roster and task design so no one is absorbing a high-risk interaction alone, with a clear, pre-agreed point at which staff can end it or call for backup.

  
  

Workplace

• Physical layout and environmental design: real distance or barriers between client and worker, sightlines, and an escape path that doesn't run past the person causing the problem. Duress alarms that are tested, not just installed.

• Audit what actually gets fed back to staff after an incident. If the only feedback that reaches them is about their handling of it, that's the loyalty signal — however well-intentioned the words were.

• Build the response into policy before the incident, not while you're standing in it. Under pressure, organisations default to whatever's fastest to resolve — which is almost always the complainant, not the staff member.

• Separate the two responses explicitly. Managing the complainant/aggressor and supporting the staff member are two different actions, on two different tracks, and the second one doesn't wait for the first to resolve.

  
  

Worker

• Support and recognition after an incident, not a platitude. "We can always improve" lands as tokenistic — most people already know that intellectually. What they need is to feel backed and seen, not gently coached.

• De-escalation and communication skills still matter, and matter more for workers who are young or new to the role. But composure under aggression, especially from people who are themselves distressed or vulnerable, is built over years — it's one leg of three, not a fair substitute for the other two. 

  
  

I've recommended de-escalation training more times than I can count. It's only more recently that I've started asking what that recommendation was quietly letting everyone else off the hook for.

A direct question

Preventing the impact of OVA isn't optional generosity toward your team. It's a WHS obligation, the same as any other hazard. So — is OVA actually sitting on your psychosocial risk register, named as its own hazard rather than folded into a generic "workplace conduct" line? And where it is, do the controls next to it change anything about the Work and Workplace corners, or do they stop at a policy document and a training module?

If you're not sure what I mean by any of that, that's worth a conversation — not as a gotcha, but because most organisations genuinely haven't been shown what "adequate controls" looks like beyond a policy sitting in a folder. If you don't know, let's talk.

(One factual note, worth confirming for your own state and sector before this goes out, since it's a compliance claim: the core WHS duty to identify and manage psychosocial hazards — including OVA — applies to every business regardless of size. There's no employee-count threshold that exempts a smaller organisation from the underlying obligation. What does vary by size and by state is how formal the expected documentation is — a large health service and a five-person outreach team both carry the duty, but a regulator's expectation of what "adequate" looks like on paper scales with size and risk exposure. I don't have live access to check current state-by-state guidance while drafting, so this is worth verifying against your own WHS regulator's material before it's published as a firm claim.)

Where to start

The two services below map onto the two corners that usually get skipped. Our OVA training is delivered across three formats and covers the Worker leg — skills, confidence, de-escalation. Our Psychosocial Risk & Protection Review™ looks at the Work and Workplace legs — task design, response protocols, and the gap between what a policy says and what actually happens under pressure.

You noticed something reading this. That noticing matters — it's usually the first sign the pattern's already familiar.