Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 11, Issue 19;   May 11, 2011: Guidelines for Sharing "Resources"

Guidelines for Sharing "Resources"

by

Often, team members belong to several different teams. The leaders of teams whose members have divided responsibilities must sometimes contend with each other for the efforts and energies of the people they share. Here are some suggestions for sharing people effectively.
Vortex cores about an F18 fighter jet

Vortex cores about an F18 fighter jet. The figure depicts vortex cores overlaid with streak lines. The vortex cores are represented by black line segments and the streak lines are colored by time at release. Creating turbulence drains energy from the aircraft. So it is with organizational turbulence — the chaotic group behavior that happens when too many different tasks compete with each other for people with skills that are in high demand within the organization. Even though all the projects might eventually be completed successfully, we can consider organizational turbulence to be the scurrying related to finding people and holding onto them until their work is complete. That activity (the scurrying) drains energy from the organization by adding costs to almost everything it does. Photo courtesy U.S. National Aeronautics and Space Administration.

First things first: when referring to people in the abstract, I prefer words like "someone," "person," or "people." I dislike the word "resources," which, to me, evokes things like equipment, timber, and coalmines. OK. That's out of the way.

When team members have responsibilities to multiple teams, those teams all face risks. The unexpected happens. Priorities change. Schedules change. Time commitments cannot always be honored. We might try to schedule our efforts, but when team members belong to multiple teams, the plan and the reality are sometimes wildly different, even if the root cause of the trouble is elsewhere.

Here are four guidelines for sharing people more effectively than we often do.

Front-load the activities of shared people
Trouble sometimes arises in partner efforts. If resolving that trouble requires additional time from someone you share, you could lose access to that person. Moreover, even if the partner project goes smoothly, difficulties in other projects could result in schedule changes for the partner project, and the shared person might not be available at the time you scheduled.
If possible, schedule your own efforts so that the work that shared people do happens early.
Adjust effort estimates for interruption of flow
During planning, when we estimate effort, we often assume that the person doing the work is doing nothing else. Since that assumption is invalid for people with divided responsibilities, and since juggling multiple assignments does have associated costs, our estimates tend to be lower than the actual time required.
Make estimates that realistically account for the loss of time due to multiple assignments. When tracking actual effort data, track assignment multiplicity, too.
Combine hours into the longest possible contiguous bursts
To minimize Combine hours into the longest
possible contiguous bursts
losses due to interruption of flow in the context of split assignments, combine hours of effort for each person into the largest possible contiguous chunks. Instead of one day per week for six weeks, schedule two days per week for three weeks, or four days in one week, and two days three weeks later.
You might have to negotiate with partner team leads, but when they understand the advantages of contiguous bursts, the negotiations are likely to be smooth.
Avoid the "MS Project flat rate syndrome"
Planners tend to use as weekly effort estimates for each person, the total estimated effort for each person divided by the task duration in weeks. Rarely does work actually proceed in this way. Even if it did, such a pattern maximizes the losses due to multiple assignments, because it maximally interrupts flow.
Actual work is usually performed in bursts. Use your project planning software to schedule those bursts.

People with multiple assignments are usually less effective than they would be if they had only one assignment. And they might be called away at any time. Plan for it. Go to top Top  Next issue: How to Create Distrust  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!

Your comments are welcome

Would you like to see your comments posted here? rbrendbTtLLSVlUPPCNkAner@ChacthFxWKdRwnLylOCDoCanyon.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.

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:

A Katrina rescue in New OrleansLong-Loop Conversations: Asking Questions
In virtual or global teams, where remote collaboration is the rule, waiting for the answer to a simple question can take a day or more. And when the response finally arrives, it's often just another question. Here are some suggestions for framing questions that are clear enough to get answers quickly.
Edward Bernays, nephew of Sigmund Freud and an early pioneer in the field of Public RelationsCommunication Traps for Virtual Teams: I
Virtual teams encounter difficulties that rarely confront face-to-face teams. What special challenges do they face, and what can we do about them?
Robert F. Scott and three of his party arrive at a tent left by Roald Amundsen near the South PoleManaging Non-Content Risks: I
When project teams and their sponsors manage risk, they usually focus on those risks most closely associated with the tasks — content risks. Meanwhile, other risks — non-content risks — get less attention. Among these are risks related to the processes and politics by which the organization gets things done.
The Great Wall of China near MutianyuScope Creep and Confirmation Bias
As we've seen, some cognitive biases can contribute to the incidence of scope creep in projects and other efforts. Confirmation bias, which causes us to prefer evidence that bolsters our preconceptions, is one of these.
North Fork Fire in Yellowstone, 1988The Risks of Too Many Projects: II
Although taking on too many projects risks defocusing the organization, the problems just begin there. Here are three more ways over-commitment causes organizations to waste resources or lose opportunities.

See also Project Management and Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

The future site of 2 World Trade Center as it appeared in 2013Coming October 5: Downscoping Under Pressure: I
When projects overrun their budgets and/or schedules, we sometimes "downscope" to save time and money. The tactic can succeed — and fail. Three common anti-patterns involve politics, the sunk cost effect, and cognitive biases that distort estimates. Available here and by RSS on October 5.
A hummingbird feeding on the nectar of a flowerAnd on October 12: Downscoping Under Pressure: II
We sometimes "downscope" projects to bring them back on budget and schedule when they're headed for overruns. Downscoping doesn't always work. Cognitive biases like the sunk cost effect and confirmation bias can distort decisions about how to downscope. Available here and by RSS on October 12.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendbTtLLSVlUPPCNkAner@ChacthFxWKdRwnLylOCDoCanyon.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:

Reprinting this article

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

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.