If we think of a project and its people as a system, we can regard as external inputs the project charter, the project's requirements, and its resources. Changes in these inputs produce changes in the project's outputs. Consternation and frustration arise when changes in the outputs violate our expectations with respect to changes in the inputs.
As we've seen, nonlinear work doesn't always obey the superposition principle. That is, the result of two sets of inputs acting together is not always equal to the sum of the results of each input acting separately. This failure is one reason why our predictions of project results are so wrong so often.
Internal interactions within the project can provide another reason for our frustration. Here are three examples of internal interactions whose effects can dominate the effects of any change in project inputs.
- In the course of development, the project team might discover something that nobody knew or understood before work began. It might be an unanticipated obstacle (bad news), or a wonderful new opportunity (possible good news). Sometimes these discoveries lead to changes in requirements, even though no external agent sought a change in requirements. Whatever the discovery is, it can affect both project performance and project outcomes. And with alarming frequency, these effects can be far larger than the effect of any changes anyone — customer, manager, executive, regulator, marketer — might impose on the project. From this perspective, such changes come from nowhere.
- In complex The only real surprise in any
project would be the
absence of surprisessystems, emergence happens when many small identical elements of the system organize themselves into coherent behavior. For example, the organized movement of a school of fish is emergent behavior. Emergent phenomena are also observable in projects or portfolios of projects. When one task encounters difficulty, the consequences of that difficulty can propagate across the project, with the result that many other tasks find themselves in similar straits, resulting in a form of gridlock. This can happen at any time, in the absence of any external stimulus.
- Outputs can change even when inputs don't
- Even when none of the inputs have changed, mistakes, miscommunications, insights, and creativity can cause the outputs to develop along paths that differ from what anyone expected. This happens because the system contains more internal degrees of freedom than those that are specified by the inputs. We tend to call these unexpected changes "surprises," but the only real surprise in any project would be the absence of surprises.
Nonlinear work is frustrating not so much because it is nonlinear, but because we insist on believing that it is linear. We consider a project most successful when it behaves according to our expectations: no discoveries, no emergence, and outputs fully determined by inputs. It's a nice fantasy, but it's a fantasy nonetheless. First 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!
Your comments are welcomeWould you like to see your comments posted here? rbrenhxRGWtwkjGOzROedner@ChacsbDZTwYqZttNqDSLoCanyon.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:
- Flanking Maneuvers
- Historically, military logistics practice has provided a steady stream of innovations to many fields,
including project management. But project managers can learn even more if we investigate battlefield tactics.
- Teamwork Myths: Formation
- Much of the conventional wisdom about teams is in the form of over-generalized rules of thumb, or myths.
In this first part of our survey of teamwork myths, we examine two myths about forming teams.
- Personnel-Sensitive Risks: II
- Personnel-sensitive risks are risks that are difficult to discuss openly. Open discussion could infringe
on someone's privacy, or lead to hurt feelings, or to toxic politics or toxic conflict. If we can't
discuss them openly, how can we deal with them?
- Nonlinear Work: When Superposition Fails
- Much of the work we do is confounding, because we consistently underestimate the effort involved, the
resources required, and the time required to get it done. The failure of superposition can be one reason
why we get it wrong.
- Why Scope Expands: I
- Scope creep is depressingly familiar. Its anti-partner, spontaneous and stealthy scope contraction,
has no accepted name, and is rarely seen. Why?
See also Project Management for more related articles.
Forthcoming issues of Point Lookout
- Coming October 18: Missing the Obvious: II
- With hindsight, we sometimes recognize that we could have predicted the very thing that just now surprised us. Somehow, we missed the obvious. Why does this happen? Available here and by RSS on October 18.
- And on October 25: Workplace Memes
- Some patterns of workplace society reduce organizational effectiveness in ways that often escape our notice. Here are five examples. Available here and by RSS on October 25.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbreniGvWWgYGMaSJYhkgner@ChacJFLfyRDoSdwNUePIoCanyon.com or (617) 491-6289, 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, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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
- Ten Project Management Fallacies: The Power of Avoiding Hazards
- Most of what we know about managing projects is useful and effective, but some of what we know "just ain't so." Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully. Even more important, avoiding these traps can demonstrate the value and power of the project management profession in general, and your personal capabilities in particular. In this program we describe ten of these beliefs. There are almost certainly many more, but these ten are a good start. We'll explore the situations where these fallacies are most likely to expose projects to risk, and suggest techniques for avoiding them. Read more about this program. Here's a date for this program:
- 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.