Can You Be In at 6:00 Tomorrow?

Can You Be In at 6:00 Tomorrow?

Image from Wikipedia

I think you can tell a lot about a person by their response to the question, “can you be in at 6:00 tomorrow?”  I don’t think the right answer is, “YES” or “NO”.  I think there’s a thought process that responsible, hard-working people take to the process.  I think that process goes like this:

  1. Why?  There are good reasons to be in the office at 6:00 and there are bad ones.  If there truly is a time sensitive issue that needs to be addressed before business, then fine.  If its something I can do tonight before I go home, you owe me that option.  Furthermore, if its not really necessary for me to be there, don’t ask me to be.  I’ll resent you thoroughly for it.  If you’re the kind of manager who measures my contribution by the time on the clock when I’m coming and going, we won’t be working together long.
  2. Assuming all those questions are answered to my satisfaction, the answer is YES.  If you can’t handle days that require you to be in the office at 6:00, then don’t work for a startup.  When you’re working for a company of a couple dozen, any one person dropping the ball can be heard around the office.  These pressure moments when you see everyone coming together to get a product out the door should be the ones that you’re excited about, not the ones that you dread.  I’m here in the office at 6:00 this morning waiting for a build of our product from the developers that I can test before showing it to some clients at 9:00 and I’m excited.  The team made some amazing progress on it overnight and I’m excited to share that with my clients at 9:00.

What gets you excited enough to get out of bed at 6:00?

  • Guest

    On the other hand, if you're testing a product at 6:00am for release at 9:00am you have some serious organizational problems in your development process that reach far beyond minor hiccups and the occasional need to be in at 6:00am.

    Personally, I'm a much bigger fan of better planning, and leaving product feature decisions to people who actually understand the full scope of the product, instead of pulling massive amounts of resources in at the last minute because of oversights and omissions.