When HR Policy and Morality Fight, Who Pays the Price?

"This has been the hardest week of my life."

Tom was physically drained, hadn't slept in days, and although normally quite a mentally strong man, there were a few moments when he had to hold back tears. 

His reputation had taken a serious hit, and his current team now looked at him skeptically, as if he might betray them at any moment.

But his eight-month ordeal was finally over. He had successfully proved to HR that the house was indeed burning down by sitting in the burning house long enough to accumulate enough scars for HR to get the evidence they required.

HR was not being insensitive or bullheaded. They were following policy. After all, intuition, even from a seasoned business veteran, shouldn't be allowed to supersede policy, right?

My own entry into this story 8 months ago started with an odd thought: "I really want to take a shower. Right now."

I was working with Tom's company and about to start a new assertiveness training program. I had just interviewed a woman, Yumi, about the program. The interview was supposed to be 30 minutes. I ended it at the eight-minute mark. Truth be told, I wanted to end it after three minutes.

Closing my MacBook, I couldn't shake the feeling: "I really want to take a shower. Right now." I felt polluted, covered in something that my body desperately wanted me to scrub off. And I had never, in 25 years, had that feeling after an interview.

And for the first time in my life, I wrote an email I never intended to write, to the woman's boss, Tom:

This woman is dangerous. We need to talk.

When I relayed my concerns to Tom, his face sagged. He didn't want to think negatively about his team, but my words surfaced his buried fears: Crap. I was worried something was off about her.

Tom asked me to do another first in my career—give HR my professional assessment and advice about a potentially dangerous employee. Normally I would not. I never have. But I kept thinking back to that reaction. "I want to take a shower. Right now."

So I told Tom to set it up.

The HR rep was friendly, engaged, and listened well. I think she believed me. She had already heard some stories about this woman that were concerning, just in the past week.

I outlined exactly what happened in the eight-minute interview and what I thought it meant. I also gave a rough timeline and predictions for how the escalation would likely transpire. This was not a new story to me. I have my own battle scars, lessons learned, and my intuition was red hot.

I bluntly stated, "When I was running my business back in the early 2000s, I would fire her as quickly as possible and deal with the consequences." I learned to take that option when necessary because I had seen what keeping someone like this could do to people like Tom, his team, and the company.

Sometimes, you shouldn't let the building burn down with people inside just to confirm that the fire was actually real.

Unfortunately, my professional intuition didn't budge her. Policy is policy. Tom would have to continue trying to help Yumi grow while simultaneously collecting meticulous evidence.

Let it burn.

And burn it did. Exactly as I had laid out. Now, eight months later, sitting in front of me was Tom, covered in soot with red-lined, insomnia-ravaged eyes. Even his marriage had been under strain.

The company, finally seeing that Tom had taken enough damage to make a legitimate claim, negotiated with the woman to leave the company...for a nice, hefty payout. And then, after eight months spent gathering enough evidence to negotiate her departure, the company allowed Yumi to continue working for another week.

She used those 7 days to light a few more matches on her way out.

HR is Like a Peach

HR is like a peach. The outside is soft and sweet, but at the core is a hard, inflexible directive—risk management.

When a company is filled with good-faith actors and the risks are low, everyone gets to enjoy the outer sweet layer. HR can focus on development, engagement, employee experience, coaching, culture, wellbeing, and all the other very useful human work it performs. But when serious risk emerges, the core takes over.

Organizations need to protect themselves legally, financially, and reputationally. In my experience, once those trip wires are activated, mitigating organizational risk gets virtually all of the attention until that risk is contained. 

I understand why. But those decisions are not happening in a vacuum, and the risk does not simply disappear because HR is managing it. Someone carries it. In Tom's case, much of it was transferred to him.

Fundamentally, HR needed evidence to make hard decisions. But needing more evidence was not a neutral choice, as some would have us believe. Evidence required Tom to remain in the burning building until HR had enough burns to establish that there really was a fire.

If a female friend told me she had a bad feeling about a man she had just started dating—that something in her gut said he might become violent—I would tell her to leave. Trust your intuition. Don't stick around to collect evidence.

Yet in business, we ask people to do exactly that: Stay. Experience it. Document it. Collect the bruises. Bring us more evidence.

There is something morally sobering about that.

From my perspective, the real question was not simply whether HR should have fired Yumi because James wanted to take a shower after an eight-minute interview. Of course not. There were other questions to consider.

What could the company do to reduce Tom's exposure while it investigated? How frequently would HR reassess the situation? What evidence would change its position? Who else could observe the interactions? Could Tom have received independent support from someone familiar with these kinds of high-conflict situations? And at what point would an accumulating pattern become enough?

What Counts as Evidence?

Relying on evidence—being "evidence-based"—is kind of the gold standard these days. But we sometimes forget what evidence actually means in circumstances like these. Also, what exactly constitutes "evidence"?

From my perspective, as a former CEO and now corporate trainer, I had enough evidence from that eight-minute interview with Yumi to schedule a call with Tom. I wanted to check with him, mention the specific things I had observed that were informing my intuition, and see if I was wrong. But Tom's reaction told me I was onto something. He had already sensed something was off.

I had acted on intuition, but my intuition wasn't floating in the air. It was connected to things I had observed. Yumi had accused me of damaging her "psychological safety" by making a report about her to Tom. There was no report. What she was accusing me of was not remotely factually accurate—or even possible.

