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 welcomeWould you like to see your comments posted here? rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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.
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.
More articles on Project Management:
- The Weaver's Pathway
- When projects near completion, we sometimes have difficulty letting go. We want what we've made to be
perfect, sometimes beyond the real needs of customers. Comfort with imperfection can help us meet budget
and schedule targets.
- Nine Project Management Fallacies: IV
- Some of what we "know" about managing projects just isn't so. Understanding these last three
of the nine fallacies of project management helps reduce risk and enhances your ability to complete
- Long-Loop Conversations: Asking Questions
- In virtual or global teams, where remote collaboration is the rule, waiting for the answer to a simple
question can take a day or more. And when the response finally arrives, it's often just another question.
Here are some suggestions for framing questions that are clear enough to get answers quickly.
- 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.
- Some Risks of Short-Term Fixes
- When we encounter a problem at work, we must choose between short-term fixes (also known as workarounds)
and long-term solutions. Often we choose workarounds without appreciating the risks we're accepting
— until too late.
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.
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
- 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.
- 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.