So a colleague said something interesting to me about project management:
The best day of project management is usually the first day, but I want to show you that the best day is really the last day of the project.
And as I thought about this, I sort of starting laughing to myself and thinking, you know what, I think this guy has something here.
– Day 1 of a project, everyone is usually all bright-eyed and bushy-tailed.
We’re embarking on an adventure together to build something new for the organization and our customers.
We’re going to team up and everyone will contribute.
And out of the project sausage maker–poof!–like magic comes a new system or product.
– But as we all know, things don’t always go so smoothly.
With some projects, the pretty smiley faces of day 1 may quickly turn to ugly frown faces.
There is analysis paralysis, scope creep, conflicting or changing priorities, resource issues, technical challenges, or the sausage just doesn’t come our right–oh sh*t!
Thus, many projects end up going bust in terms of cost, schedule, or performance.
That is, they end up costing too much, being delivered behind schedule, or just not meeting the performance requirements.
You have some projects that never even truly get off the ground, have multiple resets, or get dumbed-down or even cancelled altogether along the way.
So by the time you reach the last day of the project, many people seem like they’ve been through the project ringer.
I’m sure that I’ve heard more than one project manager say:
Just take me out back and shoot me!
So when this colleague said that he wants the best day of the project to be the last–in terms of satisfaction with the project (not that that pain was finally over!)–I really appreciated this as an awesome goal.
We should all look to the last day of our projects as the best–one where we can look back and say:
Wow, great job everyone! We really got something great done here–and we did it right! 😉
(Source Photo: Andy Blumenthal)