Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 10, Issue 14;   April 7, 2010: Project Improvisation Fundamentals

Project Improvisation Fundamentals

by

Project plans are useful — to a point. Every plan I've ever seen eventually has problems when it contacts reality. At that point, we replan or improvise. But improvisation is an art form. Here's Part I of a set of tips for mastering project improvisation.
In-flight portrait of the Apollo 13 Environmental Control System

In-flight portrait of the Apollo 13 Environmental Control System. Apollo 13 was the mission that suffered an explosion in an oxygen tank in the Service Module, which led mission controllers to decide to use the Lunar Module (LM) as a lifeboat to return the crew to Earth. But because the LM lacked sufficient carbon dioxide scrubbing capacity for three men for the duration of the mission, carbon dioxide concentrations began to climb to toxic levels. The system used lithium hydroxide canisters to absorb CO2, as did the system in the Command Module (CM), but the two canister types were incompatible.

A team in Houston then improvised a means of using the CM canisters in the LM Environmental Control System, using only materials available on board. After verifying the scheme in simulation, they read their instructions to the crew, who then reproduced the improvisation in the spacecraft. The scheme worked. It was just one small part of the entire improvisational effort that returned the crew to Earth alive and well. Photo courtesy U.S. National Aeronautics and Space Administration.

When executing a project, improvisation happens whenever we depart from the plan. Since most projects entail at least some small steps into unexplored territory, their plans are somehow incomplete or incorrect. When we discover the conflicts between a plan and reality, we halt and replan if we have time, and we improvise if we don't. We usually improvise.

Here is Part I of a set of guidelines and insights that help make improvisational approaches more effective. Part II explores project improvisation as a group process. Part III addresses connections between project improvisation and risk management. This Part I examines the fundamentals of project improvisation.

Educate everyone in advance
The defining characteristic of projects is that we've never done anything quite like them before. The inevitable surprises create a need to improvise. To view the need to improvise as either a defect in the plan or a defect in the planner is a critical error.
Educate all concerned, in advance, that improvisation is a normal and natural part of project work. Attempting such education at the moment of need is counterproductive, because it seems like defensive rationalization.
The plan ends when improvisation begins
When improvisation begins, its effect on the parts of the plan in which we still believe are unknown. We have to take time to understand the full impact of the improvisation.
While it's certainly possible that large portions of the plan can remain in place, the effects of improvisation can be subtle and unexpected. A thoughtful review of the entire plan is required.
Denying improvisation leads to uncontrolled improvisation
Some organizational cultures want to believe that improvisation has no place. Even when improvisation is happening, they deny its existence by calling it a replan. For instance, if six people revise in five days a plan that took thirty people six months to develop, can we seriously call it a replan? Such a revision is closer to improvisation than it is to replanning.
We usually do better at whatever we're doing if we're willing to admit we're doing it. If you're improvising, call it improvisation, and do whatever it takes to make it the best improvisation it can be.
Past performance can be misleading
Unless your We usually do better
at whatever we're doing
if we're willing to
admit we're doing it
culture is already aware of project improvisation as a necessary and useful skill, it's likely that previous improvisations have gone unrecognized and uncontrolled. Performance might have been disappointing.
Past performance can be misleading if it reflects uncontrolled, ad hoc improvisation. Distinguish such episodes from serious, coordinated, and thoughtful improvisations.

Effective improvisation requires individual skills and team skills. When a team starts improvising together, it relies more than ever on trust, communication, and inventiveness — all under pressure. Mastery of the improvisation regime requires education and practice.  Next in this series Go to top Top  Next issue: Project Improvisation as Group Process  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? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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:

An example of a Weaver's PathwayThe Weaver's Pathway
When projects near completion, we sometimes have difficulty letting go. We want what we've made to be perfect, sometimes beyond the real needs of customers. Comfort with imperfection can help us meet budget and schedule targets.
A Katrina rescue in New OrleansLong-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.
Ice on Challenger's launch pad hours before the launchDesign Errors and Groupthink
Design errors cause losses, lost opportunities, accidents, and injuries. Not all design errors are one-offs, because their causes can be fundamental. Here's a first installment of an exploration of some fundamental causes of design errors.
An apple and a skyscraper full of windowsHow We Waste Time: II
We're all pretty good at wasting time. We're also fairly certain we know when we're doing it. But we're much better at it than we know. Here's Part II of a little catalog of time wasters, emphasizing those that are outside — or mostly outside — our awareness.
Aedes aegypti mosquito in Dar es Salaam, TanzaniaDepth First or Breadth First?
When investigating candidate solutions to a problem, we tend to focus first on what we believe is the "best bet." But a more systematic approach can sometimes yield dramatic advantages by reducing the cost of the investigation and the time it requires.

See also Project Management and Problem Solving and Creativity for more related articles.

Forthcoming issues of Point Lookout

A well-festooned utility poleComing June 26: Additive bias…or Not: I
When we alter existing systems to enhance them, we tend to favor adding components even when subtracting might be better. This effect has been attributed to a cognitive bias known as additive bias. But other forces more important might be afoot. Available here and by RSS on June 26.
A close-up view of a chipseal road surfaceAnd on July 3: Additive bias…Not: II
Additive bias is a cognitive bias that many believe contributes to bloat of commercial products. When we change products to make them more capable, additive bias might not play a role, because economic considerations sometimes favor additive approaches. Available here and by RSS on July 3.

Coaching services

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

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-1000 words in your inbox in one hour. License any article from this Web site. More info

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at X, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
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.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.