January 13, 2010 – An “OH [INSERT EXPLETIVE HERE]!” Moment

I bolted awake at 5:11 this morning…heart pounding, mind racing…to the sound of rain. Living in Southern California, it isn’t a sound I hear all that often, but it is one that strikes fear into my heart. Lest one think that I suffer from Ombrophobia, I actually enjoy a good rain storm. I miss the huge thunderstorms we had growing up south of Buffalo, NY. My true fear of rain rises from the list of my belongings sitting outside that are not intended to get wet.

Today it was the seat from our van, removed a month ago to make traveling easier for my daughter and her sprained ankle. Originally placed in the garage, it was sitting, exposed, on the patio where she had dragged it to sit in the sun.

It was indeed an “Oh [INSERT EXPLETIVE HERE]!” moment. Your mind, body and soul leave their peaceful ignorance and arrive, adrenaline pumping, heart stopping, in total awareness. I’ve had a few of those moments:
• Calculating the cost of sending my daughter to college next year
• Reading the scale the last time I weighed myself
• Opening the email telling me my team lied to me
• Checking the deadline on the project
• Realizing that my last blog was on April 6 of last year
• Getting called in to your manager’s office on the day they announce layoffs

I was reminded again that these moments are the result of choices we make every day. It usually isn’t the big decisions that trip us up. We tend to put a lot of thought into those. It is the little ones that nail us.

How many times did I walk by that seat and think, “That needs to be put back in the van” and did nothing about it? How many pieces of chocolate did I eat between Thanksgiving and New Years? Why didn’t I put either the dog or the garbage out before leaving the house?

Those haunting questions have driven me to take the Choice Challenge. By following these 5 steps, I predict you can drastically reduce your number of “those” moments.

1. Establish Priorities. Without priorities, nothing is important. You may think it is the opposite (i.e. everything becomes important), but life doesn’t work that way. Note to Tiger Woods: A moment (or moments) of excitement with a mistress is not at the same level as your family or your career.

2. Define Achievements. Set bench marks for yourself and head toward something. All great non-goal examples begin “perhaps this is the year I will…” or “wouldn’t it be amazing if….” Drop the “perhaps” and dreaming pieces and establish some real goals.

Having a happy, involved, and loving family would be a great achievement. Is it something you are going to leave to chance or are you willing to work at it?

3. Recognize Your Choices. When your phone rings, you have a choice: interrupt what I am doing or allow the caller to leave a message. Your reaction to a situation or individual is a choice: do I immediately yell and throw a fit or take time to plan my revenge… I mean response? Should I watch reruns on TV or work on my book?

Waiting until after you have eaten a candy bar to think about your diet doesn’t work. Believe me, I’ve been there.

4. Evaluate each Choice against your Priorities and Achievements. Many things are not bad, they just don’t get you where you need to go. Doing your timesheet is a good thing, unless you have a Director waiting for a report. Staying late at work to get ahead is great, unless it is your anniversary and your wife is waiting for you.

5. Make the right choice. Nine times out of ten you know what the right thing to do is. Have the courage and strength to pull the trigger on the right choice. You could avoid having another “Oh…” moment.

One of my achievements this year is to begin writing again… that and to get that chair dried off and back in the van.

April 6, 2009 – Going Covert, Part 6

NOTE: On January 12, Computerworld published an article I wrote entitled Covert PMO. This series of entries is a fictional account based on the Project Manager in that article. Any resemblance to anyone from my past, present or future is purely coincidental. To start at the beginning, jump to January 1, 2009 – Going Covert, Part 1.

Day 27, Tuesday – Management meetings have been switched to Tuesday. That actually works out well. On Monday’s I approve last week’s time, update the schedule and fill out the status report on line. In Tuesday morning’s standing meeting I confirm the status in time to make any last minute updates before the firing squad.

Speaking of firing squads, I think I’ve found a way to turn the tide on the management meetings: shoot yourself first. It sounds drastic but it seems to work.

Today I came in with my usual reports. This time, instead of waiting for the barrage of questions and going on the defense, I attacked…myself. I had already asked myself all of the questions I knew they wanted to so I walked through them all before they could start.

“We are currently 2 weeks behind schedule. In order to make the deadline I have asked the team to fast track some of the testing. We’ve completed the extract and started the data conversion and transfer pieces. While that is happening we’ve used Excel to generate a test file for the vendor, Counseling Phone Support (CPS), to use.

“There are 2 major risks to the project: 1) any additional changes to the format or content of the data. 2) The inability to make web services work as the interface.

“Because the probability of either of these remains high, I have an individual finalizing a manual means to produce the file and FTP it to CPS for processing. It may be labor intensive but we could extend the project indefinitely by supplying the data by hand.”

I answered most of their questions before they even asked them. I even threw in some they should have asked. For those I didn’t have answers to I brought the acknowledged the issue and told them when I thought there would be an answer.

Some of them looked bored. Quite a switch from the last meeting I had with them.

Day 28, Wednesday – Wednesdays always offer a little breathing space. The rush for the end of the week hasn’t started quite yet and all the reports are done. It gives me a chance to “walk around” and check with the team. It’s a bit easier when they are all co-located but I try to touch base with most of them somehow during the week. Still trying to work out the video thing with the offshore team.

Back to the PM problems. If I remember correctly we had just solved world hunger and started on world peace. No, that wasn’t it, but it sometimes helps to put this into perspective. There are a lot bigger problems in the world than the Business getting the requirements right the first time.

Estimated End Date: Deadline was set before anyone really estimated the effort.

We identified 3 types of estimates: Ballpark Estimate, Budget Estimate, and Detailed Estimate.

Ballpark Estimate is used the first time an idea is tossed out. It could be as much as 75% low because we only know the bare minimum.

Budget Estimate is given after a set of high level requirements is reviewed and an impact assessment team has reviewed it. This estimate can be up to 25% low and have a realistic duration. The end date should be announced until the project actually starts.

The Detailed Estimate is done while the design is finalized and should be within 10% of the final cost. End date should be set.

As a group we’ve decided to start using the terms. Without management support we can’t enforce it, but consistency may breed familiarity and that can lead to acceptance.