You can build the perfect system until one person decides they’re the exception.
Let me tell you what happened last week.
I was coordinating a large group trip, including flights, hotels, transfers, and allowances.
And I mean everything.
Now, when I’m managing travel logistics like this, my approach is simple: no journey is over until everyone returns home safely.
When I touch projects like this, I don’t just book tickets.
I handle end-to-end coordination…. It’s operational excellence, fused with a touch of maternal instinct.
That means I need full visibility into everyone’s movements: who’s staying where, which dates they’re flying, and how we’re managing funds.
I had gone into what I call “military mode,” cross-checking name spellings, catching changes, and fielding all kinds of last-minute requests.
One traveler even submitted the wrong name and date of birth (total chaos).
Still, after several rounds of firefighting, we got there.
Tickets were issued, hotel rooms sorted, and transfer shuttles arranged.
We were down to the final detail: allowances.
The System Was Working Until One Person Decided the Rules Didn’t Apply
The plan was clear: I would handle the group’s allowances directly.
That had been communicated to both the team and the travelers.
My phone had been buzzing nonstop with questions: “When are we getting paid?” “Can I collect now?” But I told everyone the same thing: you’ll hear from me once everything is finalized.
Apparently, that wasn’t enough for one team member.
I walked into the finance office to collect the allowances… only to be told one traveler had already taken his.
Just like that.
No heads-up.
No email.
No call.
The finance team mumbled something about “we were just about to call you,” but by then the damage had been done.
A clear process had been broken willingly, and not by accident.
What Happens When Someone Puts Themselves Above the Process?
When I confronted the traveler, he didn’t even flinch.
In his mind, he hadn’t done anything wrong.
He was the one traveling, after all. He was “helping me out.”
This is how it had been done in the past.
And in any case, he wanted his money.
I couldn’t believe the arrogance.
There was no remorse, just justification and no sense of the ripple effects, just entitlement.
Because here’s the thing: when one person ignores the system, they don’t just disrupt the process; they compromise people.
That finance lead was left scrambling to explain, a huge risk in my eyes!
I had to do damage control, and worst of all, the rest of the group, who had followed instructions, saw that cutting corners still got results.
Entitlement Is the Silent Killer of Accountability
This wasn’t a logistical error, and it sure wasn’t poor communication.
It was a mindset problem.
One person assumed that rules didn’t apply to them.
Those systems were optional.
That their convenience came before collective coordination.
And when you’re building scalable systems, whether for operations, HR, finance, or sales, that kind of thinking is dangerous.
Because when exceptions become habits, your whole structure collapses under the weight of unpredictability.
So, What’s the Lesson?
The process is fragile.
Systems are only as strong as the people upholding them.
And when leaders tolerate entitlement, they unintentionally reward sabotage.
Here’s what I’ve learned:
- Don’t just design good systems…. Enforce them.
- Assume there will be pressure to bend the rules…Plan for it.
- And when someone circumvents the process, don’t explain it away, correct it out loud.
Because silence doesn’t protect your team.
It only empowers the next person to do the same.
Before You Scale, Fix Your Culture
If you’re building systems in your organization, start with this uncomfortable question:
Who in your team thinks the rules don’t apply to them?
That’s where your next fire will come from.
Until next Sunday!
