The Risky Role of Hands-On Project Manager

When we designate a hands-on project manager, we're usually hoping to save money by having one person in two roles. The hands-on project manager is supposed to both manage the project and personally carry out part of the work. For small, low-risk projects, it probably works well, most of the time.

And then there are the other times.

The arrangement places the project at elevated risk, both for structural reasons and because of the conflicts of interest inherent in the role.

Schedule collisions

Project managers devise, negotiate, defend, explain, and adjust project schedules, but they can't control unanticipated events. Situations that demand the full attention of the project manager can collide with the parts of the schedule that demand the full attention of the same person as a team contributor.

Conflict of love or fascination

Sometimes, hands-on project managers have a love for or fascination with particular subsets of the project's work. Hands-on project managers tend to assign that work to themselves, independent of whether or not that assignment is a sound project management decision. Some will even contort the project schedule to make this assignment possible.

Distraction

At times when the project management work isn't fun, the hands-on project manager is often tempted to retreat to the hands-on part of the role, and when the hands-on part isn't going well, the hands-on project manager might retreat to the project management part of the role. Sadly, the right choice is usually exactly the opposite behavior.

Teammate risk

A special risk appears when the road gets so rocky that the hands-on project manager must ask for extra effort from the team. Unless everyone believes that the hands-on project manager bears a fair share of the extra load, some might experience resentment, because the hands-on project manager has a conflict of interest. The result can stress the team and its relationships.

Financial conflicts

The possibility Usually, hands-on project managers
have a love for or fascination
with particular subsets
of the project's workof savings from the hands-on project manager role sometimes biases those who decide whether or not a project will have a hands-on project manager. The bias likely arises from underestimating the risks of the combined role compared to a structure with a separation of the roles.

One factor that makes the device of hands-on project manager so tempting to sponsors and managers is the small size of the projects in which it's usually employed. According to this argument, even in the worst case, the downside for the organization is limited, because the project is so small.

But the small size of the project might not provide much protection. For instance, larger projects with big impact might depend on the success of one little project. Or the dependent projects might themselves be small, but the impact of their deliverables on the organization might be considerable. In assessing these risks, it's not the size of the project that matters — it's the size of the consequences. To think otherwise is risky.  Top    Next Issue

Projects never go quite as planned. We expect that, but we don't expect disaster. How can we get better at spotting disaster when there's still time to prevent it? How to Spot a Troubled Project Before the Trouble Starts is filled with tips for executives, senior managers, managers of project managers, and sponsors of projects in project-oriented organizations. It helps readers learn the subtle cues that indicate that a project is at risk for wreckage in time to do something about it. It's an ebook, but it's about 15% larger than "Who Moved My Cheese?" Just . Order Now! .

This article is based on an excerpt from my ebook How to Spot a Troubled Project Before the Trouble Starts, which has much more about the factors that put projects at risk.

Your comments are welcome

About Point Lookout

Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Project Management:

Geese Don't Land on Twigs

Since companies sometimes tackle projects that they have no hope of completing successfully, your project might be completely wrong for your company. How can you tell whether your project is a fit for your company?

Seeing Through the Fog

When projects founder, we're often shocked á#8212â we thought everything was moving along smoothly. Sometimes, with the benefit of hindsight, we can see that we had á#8212â or could have had á#8212â enough information to determine that trouble was ahead. Somehow it was obscured by fog. How can we get better at seeing through the fog?

Nine Project Management Fallacies: I

Most of what we know about managing projects is useful and effective, but some of what we "know" just isn't so. Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully.

Missing the Obvious: II

With hindsight, we sometimes recognize that we could have predicted the very thing that just now surprised us. Somehow, we missed the obvious. Why does this happen?

Vendor Mismanagement

When we outsource knowledge work to vendors, we expect to achieve the desired result with less risk and uncertainty than if we did the work ourselves. But mission creep, mission retrenchment and employee capture can lead to less welcome results.

See also Project Management and Project Management for more related articles.

Forthcoming issues of Point Lookout

Coming June 4: White-Collar Contractor Sabotage

Modern firms in competitive, dynamic markets draw on many types of employer/employee relationships, including contractors. By providing privileges and perks preferentially among these different types, they risk creating a caldron of resentments that can reduce organizational effectiveness. Available here and by RSS on June 4.

And on June 11: More Things I've Learned Along the Way: VI

When I gain an important insight, or when I learn a lesson, I make a note. Example: If you're interested in changing how a social construct operates, knowing how it came to be the way it is can be much less useful than knowing what keeps it the way it is. Available here and by RSS on June 11.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenubcqSvusyBsQaEDwner@ChacfhuriyFKgDguTpuYoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

• Get 2001-2 in Geese Don't Land on Twigs (PDF, )
• Get 2003-4 in Why Dogs Wag (PDF, )
• Get 2005-6 in Loopy Things We Do (PDF, )
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
• Get 2009-10 in The Questions Not Asked (PDF, )
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info