A Workplace Lesson I Learned Years Ago - and Still Pass On Today
Sometimes the best lessons from an old job don't stay there.
There are some things you only learn after working long enough.
For me, one of those lessons came from my hotel-worker days:
Never use the word “absent” in future tense when notifying HR or your supervisors.
Recently, one of my co-developers sent a message saying he would be absent the following day because he had a family holiday planned.
Nothing inherently wrong with that, right?
Well, the problem isn't necessarily the absence itself. It's how the message can be interpreted.
When you say:
“I’ll be absent tomorrow.”
it can sound like you've already decided that you're not going to report for work.
And once that message gets forwarded to HR or higher management, the context can easily become:
“Employee knowingly decided not to report for work.”
That's not necessarily what the person meant, but wording matters.
What I suggested
I told him to frame it around the circumstance instead:
“I may not be able to report for regular work tomorrow, October 5, due to an unavoidable family commitment that requires my presence.”
That small change makes a big difference.
He's not announcing, “I have decided to be absent.”
He's notifying the team that an unavoidable family matter may prevent him from reporting to work.
He also did the important things right:
Prepared a handover.
Made sure ongoing items were covered.
Stated when he would be back.
Committed to catching up on pending work.
Remained reachable for anything genuinely urgent.
That's what I consider looking out for the team.
Not just making sure your own absence is communicated, but making sure the people you're leaving behind aren't left wondering what happens to your work.
And then there's the lesson behind the lesson
The funny thing is, I didn't come up with this advice myself.
I learned it years ago from an HR person at one of my previous jobs, back when I was working in a hotel.
She taught me that when communicating an upcoming absence, you have to be careful with the language you use.
At the time, it was just another piece of workplace advice.
But apparently, it stuck.
Years later, I'm working in software engineering, and I'm passing that same lesson on to another person.
And honestly, that's one of the signs of a good HR person.
You don't always realize the impact of the lessons they teach you while you're working under them.
Sometimes their advice follows you into your next job.
Then your next one.
And eventually, you're teaching someone else something that they taught you years ago.
I'm still thankful to her
She was actually my first real HR experience.
I originally went to that hotel for an interview as a graphics artist.
There wasn't even a graphics artist position available that day.
And somehow, she still hired me.
She saw something in me and found a way to bring me into the organization even though the position I initially applied for didn't exist.
Years later, I still remember the things she taught me.
And now, one of those lessons helped me look out for a co-worker.
That's pretty cool when you think about it.
A good HR person doesn't just enforce policies.
Sometimes, they teach you things that stay with you long after you've left the company.
And sometimes, those lessons end up helping people they never even met.
So to my former HR:
Thank you.
You probably don't know it, but your advice from all those years ago just helped another developer avoid an unnecessary HR side quest.
And yes, I still remember:
Don't casually write “I'll be absent tomorrow.” 😅