by Rick Brenner
In this part of our exploration of nonlinear work, we consider the effects of interactions between the internal elements of an effort, as distinguished from the effects of external changes. Many of the surprises we encounter in projects arise from internals.
Dunlin flock at Nelson Lagoon, Alaska. Flocks of birds, schools of fish, and swarms of insects, among many other biological groups, exhibit a behavior called swarming. Swarms seem to act in perfect if mysterious coordination. Swarms have no designated leader and no pre-defined global plan. Their behavior is emergent — a group improvisation. As humans, we like to believe that when we act in concert, we usually follow a leader or a plan. My own guess is that much of our group behavior is more like swarming than not. If it is like swarming, then the behavior of projects that seem ungovernable might be a bit less mysterious.
Recent research is beginning to explain how flocks coordinate their behavior. See Biro, et. al., "Hierarchical group dynamics in pigeon flocks," Nature 464, 890-893 (8 April 2010), or listen to the story by National Public Radio, "Backpacked Birds Reveal Who's The Boss." Photo courtesy U.S. Geological Survey.
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 welcome
Would you like to see your comments posted here? rbrensoieQsiCcEuIxrRoner@ChacMgntzjnmkQlmVyoyoCanyon.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.
More articles on Project Management:
- Remote Facilitation in Synchronous Contexts: Part II
- Facilitators of synchronous distributed meetings — meetings that occur in real time, via telephone or video — encounter problems that facilitators of face-to-face meetings do not. Here's Part II of a little catalog of those problems, and some suggestions for addressing them.
- Remote Facilitation in Synchronous Contexts: Part III
- Facilitators of synchronous distributed meetings (meetings that occur in real time, via telephone or video) can make life much easier for everyone by taking steps before the meeting starts. Here's Part III of a little catalog of suggestions for remote facilitators.
- Risk Management Risk: Part II
- Risk Management Risk is the risk that a particular risk management plan is deficient. Here are some guidelines for reducing risk management risk arising from risk interactions and change.
- Projects as Proxy Targets: Part I
- Some projects have detractors so determined to prevent project success that there's very little they won't do to create conditions for failure. Here's Part I of a catalog of tactics they use.
- Why Scope Expands: Part 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 July 29: Down in the Weeds: Part II
- To be "down in the weeds," in one of its senses, is to be lost in discussion at a level of detail inappropriate to the current situation. Here's Part II of our exploration of methods for dealing with this frustrating pattern so common in group discussions. Available here and by RSS on July 29.
- And on August 5: Wacky Words of Wisdom: Part IV
- Words of wisdom are pithy sayings that can be valuable so often that we believe them absolutely. Although these sayings are often valuable, they aren't universally valid. Here's Part IV of a growing collection. Available here and by RSS on August 5.
I offer email and telephone coaching at both corporate and individual rates.
Contact Rick for details at rbrenegBfkJHgKnzqsmFhner@ChaccqsOakGwERjBoOCfoCanyon.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:
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 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 an upcoming date for this program:
- Managing in Fluid Environments
- Most people now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know what’s coming next. In such environments, managing — teams, projects, groups, departments, or the enterprise — often entails moving from surprise to surprise while somehow staying almost on track. It's a nerve-wracking existence. This program provides numerous tools that help managers who work in fluid environments. Read more about this program. Here are some upcoming dates for this program:
- The Race to the South Pole: The Organizational Politics of Risk Management
- On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. But to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. We'll use the history of this event to explore lessons in risk management, its application to organizational efforts, and how workplace politics enters the mix. A fascinating and refreshing look at risk management from the vantage point of history and workplace politics. Read more about this program. Here's an upcoming date for this program:
- Team Development for Leaders
- Teams at work are often teams in name only — they're actually just groups. True teams are able to achieve much higher levels of performance than groups can. In this program, Rick Brenner shows team leads and team sponsors the techniques they need to form their groups into teams, and once they are teams, how to keep them there. Read more about this program. Here's an upcoming date for this program: