
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? rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.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:
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 Retrospective Funding Problem
- If your organization regularly conducts project retrospectives, you're among the very fortunate. Many
organizations don't. But even among those that do, retrospectives are often underfunded, conducted by
amateurs, or too short. Often, key people "couldn't make it." We can do better than this.
What's stopping us?
More Obstacles to Finding the Reasons Why
- Retrospectives — also known as lessons learned exercises or after-action reviews — sometimes
miss important insights. Here are some additions to our growing catalog of obstacles to learning.
Risk Creep: I
- Risk creep is a term that describes the insidious and unrecognized increase in risk that occurs despite
our every effort to mitigate risk or avoid it altogether. What are the dominant sources of risk creep?
Checklists: Conventional or Auditable
- Checklists help us remember the steps of complicated procedures, and the order in which we must execute
them. The simplest form is the conventional checklist. But when we need a record of what we've done,
we need an auditable checklist.
See also Project Management for more related articles.
Forthcoming issues of Point Lookout
Coming July 16: Responding to Unwelcome Events
- Unwelcome events have two kinds of effects on decision-makers. One set of effects appears as we respond to events that have actually occurred. Another set manifests itself as we prepare for unwelcome events that haven't yet occurred, but which might occur. Making a wrong decision in either case can be costly. Available here and by RSS on July 16.
And on July 23: Microdelegation
- Microdelegation is a style of delegation in which the delegator unintentionally communicates the task to the subordinate in such detail and so repetitively that the subordinate is offended. As a result of this delegation style, many subordinates feel distrusted or suspected of fraud or goldbricking. Available here and by RSS on July 23.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.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
rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