What alarmed me most was the shift that came next. When I explained there had been no report, she simply brushed that aside and immediately blamed her coworkers for supposedly talking about her behind her back. With no evidence or reason, the attack moved from me to someone else. That was highly unusual, especially in an interview like this.

Her use of the term "psychological safety" mattered too. This is a popular and powerful term inside modern organizations. Within minutes of meeting a complete stranger, she had used that term in a vaguely threatening manner. I cannot prove what reaction she wanted from me—perhaps an apology, perhaps silence, perhaps simply to put me on the defensive—but it worked as an attempt to seize control of the interaction. My body noticed it immediately.

I formed a professional assessment from that interaction. My assessment was that Yumi wanted a very high degree of control over how she worked and would experience interference, accountability, or unwanted feedback as a threat. I expected that when challenged, she would move the focus away from the actual work issue and onto the person challenging her. Blame, accusations, HR terminology, involving other people, and eventually formal claims would become tools for getting people to back off and leave her alone.

That was my assessment, and it produced predictions. My first predictions came true about a week after that initial phone call. Then Tom and I had a conversation with HR. More predictions came true after that.

So at what point did HR's threshold change?

That's a question I genuinely don't know the answer to. At the beginning, they had the professional judgment of an outside person who had met Yumi for eight minutes. Fine. That shouldn't be enough by itself to make an employment decision. But then Tom independently confirmed concerns. Then observable behaviors began appearing. Then specific predictions I had made began coming true. Then it escalated.

What kinds of evidence are organizations prepared to recognize, and at what point do observations, experienced pattern recognition, corroboration, and successful prediction become sufficient to alter HR’s response?

Did HR really need to see the entire arc from start to finish, unraveling at a grindingly slow pace, to gather enough evidence to take action? I cannot make that decision for them. All I know is what they chose.

They chose to protect the policy using Tom's flesh as protective gloves.

Maybe they had no other choice. Maybe their hands were truly tied. But if that is the case, then I think there is another responsibility that should not be ignored.

What Happens to the Person Inside the Fire?

It's worth noting what Tom told me in our final chat. I had only spoken with him three times during those eight months, but he said those conversations helped him understand what was going on and what would likely happen. They helped him see what could and could not be changed or fought, where he needed to protect himself, what toll the experience was likely to take on him, and why his reputation could take a hit even if he handled the situation well.

That mattered because Tom was starting to doubt himself. Having someone outside the system look at what was happening, put language around it, make predictions, and then compare those predictions against what actually occurred helped him trust his own perceptions. It helped him stay calmer and keep his attention on the things he could actually influence rather than exhausting himself trying to control the things he couldn't.

And I think something else happened during those eight months that is easy to overlook: Tom became more capable.

Not because I rescued him from the situation. I couldn't. Not because I told him exactly what to do. I didn't. He became more capable because he was learning how to see what was happening while standing inside an extraordinarily confusing and frustrating situation. 

After it was over, there was another developmental question waiting for him: how had Yumi been hired in the first place? Tom had already admitted that something about her had bothered him. But she had worked extremely diligently during her three-month probation period. He had been trying to fill the position for nine months and was becoming increasingly worried about finding someone with the right skills.

So I asked him to think back. Where had his intuition spoken to him during hiring or probation? What had he noticed? What had he explained away? Had his anxiety about finally filling the position made him want the answer to be yes badly enough that he overrode the quieter intuition telling him to slow down because something didn't feel right?

I don't know what he'll find. But that is capability development too.

And this is where I think HR missed an enormous opportunity.

When the peach is soft, organizations talk constantly about capability development. Managers should learn, grow, reflect, become more self-aware, communicate better, become more resilient, and develop their judgment. But when the hard center takes over, that conversation can disappear exactly when the developmental opportunity becomes most intense.

Tom was mostly told to keep trying and keep collecting evidence. But what was he learning while he did it? How could the company help him become more capable of navigating the situation rather than merely surviving long enough to document it? 

And perhaps most importantly, how could the company help him come through this without deciding that the lesson was to become a colder manager? Because when I met Tom at the end, that was one of the possibilities he was considering.

That should concern HR too.

The Cost of Policy

Tom was exhausted. His reputation had been damaged. His marriage had been put under some strain. Some people on his team now looked at him differently. And after eight months of being told to keep trying, keep managing, and keep gathering evidence, he was wondering whether the way to protect himself in the future was to become a colder manager.

Meanwhile, the company finally had enough evidence. Yumi was gone and the immediate risk had been mitigated. From a conventional risk-management perspective, perhaps the system had worked. But I don't think that is the only ledger that matters.

A policy can be rational. An HR professional can be kind. Legal concerns can be completely legitimate. An employee accused of wrongdoing deserves protection against arbitrary action. And the process can still cause enormous harm that is overlooked.

That harm needs to go onto the ledger too. If an organization decides it needs more evidence before it can act, fine. But then it also needs to ask who will carry the risk while that evidence is gathered, and what support will help that person become more capable rather than merely more damaged.

Otherwise, "we need more evidence" can become an extraordinarily clean organizational sentence describing a very inhumane process.

I am glad I took that shower. Tom will recover, too. Hopefully the new Tom will emerge from the ashes stronger, more willing to listen to his intuition and more capable of handling the next challenge life throws at him. 

But I don't think organizations should confuse a person's ability to learn from being burned with justification for leaving someone in the fire.

Policy may tell you why you have to wait. Morality still requires you to ask who is paying for the waiting, and what you can do that policy doesn’t necessarily require you to do.