What "reasonable management action" actually means under Fair Work
Most founders assume they can manage performance any way they like — as long as they're being fair. That assumption is wrong. And it's the one that shows up most often when things go sideways.
Under Fair Work, "reasonable management action carried out in a reasonable manner" is a specific legal concept — not a general vibe. It's the threshold that determines whether a worker's stress injury claim is compensable, whether a general protections claim has legs, and whether your conduct in a difficult conversation was defensible or not.
The "reasonable" part does a lot of work. And it's not judged by what felt reasonable to you in the room.
What the law actually asks
When a team member makes a claim arising from a performance conversation, a formal warning, or a restructure — Fair Work doesn't just ask whether you had a reason to act. It asks whether the action itself was reasonable, and whether the way you carried it out was reasonable too. Both parts matter independently.
A legitimate performance concern, handled with inconsistency, raised without prior documentation, or communicated in a way that was humiliating rather than direct — that's where "I had every right to do this" stops being a complete answer.
Where founder-led businesses most often get this wrong
The pattern I see most often isn't malicious. It's improvised. A performance concern builds quietly over months. Nobody documents it. Then something tips — a mistake, a conflict, a bad week — and the founder has a direct, emotionally charged conversation that hasn't been preceded by any formal process.
That conversation, however justified, is now the first piece of paper in the file. And if the team member later claims the conversation caused them psychological harm, the question isn't whether your frustration was warranted — it's whether the way you expressed it, in the context of no prior documented process, meets the threshold of reasonable management action carried out in a reasonable manner.
Often, it doesn't. Not because you're a bad manager. Because nobody built the process underneath you before the conversation happened.
The Boundaries pillar in practice
Boundaries — the third pillar of The Compass Method — is about exactly this. Not policies for their own sake. Documented processes that make your management actions legible, consistent, and defensible before you need them to be.
That means a performance management process your team knows exists. It means conduct expectations that are written somewhere both parties have seen. It means the difficult conversation happening as step three in a process, not as step one in a crisis.
The single highest-leverage move you can make this week
Find your last difficult management conversation — a performance issue, a conduct concern, a restructure discussion. Ask yourself honestly: if that conversation became a claim tomorrow, what's in writing that shows the process was fair and consistent before it happened?
If the answer is "not much," that's where Boundaries work starts. Not with a policy document nobody reads — with a simple, documented process that exists before the next hard conversation, not after it.
This article is general advisory content, not legal advice. For matters requiring formal legal advice, speak with a qualified Australian employment lawyer.