Sunday, May 11, 2008

Distraction: Project Enemy #1

Over the years, I've come across many common barriers to project success. One that stands out above all others is what I'd simply refer to as "distraction."

Resources are not able to commit to projects, are rarely co-located (physically or electronically), and are spread across too many concurrent efforts (on both project and non-project work).

Project managers are distracted by being asked to take on too many projects, and by adhering to overly rigid methodologies and using cumbersome tools.

When you think about it, how many projects undergo significant delays, or stretch out over months, when, if the team were dedicated to the project, and the customers and suppliers were heavily involved, it could be done in a matter of weeks? Then, perhaps additional projects could be squeezed in, with everything being done in a more focused manner.

This distraction not only delays projects, dilutes efforts, and causes errors (due to lack of attention to detail), it drives the focus away from the client. Instead, everyone is just trying to "execute tasks," independent of the outcomes and value of the project. The devil is in the details, and if everyone's efforts are diluted with a dozen simultaneous initiatives rather than being focused on the client and the outcome, nobody will catch the details---guaranteed.

If we did nothing other than solve the distraction problem (for both the team members and the project manager), all the other pieces would likely fall into place. We'd have more focused efforts, more productive teams, and---ultimately---better outcomes.

2 Comments:

At 4:00 PM, Anonymous Demian Entrekin said...

I'd like to hear more about your views on an overly rigid methodology and how that presents a distraction.

For my view, this can be especially troublesome when you are working on something that is more creative than rote. For example, a greedfield R&D project is quite different from a network-wide router upgrade.

Standardization is key to manage-ability and reuse, but it must be loose fitting so that it fits all kinds of personalities. Thoughts?

 
At 5:11 PM, Blogger Jerry Manas said...

Demian, I couldn't agree more. I've often said that an overly rigid methodology, and its close cousin, overly cumbersome EPM tools, are two of the highest forms of distraction, as they take away focus from the real work being done, and more importantly, the customer.

Frameworks need to be flexible, and ideally tiered to suport multiple types of projects, and multiple levels of complexity and uncertainty. You can't plan an R&D project the same way you construct a building. When we apply a "one size fits all" methodology to an incompatible project, we get the ultimate in distraction.

 

Post a Comment

Links to this post:

Create a Link

<< Return to PMThink! Project Management Gateway