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

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:

An Agenda for Agendas

Most of us believe that the foundation of a well-run meeting is a well-formed agenda. What makes a "well-formed" agenda? How can we write and manage agendas to make meetings successful?

The Politics of the Critical Path: 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.

Scope Creep and Confirmation Bias

As we've seen, some cognitive biases can contribute to the incidence of scope creep in projects and other efforts. Confirmation bias, which causes us to prefer evidence that bolsters our preconceptions, is one of these.

Wishful Thinking and Perception: II

Continuing our exploration of causes of wishful thinking and what we can do about it, here's Part II of a little catalog of ways our preferences and wishes affect our perceptions.

Joint Leadership Teams: Risks

Some teams, business units, or enterprises are led not by individuals, but by joint leadership teams of two or more. They face special risks that arise from the organizations that host them, from the teams they lead, or from within the joint leadership team itself.

See also Project Management and Project Management for more related articles.

Forthcoming issues of Point Lookout

Coming January 22: Storming: Obstacle or Pathway?

The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.

And on January 29: A Framework for Safe Storming

The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.

Coaching services

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