Project Improvisation as Group Process

When the time comes to depart from a carefully designed project plan, improvisation is often necessary. In Part I of this series, we explored some fundamentals of improvisation. In Part III, we'll explore the relationship between improvisation and risk management. We now turn to examining improvisation as a group process.

Avoid the rush to improvisation

Replanning takes time. And sometimes, replanning requires halting further work. If there isn't time to replan, and if work must continue, improvisation is a very tempting alternative, even though replanning is usually safer and cheaper than improvising.

The rush to improvisation is often driven by group panic. Ask yourself, are you certain there's no time for replanning? That work really must continue? Sometimes, the rush to improvise is internally driven — we don't want to stop to think. That's a very risky reason for improvising.

Remember that improvisation is a team effort

At the point when a decision maker concludes that it's time to improvise, the rest of the team is still following the plan. Since whatever follows is a team effort, improvisation will be more successful if the team improvises together.

When improvisation begins, all objectives, resource allocations, roles, and responsibilities are subject to change. A thorough group understanding of the new situation and the new approach is necessary for effective group improvisation.

Devise your improvisation compatibly

Operational structures of groups vary widely, from hierarchies to heterarchies or clouds. Hierarchical structures are top-down, command-and-control oriented, while cloud structures produce coordinated efforts in a more emergent fashion. An effective improvisational approach uses a style that is compatible with the operational structure already in place.

For instance, a team that uses a hierarchical operational structure is unlikely to produce a successful improvisational approach if asked to do so using a cloudlike structure. And a team accustomed to an autonomous approach to normal operations will have great difficulty when an improvised alternative is imposed on them by fiat. Choose an approach to developing the improvisation that is compatible with the team's culture. If you must deviate, enroll the team in the deviation first.

Use sophisticated communications

Project inception Remember that
improvisation
is a team effortusually includes extensive group communication to propagate the vision of the project, its importance to the organization, and the roles of all involved. When improvising begins, the resulting project configuration can conflict with much of whatever was communicated at project inception.

Those conflicts must be clearly communicated. We must communicate the new configuration, the new roles, and the new responsibilities, and in so doing, erase the no-longer-relevant elements of the old project plan. Because coordination is essential to effective improvisation, the need for communication within the team escalates dramatically when improvisation begins. That's one reason why improvisation is so much more difficult for virtual teams.

In two weeks, we'll examine how improvisation interacts with risk management.   First issue in this series    Next issue in this series   Top    Next Issue

Occasionally we have the experience of belonging to a great team. Thrilling as it is, the experience is rare. In part, it's rare because we usually strive only for adequacy, not for greatness. We do this because we don't fully appreciate the returns on greatness. Not only does it feel good to be part of great team — it pays off. Check out my Great Teams Workshop to lead your team onto the path toward greatness. More info

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:

Status Risk and Risk Status

One often-neglected project risk is the risk of inaccurately reported status. That shouldn't be surprising, because we often fail to report the status of the project's risks, as well. What can we do to better manage status risk and risk status?

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?

The Risks of Too Many Projects: I

Some organizations try to run too many development projects at once. Whether developing new offerings, or working to improve the organization itself, taking on too many projects can defocus the organization and depress performance.

Internal Audits Without Pain

If adhering to established procedures is part of your job, you probably experience occasional audits. You can manage the pain of the experience by regarding audit preparation as part of the job. Because it is. Here are some tips for navigating audits.

Rational Scope Management

In project management, rational, responsible scope management helps us focus on the task at hand. But rational scope management lets us adapt our work to changes in external factors, and changes in our understanding of the problem.

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

Forthcoming issues of Point Lookout

Coming July 3: Additive bias…or 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.

And on July 10: On Delegating Accountability: I

As the saying goes, "You can't delegate your own accountability." Despite wide knowledge of this aphorism, people try it from time to time, especially when overcome by the temptation of a high-risk decision. What can you delegate, and how can you do it? Available here and by RSS on July 10.

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:

• 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