Every manager has had an employee show up late. What you do in that moment reveals everything about what kind of leader you are.
I used to think it revealed whether you were “professional” or “too soft.” I was wrong.
It reveals whether you lead humans or manage policies.
The meeting I’ll never forget happened on a Tuesday morning.
My supervisor called me into her office with that particular tone that meant someone was in trouble. “Rebecca, we need to discuss Sarah’s (not her real name) punctuality. She was five minutes late again yesterday. I need you to have a formal conversation with her about time management.”
Sarah. My most reliable team member. The one who stayed an extra hour most days without being asked. The one who caught errors that could have turned into compliance nightmares. The one whose work I never had to double-check because I knew it would be done properly the first time.
Sarah, who was five minutes late because she’d been caught in traffic after dropping her kids off at school.
I sat in that office, staring at my supervisor, feeling something twist in my stomach. This wasn’t right. I knew it wasn’t right. But the policy was clear: repeated lateness requires progressive discipline, regardless of context.
“Of course,” I heard myself say. “I’ll speak with her this afternoon.”
I walked back to my desk knowing I was about to have the stupidest conversation of my career.
The conversation went exactly as badly as you’d expect.
“Sarah, I’ve been asked to have a conversation with you about being 5 minutes late to work.”
I watched her face change. Confusion, then understanding, then something that looked like betrayal. She’d stayed an extra hour every day that week to pick up slack because we didn’t have enough resources to manage all of the required work.
“I understand the policy,” she said quietly. “It won’t happen again.”
But something had shifted. I could see it in her posture, in the way she started keeping her head down, in how she withdrew from interacting with her colleagues.
I had managed to turn my best employee into someone who was afraid to make mistakes.
All in the name of “fairness” and “following policy.”
About a year later, I faced a choice that changed everything.
Another employee, Lisa (again, not her real name), came to work a little later than normal and said “Rebecca, I had to wait until it was light outside to drive to work today. My vision has been getting worse, and yesterday I almost rear-ended someone because I couldn’t see the brake lights clearly. I’m terrified to get behind the wheel.”
Our workplace was hybrid, but the policy required in-person attendance 3 scheduled days a week. Lisa’s work that day fell into that category.
I looked at the policy. I looked at Lisa’s request. I thought about the impact of these types of conversations and about what kind of leader I wanted to be.
With Sarah, I learned something crucial: the moment you prioritise policy over people, you stop being a leader.
“Please do not feel pressured to drive into work when it’s not safe, your health and safety isn’t worth the risk” I told Lisa. “We’ll figure out accommodations for your vision issues, and please see a doctor as soon as possible.” She burst into tears right in front of me. Not out of sadness, but relief that I cared about her well-being.
A couple of days later, I got a ping on Teams. HR.
“Rebecca, Lisa has to come into the office 3 days a week or take sick leave.”
“No,” I said. “She’s working from home. It’s not safe for her to drive and I’m not having her risk her life (or the lives of other people) by driving when it’s unsafe and she’s perfectly capable and set up to work from home.”
“This is against policy. You need to—”
“I take full responsibility for telling Lisa to work from home. And I would make the same decision every time because if something happened to her or someone else because I made her come into work, I couldn’t live with myself, even if it went against policy.”
My hand got slapped. There was a meeting about “policy consistency” and “setting precedents.” But Lisa got her vision sorted, returned to work safely, and never forgot that someone chose her wellbeing over bureaucratic compliance.
And this decision? It showed my team that I actually care about the people I work with.
Here’s what I wish someone had told me earlier:
Policies exist to guide decision-making, not replace it. When you follow them blindly, you’re not being a responsible manager—you’re avoiding the harder work of actual leadership.
Real leadership means asking:
- What is this policy trying to protect?
- What are the actual risks we’re managing?
- What happens to the humans involved if I prioritise the rule over the relationship?
The Sarah conversation taught me that fairness isn’t treating everyone exactly the same—it’s considering context, contribution, and circumstances.
The Lisa situation taught me that sometimes doing the right thing means accepting that systems will push back.
Both taught me that integrity means making decisions you can live with, not decisions that keep you out of trouble.
Today, I help leaders build what I call “Integrity Architecture”—systems that guide good decision-making instead of replacing human judgement. Because the best policies in the world are worthless if they’re applied by people who’ve forgotten how to think.
Your people don’t need you to be a policy enforcement officer.
They need you to be a leader who can think, who cares about outcomes more than compliance, and who remembers that rules serve people, not the other way around.
The question isn’t whether you follow policy. The question is whether you lead with integrity when policy and people collide.
What kind of leader are you going to be?
comments +