Several years back a colleague of mine (I'll call the colleague "Nellie") was managing a very high-visibility project. This project was high on the radar of key executives all the way up to the CEO of the company and any major mis-steps would send fireworks up the chain faster than lightning.  This was one of those "thrill-seeker" projects; definitely high risk but also of high reward if the project was successful.  Nellie was up to the challenge and willingly accepted the assignment.

Talk about your character-building experience...

I was a young hot-shot project manager on an engagement that I had sold to a client.  I had it all planned out and had delusions of completely delighting my client with an issue-free project.  It all seemed so simple, then the project started...and never finished.

I'll spare you the gory details of my harrowing experience but what I can tell you is that I put more focus on selling and planning the project than I did on its execution.  I took a naive attitude of the project being able to pretty much run itself with some junior analysts running the day-to-day aspects of the work.  It blew up in my face and I got booted from the client never to return again.  It was my inaugural visit to the project management guillotine. 

Some time back I was responsible for a portfolio of projects being done within the finance organization of my company.  One of the projects was outsourced to a large consulting firm who supplied the project management, analysis, and development resources to the project.  I would hold weekly meetings with the project manager who consistently gave me a "thumbs up" on the project up to the first key milestone being hit.  When the week of the first milestone approached, he announced that the milestone was going to have to slip by a week to ensure successful delivery.  The next week came along and again the project slipped a week.  This went on for two more weeks with the promise of "we'll for sure nail it next week."  I decided to do some crawling around the project to assess where the project was really at.  Turns out we were at least a month away from delivering to the milestone which was already a month late.

Excerpted from The Project Management Advisor - 18 Major Project Screw-Ups And How To Cut Them Off At The Pass (Prentice Hall, 2004)

So we've all been to the doctor.  We know the feeling of getting marched into a sterile examination room, given a gown that only covers the front half of your body, aked to step on a scale, prodded with a thermometer, asked to pee in a cup.  Then there's what seems like an eternity of sitting on an examination table with your hind quarters hanging out waiting for the doctor to come in the room.  Then after what seems like an eternity the door bursts open and the doctor pronounces, "Hello, I'm Dr. Goofleblat..."

I love baseball.  I love watching the strategies, the big plays, the colossal errors (anyone remember poor Bill Buckner?) and the dramatic finishes.  The Tampa Bay Rays, who in nine of their first ten years of existence finished dead last in their division (In 2004 they managed to beat out one team and finished fourth in their division), surprised everyone in 2008 by beating out such teams as the Boston Red Sox and the New York Yankees and made it to the World Series only to lose to the Philadelphia Phillies.  Even though they lost the World Series, they were heroes in the eyes of millions who rooted for them and their storybook season. 

One strategy that I particularly enjoy is the use of specialty players, of which the most prevalent is the "closer".  The closer is a pitcher who is brought in for just a very short period of the game (typically the last inning of a game) to shut down opponent hitters and either secure a win for their team or allow a team who is behind to catch up in their last at-bat.

So maybe you think you're all that and a bag of chips and that you can get more things done than most people in your organization.  As managers, though, it's not just about you getting things done on your own; it's about you getting your team to be as effective (or more) as you.

I deliberately use the term effective versus efficient.  For me, there is a very clear distinction which I believe is crucial in driving results.

In an earlier leadership role I had been striving to create focus and accountability within each of our major work areas.  The team responded beautifully with doing their best to adjust to roles, to stay focused on their areas, and to minimize confusion by stepping across boundaries.  They did exactly as I asked.

We were in a team meeting and I could see that there was erupting confusion around contacting customers in an effort to close some sales.  There was a lot of respect for my sales & marketing manager in not stepping in on her turf when it came to customers. Where the problem arose, though, was in the fact that the team was confused as to who was supposed to be following up on some key sales activity that had begun prior to our organizational re-alignment.

Some time back my son and I participated in a service project to help a young family clean out a back yard.  At one time the yard was a wonderful oasis with a swimming pool, lush garden, and beautiful walkways.  The once beautiful oasis was neglected over time and became an overgrown jungle of northwest foliage with its prime resident being thorny blackberry bushes.  The blackberry bushes were six feet tall and covered most of the yard.  What a prickly mess!

I’ve noticed an interesting trend in working with my clients.  There is an increased focus on companies assembling project teams comprised of cross-organizational team members to solve problems. This is increasingly being done in favor of single organizations trying to produce results on their own.  More and more project teams are taking on "virtual" characteristics where teams are temporarily assembled and could be located anywhere in the country or the world.