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 in this series | Next 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.

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:

Declaring Condition Red

High-performance teams have customary ways of working together that suit them, their organizations, and their work. But when emergencies happen, operating in business-as-usual mode damages teams — and the relationships between their people — permanently. To avoid this, train for emergencies.

Nine Project Management Fallacies: II

Some of what we "know" about managing projects just isn't so. Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully.

TINOs: Teams in Name Only

Perhaps the most significant difference between face-to-face teams and virtual or distributed teams is their potential to develop from workgroups into true teams — an area in which virtual or distributed teams are at a decided disadvantage. Often, virtual and distributed teams are teams in name only.

Design Errors and Group Biases

Design errors can cause unwanted outcomes, but they can also lead to welcome surprises. The causes of many design errors are fundamental attributes of the way groups function. Here is Part II of our exploration.

Deep Trouble and Getting Deeper

Here's a catalog of actions people take when the projects they're leading are in deep trouble, and they're pretty sure there's no way out.

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

Forthcoming issues of Point Lookout

Coming October 23: Power Distance and Teams

One of the attributes of team cultures is something called power distance, which is a measure of the overall comfort people have with inequality in the distribution of power. Power distance can determine how well a team performs when executing high-risk projects. Available here and by RSS on October 23.

And on October 30: Power Distance and Risk

Managing or responding to project risks is much easier when team culture encourages people to report problems and question any plans they have reason to doubt. Here are five examples that show how such encouragement helps to manage risk. Available here and by RSS on October 30.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

The Race to the South Pole: Lessons in Leadership

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. But to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. We'll use the history of this event to explore lessons in leadership and its application to organizational efforts. A fascinating and refreshing look at leadership from the vantage point of history. Read more about this program.

Here's a date for this program:

• Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio 44017: November 7, Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute. 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 June 29, 2017, Monthly Webinar, sponsored by Technobility Webinar Series. PMI members can earn 1.0 Category 'A' PDU by viewing this program. View this program now.