I love my nieces and truly enjoy spending the holidays with them, but this year, I returned home with a very bad cold. And, as I usually do, I forced myself to go to work with it (although I did work from home for a few days, since there was no way to get that much Kleenex at work 🙂 ). This is a bad habit of mine. I have gone to work with walking pneumonia, viral meningitis, swine flu, and countless colds with less ominous names. Why? It’s what I was taught.
At my first post-college job (as a chronic migraine sufferer–thankfully I’m not any more!), my first review went something like this:
“You’re completely amazing. We would need six people to do all the work you do. However, you take all of your sick time, so we’re rating you a 4 out of 10.”
And my bad habit was born!
That said, many geeks–especially IT geeks–do the same thing. They’re aware that the company needs them to come in and fix things, so they drag themselves to work and infect everyone else. The problem is exacerbated by the rigid way that many companies count sick time; many geeks have to save their time for sick kids, etc.
Counting sick time rigidly and creating a culture of coming in despite illness backfires. Sick people infect other people, who perform poorly or take time off. This costs companies much more money than simply letting people stay home when they’re sick!
As such, I was quite impressed by HubSpot’s recent time off policy change. They stopped counting time. They said that they were fully cognizant that everyone put in more than 40 hours/week, and we were professional enough to handle balancing getting our jobs done with taking time off. What does this mean for me? I’ll probably be more likely to stay home when I’m sick. Sure, I’ll work from home (since I’m a type-a workaholic), but my coworkers have much less to fear!