When Policy Becomes a Weapon
What happens when unresolved conflict borrows the language of compliance
DEAR HR DIARY
Let me introduce you to three people before we get into it.
Teresa is a senior manager — near executive level, experienced, the kind of person who knows how the organization works and where authority sits. She is not new to leadership. She has earned her seat, and she knows it.
Tyson is a line manager who reports to her. He leads his own team, does his job, and by all accounts hadn't done anything wrong. For a few weeks, though, something between him and Teresa had come apart — publicly, loudly. Disagreements that didn't stay behind closed doors. Teresa felt he didn't respect her authority. Tyson felt she was overreaching and wouldn't listen. Both of them had a point. Neither of them was being heard.
Somewhere above them both, the CEO had sensed that something was off. But there had been no structured conversation, no formal intervention. Just a vague awareness that things weren't quite right — and a decision, conscious or not, to wait it out.
Sherlock is not an internal employee. She's an outsourced HR consultant — thirteen years of experience, no seat in the hierarchy, no political stake in how this plays out. She was brought in to apply policy fairly. She has seen most things. She is not easily flustered.
One day, Tyson isn't feeling well. Dizzy spells. He goes for a check-up, gets a note from a licensed medical provider, and submits a sick leave application.
And that's where this story really begins.
The Everybit Reality Check
Within hours, Teresa messaged Sherlock.
The questions came in stages, across three days. Was the document from a hospital or a laboratory? Did it actually recommend rest, or just record a blood pressure reading? Was two days of absence genuinely justified? She wanted to handle things correctly, she said. She just needed clarification.
On paper, these are compliance questions. Reasonable ones, even. Sherlock answered each one cleanly — the document was from a licensed provider, the notification requirement had been met, if there were separate concerns those could be addressed independently.
Then Teresa pivoted. She suggested the document didn't look genuine. Sherlock followed up with Tyson. Tyson — who had sensed the tension in his department but hadn't known its full shape — found out that his sick leave had been questioned by the person above him. He messaged Teresa directly. Teresa forwarded it to Sherlock: what's this?
Fourteen messages into a thread that was never really about sick leave, Sherlock said the quiet part out loud:
"It seems like there might be a bigger concern here beyond the document. If there are separate concerns, let's discuss those independently in line with policy."
That one sentence is the whole story.
When a senior leader uses HR policy to scrutinize a subordinate's documentation — in the middle of an active conflict with that subordinate — policy has stopped being a compliance tool. It has become a weapon.
The dangerous thing about this kind of weaponization is how legitimate it looks. Every question Teresa asked was, technically, askable. Every concern could, in isolation, have been genuine. That's precisely what makes the pattern so difficult to name — and so important to recognize early.
The signal isn't one unusual query. It's a pattern of HR questions directed at a specific individual, from someone in active conflict with that individual.
Why This Keeps Repeating
Patterson, Grenny and colleagues — authors of Crucial Conversations — describe what happens when people feel unable to raise a real conflict directly: they find a substitute arena. One where they hold the procedural high ground. One where challenging them looks like diligence, not aggression.
HR policy is almost perfectly designed for this purpose. It's technical. It has rules. It rewards people who know the language.
Teresa had a real grievance — valid or not, it was real to her — and it had nowhere structured to go. No mediated conversation. No clear decision from leadership about how the working relationship would be managed. The CEO knew something was off but hadn't acted. So the conflict found its own level.
The Arbinger Institute, in The Anatomy of Peace, describes how unresolved conflict changes how we see people — they stop being colleagues with legitimate needs and start being obstacles to manage. By the time Teresa was asking whether a blood pressure check-up constituted genuine illness, she wasn't seeing a direct report who was unwell. She was seeing an opening.
For business owners and founders reading this: the CEO's partial awareness — knowing something was off, taking no action — is not a neutral position. It's a decision, however unintentional, to let the conflict manage itself. And what unmanaged conflict does, reliably, is travel downward. Into HR inboxes. Into sick leave applications. Into the working days of people who had nothing to do with the original disagreement.
What This Looks Like in Practice
A few things that would have changed this story at any point along the way:
● Name it while it's small. Two senior people in visible, repeated public conflict is a leadership problem — not an HR problem, not a 'let's give it time' situation. It needs a structured conversation, a facilitator if necessary, and a timeline for resolution.
● Brief your HR partner on active conflicts. Sherlock spotted the pattern because she's experienced — but she was working blind. If your outsourced HR partner doesn't know there's a live conflict between two leaders, they can't flag when policy queries and personal vendettas start to overlap.
● Protect the person caught in the middle. The moment Tyson found out his sick leave had been formally questioned, the conflict had claimed him. A simple internal rule helps: concerns about documentation go through HR — they don't loop back to the employee as a challenge from above.
● Separate the processes. The compliance question deserved a clean answer. It got one. The relationship problem between Teresa and Tyson deserved its own separate process — different conversation, different documentation trail, completely detached from anything to do with sick leave.
Worth borrowing Sherlock's line, by the way. When you sense a policy query is carrying something heavier:
"Is there a reason we wouldn't treat this as straightforward? If there are separate concerns, we can address those independently."
It closes the compliance loop and opens the real conversation — without accusation.
The Quiet Consequence
The pattern, if nothing changes, tends to compound.
The policy challenges keep coming. Every submission from Tyson's direction becomes a potential flashpoint. HR starts absorbing the cost of a conflict that was never its to resolve. And Tyson — who went to the hospital because he felt dizzy and did everything right — now knows his sick leave was questioned. That knowledge doesn't leave him. It changes how he shows up. It informs, eventually, how long he decides to stay.
At some point someone files a formal complaint. Not about a sick sheet. About the pattern.
In Kenyan SMEs, where direct conflict resolution can feel uncomfortable and hierarchy makes pushback feel risky, the instinct to let things settle is understandable. But letting things settle and resolving things structurally are not the same action. One defers the cost. The other prevents it.
Back to the Scene
Tyson went for a check-up. He came back with documentation. The policy question had a clean answer — and Sherlock gave it.
But the real question running underneath all of it, across three days and fourteen messages, was simpler:
Is anyone going to address what's actually happening here?
Sherlock — an outsider, no political skin in the game — said yes. Quietly, professionally, without drama.
Whether the people with actual authority were ready to do the same is another story. One still being written.
If any of this felt familiar — not all of it, just the part where someone's asking about a document and you know it isn't really about the document — it might be worth a conversation. That's exactly what we help untangle.
Further Reading
Crucial Conversations: Tools for Talking When Stakes Are High — Patterson, Grenny, McMillan & Switzler — Why people avoid direct conflict and what to do instead.
The Anatomy of Peace — The Arbinger Institute — How unresolved conflict changes the way we see the people around us.
Dare to Lead — Brené Brown — On the real cost of avoiding difficult leadership conversations.
The Fearless Organization — Amy Edmondson — What happens to teams when raising real concerns feels unsafe.
© 2025. All rights reserved. All Rights Reserved.
Everybit Business Limited
consult@everybit-business.com
+254789852434
Office Hours: Mon–Fri | 9:00 AM–5:30 PM
Kenya's compliance-first HR partner for growing businesses.
Kenyan labour law mastery | data-driven results.