No matter how you slice it, being super-human may not be enough. By all accounts, whether you were an ancient Greek or Roman, Hercules was "the man." Hercules' legendary exploits were so popular, ancient Romans like Marcus Antonius (Mark Antony) wanted some of that Hercules mojo for themselves. Antonius went so far as to invent a son for Hercules, named Anton, to make the connection to his family tree.Despite his divine parentage and his incredible strength, in the end, it was an act of jealousy that took his life. He was poisoned from an arrow that had previously killed one of his enemies (the centaur Nessus) and was administered by his wife, Deianerira, who thought he had fallen in love with another woman. Even his father (Zeus or Jupiter depending on whether or not you were Roman or Greek) couldn't save him.
I have observed that the same is true when "Herculean" efforts are required, or even perceived to be required, for project success. No matter how incredible your personal stamina may be, if every project you lead takes heroic efforts to be successfully accomplished, you will ultimately crash and burn just like Hercules (whether or not your spouse administers poison to you).
I came across an interesting article from CIOZone a couple of months ago, Be Honest About YOUR Boundaries, in which the author suggests that the problem with the expectation of 24/7 availability by your boss may be self-inflicted. The author describes a common scenario with a new boss, a critical project, and working extra hours to impress. Over time, he or she just expects that you carry your Blackberry or iPhone at your hip and will answer emails at any time day or night. "Whose fault is this?" she asks. "It's your fault, isn't it?"
She continues, "You were so eager to make a good first impression that you forgot that setting expectations is a two-way street. You have now set an expectation that you are available 24/7. You didn't necessarily ask for it. But you did demonstrate willingness to work-related communications all night and all weekend."
My wife has kicked me in the pants dozens (if not hundreds) of times over the course of my career for this same thing. I'll admit that even now, every time my iPhone chirps at me, I look to see what it is. And, as I glance up from my iPhone to my beautiful wife sitting across the table from me at our favorite restaurant, I think she wants some of that centaur poison for me.
Of course there are times when extra effort is required to accomplish a critical project. However, those times should be the exception rather than the rule. If your boss sees you working long hours all the time, he or she might think that's just how you work. Or worse, that you don't know how to effectively manage your time. Either way, it will be taken for granted that you are going to work that way all the time.
That being said, the need for heroic efforts all the time could indicate that your project is in trouble. A project running on schedule should really require little or no overtime. Working long hours is often just a quick fix, leading to poor employee health from too much caffeine, too many late nights, and too much junk food. I have also noticed that the ratio of mistakes to accurate work increases exponentially for every hour or two you're in the office after nine or ten hours.
Leverage project management software or other project management tools to help you manage projects more efficiently and ease the burden on your schedule. Engage the team in helping establish legitimate timelines and milestones—giving them a greater sense of ownership and you a few extra minutes to tackle one of the dozen other things you need to accomplish right now. Don't try to do it all yourself. I once worked with a fellow who felt he needed to do everything himself. It wasn't long before he was burnt out and ineffective. Don't let that happen to you.
Remember, super-human strength wasn't enough for Hercules—and it won't be enough for you either.
What are you doing to minimize the need for heroic project efforts on a regular basis?






It's hard to believe how fast 2010 shot by. I'm still consciously writing the new date down on notes and other documents. Hopefully, by the end of the week writing 2011 will feel as natural as writing 2010. I don't know about you, but I seem to go through this every year—for at least a week or two.
After taking a couple of extra days off to celebrate the holiday, it's nice to be back in the saddle. Yesterday, as I was going through my daily routine, I came across an excellent blog post by Bas de Baar, better known as the Project Shrink—
In the spirit of the season, since this will be my last post until after the holiday, I thought I would write my post to the tune of Jolly Old Saint Nicolas. Feel free to sing along:
Most of the project management methodologies utilized today in traditional project management practice evolved from creating and managing the processes used in developing the assembly lines of the early industrial revolution. The next big push in project management thought, in my opinion, came with NASA and the race into space. The list of benefits from the space race is long and varied, Tang and titanium being two of them. You might even be able to include project management software on that list, although I believe it is more likely directly attributable to independent aerospace contractors than NASA (although sometimes I get carried away and could be writing revisionist history here).
The dirty little secret of project management is that after all these years of software development, the tools have become so complicated that end users don't use them. If you're like me, there were times when I had to spend (waste) time reminding, cajoling, even begging my team members to update their status information in the project management tools we were using at the time. Or worse, I had to guess as to what real project status was.