
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 burstslosses 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. Top
Next Issue
Are 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? rbrenubcqSvusyBsQaEDwner@ChacfhuriyFKgDguTpuYoCanyon.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.
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:
The True Costs of Cost-Cutting
- The metaphor "trimming the fat" rests on the belief that some parts of the organization are
expendable, and we can remove them with little impact on the remainder. Ah, if only things actually
worked that way...
Backtracking in Incremental Problem Solving
- Incremental problem solving is fashionable these days. Whether called evolutionary, incremental, or
iterative, the approach entails unique risks. Managing those risks sometimes requires counterintuitive action.
How to Make Good Guesses: Strategy
- Making good guesses — guessing right — is often regarded as a talent that cannot be taught.
Like most things, it probably does take talent to be among the first rank of those who make conjectures.
But being in the second rank is pretty good, too, and we can learn how to do that.
Scope 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.
The Planning Fallacy and Self-Interest
- A well-known cognitive bias, the planning fallacy, accounts for many unrealistic estimates of project
cost and schedule. Overruns are common. But another cognitive bias, and organizational politics, combine
with the planning fallacy to make a bad situation even worse.
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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenubcqSvusyBsQaEDwner@ChacfhuriyFKgDguTpuYoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
