
Congestion on a U.S. highway. One common example of the nonlinearity of systems is the traffic jam. At low densities, adding one more vehicle to the stream of traffic has no measurable effect on the speed of the other vehicles. But as density increases, traffic slows, until it reaches a state like the one shown. How can this be? This phenomenon occurs because of interactions between the vehicles. That is, the natural flow rate is a nonlinear function of vehicle density. Photo courtesy U.S. Department of Transportation.
More often than we'd like, our projects are late or over budget. Or we find that the problem we've tackled is much more difficult than we thought. We aren't stupid (though some might argue otherwise), and we aren't trying to gild lilies our build empires (though some might argue with that, too). Still, these things happen with such regularity that there must be an explanation.
Part of the answer might be that much of the work we do is of a nature that our minds have difficulty comprehending. One property that gives us trouble is nonlinearity.
For example, consider the issue raised by Fred Brooks. [Brooks 1982] If three people can complete a task in six months, many would suppose that nine people can complete it in two months. We now understand that this belief is unfounded, and that our expectations are rarely met.
To understand why, let's begin by defining linear work. Work is linear when the outcomes are directly traceable from, and scale with, inputs. When work is linear, we can successfully plan the outcomes before we begin, because we can predict the course of the effort. To make linear tasks go faster, we can divide them into parts that we execute in parallel, without risking complication.
For example, two identical, independent assembly lines can produce output at double the rate of one single line, assuming that their supply and delivery chains are also independent. A manufacturing process implemented as independent assembly lines is a linear process.
But In a system that doesn't
obey superposition, the whole
can be different from
the sum of its partsnonlinear work doesn't follow this pattern. Although most of the work we do in project-oriented organizations behaves linearly in response to small adjustments, the nonlinearities dominate when we scale those adjustments to a size where we expect to derive large benefits. One attribute of nonlinear work that explains this phenomenon is its failure to obey superposition.
In a system that doesn't obey superposition, the whole can be different from the sum of its parts. In such cases, as we apply more and more resources, the yield per unit of resource can decline. In the case of Brooks's mythical man-month, this can happen because of increased need for management and communication, and increased difficulty in scheduling.
But superposition can fail for a wide variety of reasons. For example, when we decompose a problem into parts, and try to work on the parts separately, one task team might require — solely for scheduling purposes — that another task team take an approach that is less effective than it would have taken if it were free to act independently. We can easily generate numerous examples like this that show failures of superposition that confound our expectations.
In three weeks, we'll continue this exploration of the reasons why nonlinear work is so difficult to manage. Next issue in this series
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!
Footnotes
Your comments are welcome
Would you like to see your comments posted here? rbrenfHlRlTgqCIXkUHBTner@ChacrEuHRQPYVKkOucGfoCanyon.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:
Long-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.
Why Scope Expands: II
- The scope of an effort underway tends to expand over time. Why do scopes not contract just as often?
One cause might be cognitive biases that make us more receptive to expansion than contraction.
Ten Approaches to Managing Project Risks: I
- Risk management usually entails coping with losses if they do occur. Here's Part I of a concise summary
of the options for managing risk.
Wishful Interpretation: II
- Wishful "thinking," as we call it, can arise in different ways. One source is the pattern
of choices we make when we interpret what we see, what we hear, or any other information we receive.
Here's Part II of an inventory of ways our preferences and wishes affect how we interpret the world.
How to Get Out of Firefighting Mode: I
- When new problems pop up one after the other, we describe our response as "firefighting."
We move from fire to fire, putting out flames. How can we end the madness?
See also Project Management and Project Management for more related articles.
Forthcoming issues of Point Lookout
Coming April 30: On Planning in Plan-Hostile Environments: II
- When we finally execute plans, we encounter obstacles. So we find workarounds or adjust the plans. But there are times when nothing we try gets us back on track. When this happens for nearly every plan, we might be working in a plan-hostile environment. Available here and by RSS on April 30.
And on May 7: Subject Matter Bullying
- Most workplace bullying tactics have analogs in the schoolyard — isolation, physical attacks, name-calling, and rumor-mongering are common examples. Subject matter bullying might be an exception, because it requires expertise in a sophisticated knowledge domain. And that's where trouble begins. Available here and by RSS on May 7.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenfHlRlTgqCIXkUHBTner@ChacrEuHRQPYVKkOucGfoCanyon.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
rbrenfHlRlTgqCIXkUHBTner@ChacrEuHRQPYVKkOucGfoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
