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.
- 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 welcomeWould you like to see your comments posted here? rbrenrDUDwWaUxOAJtKFRner@ChaclWPJpPZohNvtYLEJoCanyon.comSend me your comments by email, or by Web form.
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.
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.
More articles on Project Management:
- Declaring Condition Red
- High-performance teams have customary ways of working together that suit them, their organizations,
and their work. But when emergencies happen, operating in business-as-usual mode damages teams —
and the relationships between their people — permanently. To avoid this, train for emergencies.
- Nine Project Management Fallacies: II
- Some of what we "know" about managing projects just isn't so. Identifying the fallacies of
project management reduces risk and enhances your ability to complete projects successfully.
- The Politics of Lessons Learned
- Many organizations gather lessons learned — or at least, they believe they do. Mastering the political
subtleties of lessons learned efforts enhances results.
- How to Make Good Guesses: Tactics
- Making good guesses probably does take talent to be among the first rank of those who make guesses.
But being in the second rank is pretty good, too, and we can learn how to do that. Here are some
tactics for guessing.
- How We Waste Time: I
- Time is the one workplace resource that's evenly distributed. Everyone gets exactly the same share,
but some use it more wisely than others. Here's Part I of a little catalog of ways we waste time.
Forthcoming issues of Point Lookout
- Coming December 11: The Rhyme-as-Reason Effect
- When we speak or write, the phrases we use have both form and meaning. Although we usually think of form and meaning as distinct, we tend to assess as more meaningful and valid those phrases that are more beautifully formed. The rhyme-as-reason effect causes us to confuse the validity of a phrase with its aesthetics. Available here and by RSS on December 11.
- And on December 18: The Trap of Beautiful Language
- As we assess the validity of others' statements, we risk making a characteristically human error — we confuse the beauty of their language with the reliability of its meaning. We're easily thrown off by alliteration, anaphora, epistrophe, and chiasmus. Available here and by RSS on December 18.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenrDUDwWaUxOAJtKFRner@ChaclWPJpPZohNvtYLEJoCanyon.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 words in your inbox in one hour. License any article from this Web site. More info
- The Power Affect: How We Express Our Personal Power
Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.