Project Improvisation Fundamentals

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 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

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:

Who Would You Take With You to Mars?

What makes a great team? What traits do you value in teammates? Project teams can learn a lot from the latest thinking about designing teams for extended space exploration.

Team Thrills

Occasionally we have the experience of belonging to a great team. Thrilling as it is, the experience is rare. How can we make it happen more often?

Mitigating Risk Resistance Risk

Project managers are responsible for managing risks, but they're often stymied by insufficient resources. Here's a proposal for making risk management more effective at an organizational scale.

Ten Approaches to Managing Project Risks: II

Managing risk entails coping with unwanted events that might or might not happen, and which can be costly if they do happen. Here's Part II of our exploration of coping strategies for unwanted events.

On the Risk of Undetected Issues: I

In complex projects, things might have gone wrong long before we notice them. Noticing them as early as possible — and addressing them — is almost always advantageous. How can we reduce the incidence of undetected issues?

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

Forthcoming issues of Point Lookout

Coming June 20: Managing Dissent Risk

In group decision making, dissent risk is the risk that dissents about important decisions will be rejected without due consideration. As a result, group decision quality can suffer, and some groups will actually eject dissenters. How can we manage dissent risk? Available here and by RSS on June 20.

And on June 27: Interrupting Others in Meetings Safely: I

In meetings we sometimes feel the need to interrupt others to offer a view or information, or to suggest adjusting the process. But such interruptions carry risk of offense. How can we interrupt others safely? Available here and by RSS on June 27.

Coaching services

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

Public seminars

The Race to the South Pole: The Power of Agile Development

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. 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 a date for this program:

• Fifth Third Bank, 5717 Madison Road, Cincinnati, OH 45227: July 17, Monthly Meeting, Cincinnati chapter of the International Institute of Business Analysis. Register now.
   

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.

• A recording of a program presented 6:00 PM June 29 (Eastern Time), Monthly Webinar, Technobility Webinar Series. You can earn 1.0 Category 'A' PDU by viewing this program. View this program now.