Month: June 2008

On Flex Time: How to Fail

In my last post about making flex time successful, I talked about some best practices that I find make flex time a beautiful thing for everyone involved. Now I’ll chat about how to completely fail with flex time.

  1. Be grouchy about it. Your employees aren’t stupid, and they know when you’re unhappy about something. If you resent employees who have flex time, you’ll damage their morale, and give other employees good reason to be grumpy about their co-workers’ arrangements.
  2. Don’t listen to complaints. Let’s say you have an employee who works weekends and takes off Thursdays and Fridays to take care of the kids. This arrangement seems fine, and then you have a huge roll-out that is scheduled to go live on a Thursday. This employee, a vital engineer on the project, might not think that he needs to be there on that Thursday. People complain, and you just shrug. The roll-out is harder, morale suffers, and people start resenting the flex person. This is sub-optimal for teamwork, to say the least.
  3. Don’t plan for it. Make sure you remember that someone has a four-day week when you’re planning projects and schedules. You cannot always depend on that person to show up on every Friday to make up for your poor planning–wouldn’t that defeat the purpose of flex time?

I’m sure there are many other creative ways to fail at flex time, but I’m hoping that these two entries will help you avoid them.

On Flex Time: Making it Successful

I blogged a bit about flex time in my post On Insomnia, but I’ve been thinking about what makes flex time successful (or not!), and I thought I’d post my thoughts here. This post is about what to do to help make flex time successful (my next will be on what might cause flex time to fail).

  1. Bilateral flexibility. Both the employer and the employee must be flexible. I had an employee once who worked a 4-day 32-hour work week, and did not work on Fridays (when daycare was closed). However, if I ever needed her to come in on a Friday for a large project or emergency, she put her son in back-up care or called on a relative and was there. Likewise, if she ever wanted to trade a Tuesday (or other day) for a Friday, I let her do so as long as the work allowed it. The bilateral flexibility made this arrangement a resounding success.
  2. Core hours. In order to facilitate teamwork (and I’m not sure there are many modern work environments that don’t need teamwork!), core hours are vital. Team members need to know when they can find each other for questions, brainstorming, etc. I held core hours for my last department to 9:30-4:00, which were hours when everyone’s work schedule overlapped. If I were working in a software company, I might set those hours to 11:00-3:00 in order to handle both my night owl programmers and the crazy early birds who need to pick their kids up from school.
  3. Don’t give flex time if the job isn’t flexible. While it’s admirable for all companies to want to grant flex time, sometimes it just isn’t happening. Nursing shifts have to start and end at specific times. Utility trucks have to all roll out at a certain hour. The help desk has to be covered from 8:00 AM-8:00 PM.
  4. Be honest during the recruiting process. If the job isn’t flexible, don’t tell a great candidate that he or she might be able to negotiate it later. Be up-front about expectations during the initial interview in order to recruit and keep great employees (this goes for much more than just flex time).
  5. Don’t only grant flex time to your favorites. If someone in a certain job has flex time, you have to be prepared for everyone else in the same role to ask for it. If you only granted it to one person due to special circumstances, be honest and communicate the circumstances (within reason–don’t disclose private HR issues) to that person’s co-workers.

Stay tuned for my next flex time post on mistakes I’ve seen (not just the flip side of the five best practices above–honest!). I figure it’ll come out next week…

On Maturity

Overall, I think that maturity is overrated. That is, if we define maturity as being boring, steady, and un-creative, which is how most “mature” people I’ve met in the business world define it. If we define maturity, however, as being well-balanced, able to have fun, able to be creative, and able to get the job done while enjoying it, then I think we should all be more mature.

I fell into the trap of assuming that I had to be mature (by my first definition) when I first became an IT Director. I stood up straight and suppressed some of the odder aspects of my personality. I probably wasn’t much fun to be around, and I guarantee I wasn’t having much fun–I lost a lot of weight from the stress.

Then I hired a computer training specialist. Who had many years of law firm experience and who had served in the Army Reserves for even more years. He was about 6 years older than I, and really knew how to be professional. He seemed well-adjusted, and the users loved him.

Then he brought in a wooden bear that, when you lifted its head, pooped M&Ms.

My wacky side loved it, but since it was right outside the HR Manager’s office, I held my breath and ignored it. One day, I sheepishly poked my head into her office, and she said she thought it was a hoot.

A hoot?

Turns out I didn’t really know the real meaning of maturity. A truly mature person knows how to have fun at work. Get the job done? Absolutely. But even more important is getting the job done while enjoying being there. You’re happier. Your team is happier. Staff stays longer at their jobs, and you only have one scotch at the end of the day (and that because you actually like scotch).

Okay; so making staffing decisions by allowing them to duel it out with flying monkeys at 10 paces might have been a bit much, but…

The Grammar Geek: Over Their!

I completely forgot my weekly “Leading Geeks” post, but since I actually get more hits on this blog for the Grammar Geek posts, I figured I’d write this one.

Most of you know about the classic there/their/they’re confusion:

  • There: is a pronoun that refers to a place that’s not here :).
  • Their: possessive pronoun meaning something belonging to them (whoever they are).
  • They’re: a contraction of “they are”.

And yet people mix them up all the time. My theory? Carelessness. I’ve actually caught my fingers typing the wrong one randomly (Fingers? Meet brain. Brain? Fingers.). If I don’t re-read my work, I sometimes find that I’ve sent an email using the wrong form!! The horror!

If you never really knew the difference, now you do. If you’re wondering why your fingers and brain occasionally disconnect, I can’t help you, but let me know if you ever figure it out (I have a theory it has something to do with habit). Just re-read before hitting send, print, or publish, and you’ll catch most of your mistakes.