Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 12, Issue 22;   May 30, 2012: Nonlinear Work: Internal Interactions

Nonlinear Work: Internal Interactions

by

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

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.

Discovery
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.
Emergence
In complex The only real surprise in any
project would be the
absence of surprises
systems, 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  Go to top Top  Next issue: Wacky Words of Wisdom: Part II  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre 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? rbrenHGGhWtYlbxtJkfhWner@ChacyWuzQpTEhDEtYCldoCanyon.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.

Related articles

More articles on Project Management:

Chocolate chip cookiesNine Project Management Fallacies: Part 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.
Rough-toothed dolphinThe Injured Teammate: Part I
You're a team lead, and one of the team members is very ill or has been severely injured. How do you handle it? How do you break the news? What does the team need? What do you need?
The Dalles of the St. Croix RiverThe Politics of the Critical Path: Part II
The Critical Path of a project is the sequence of dependent tasks that determine the earliest completion date of the effort. We don't usually consider tasks that are already complete, but they, too, can experience the unique politics of the critical path.
Firefighter lighting grass using a drip torchBeyond Our Control
When bad things happen, despite our plans and our best efforts, we sometimes feel responsible. We failed. We could have done more. But is that really true? Aren't some things beyond our control?
Panama Canal constructionAvoid Having to Reframe Failure
Yet again, we missed our goal — we were late, we were over budget, or we lost to the competition. But how can we get something good out of it?

See also Project Management for more related articles.

Forthcoming issues of Point Lookout

An outstanding example of the Utility Pole anti-patternComing June 1: Workplace Anti-Patterns
We find patterns of counter-effective behavior — anti-patterns — in every part of life, including the workplace. Why? What are their features? Available here and by RSS on June 1.
An outstanding example of the Utility Pole anti-patternAnd on June 8: The Utility Pole Anti-Pattern: Part I
Organizational processes can get so complicated that nobody actually knows how they work. If getting something done takes too long, the organization can't lead its markets, or even catch up to the leaders. Why does this happen? Available here and by RSS on June 8.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmOLDMqkiSuBfNBiSner@ChacHULVFovtxvgtFgRUoCanyon.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

Public seminars

The Race to the South Pole: The Power of Agile Development
On 14The Race to the Pole: An Application of Agile Development 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. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's an upcoming date for this program:

Managing in Fluid Environments
Most Managing in Fluid Environmentspeople now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know whats 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's an upcoming date for this program:

Sudoku Solutions, INK: A Simulation of a Project-Oriented Organization
In thCross-Functional Teams: How Organizations Actually Workis workshop, we simulate a company that solves Sudoku puzzles for its customers. Each puzzle is a project, solved by a project team led by a project manager. Team members hail from different parts of the organization, such as QA or the Department of Threes. Puzzles have different values, and the company must strive to meet revenue goals. The metaphor is uncanny. Lessons abound. Read more about this program. Here's an upcoming date for this program:

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ or share a post Subscribe to RSS feeds Subscribe to RSS feeds
Please donate!The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
How to Spot a Troubled Project Before the Trouble StartsLearn how to spot troubled projects before they get out of control.
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.