
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 itculture 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 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!
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:
Restarting Projects
- When a project gets off track, we sometimes cancel it. But since canceling projects takes a lot of courage,
we look for ways to save them if we can. Often, things do turn out OK, and at other times they don't.
There's a third choice, between pressing on with a project and canceling it. We can restart.
Finger Puzzles and "Common Sense"
- Working on complex projects, we often face a choice between "just do it" and "wait, let's
think this through first." Choosing to just do it can seem to be the shortest path to the goal,
but it rarely is. It's an example of a Finger Puzzle.
Nine Positive Indicators of Negative Progress
- Project status reports rarely acknowledge negative progress until after it becomes undeniable. But projects
do sometimes move backwards, outside of our awareness. What are the warning signs that negative progress
might be underway?
On the Risk of Undetected Issues: II
- When things go wrong and remain undetected, trouble looms. We continue our efforts, increasing investment
on a path that possibly leads nowhere. Worse, time — that irreplaceable asset — passes.
How can we improve our ability to detect undetected issues?
On Managing Life Event Risk
- Life events are those significant personal occurrences that lie outside the context of work. Some life
events cause enough stress and demand enough attention that they affect our performance at work. When
they do, they can affect our employers' plans.
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
