Sometimes projects get stuck. They stratify; they stall. We cancel them if we can, but often we press on, hoping for the best. Since we can't always tell which project elements led to the problems, we often try to preserve the very elements that caused the stalls, and eventually the project ends in disappointment or even outright failure. Usually, we get something like what we wanted, but the experience is unsatisfying.
A third choice, between pressing on with a project and canceling it, is restarting. Restarting means halting, assessing what we have, reorganizing, reassigning, repartitioning responsibility, replanning, re-envisioning. It's energizing, and it can be painful.
When you restart, put everything on the table. Introduce new leadership, new team structures, new plans - even a new vision. Restarting a project creates turbulence. And that's exactly why it works. To learn why, let's take a trip to the North Atlantic.
Iceland lies in the path of the Gulf Stream. As branches of the Gulf Stream sweep past, they spin off huge eddies that warm the island. Meanwhile, the Greenland Current, as cold as the Gulf Stream is warm, creates its own eddies as it sweeps down from the North. Where the two systems collide, they create broad vortices that bring nutrients up from the ocean bottom. These nutrients support a rich marine ecology that has made the people of Iceland wealthy.
In Nature, living systems thrive on turbulence. Turbulence disrupts stratification, increasing the exchange of material between ecological subsystems. Restarting a project
creates turbulence.
And that's exactly
why it works.By providing resources to every element of an ecological system, turbulence keeps that system vital.
Restarting a project creates turbulence. Restarting is the project's Greenland Current meeting the project's Gulf Stream. A project is a candidate for a restart if:
- It has a history of repeated schedule slips or budget overruns.
- Its failure or cancellation would be a threat to the enterprise.
- There is no clear consensus about a path to success.
Three keys to successful restarts:
- Train before you try
- Learning about restarting while you're restarting is like having a driving lesson on the freeway at 5 PM on a Friday afternoon. Restart projects with care - it can be dangerous.
- Avoid blaming
- Some people who are displaced might think of themselves as being held responsible for the problem. Typically, they aren't responsible. Unblocking sometimes requires new faces to achieve turbulence. Communicate clearly that a systemic problem, not a personal one, caused the blockage.
- Get help
- If your organization has never restarted projects before, get some help for the first one or two. There's a lot to learn.
Just as the Gulf Stream and the Greenland Current stir up nutrients to support the Icelandic marine ecology, restarting a project can support the ecology of ideas that re-invigorates the project and puts it back on the path to success. 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
Would you like to see your comments posted here? rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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.
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:
- Project Improvisation as Group Process
- When project plans contact reality, things tend to get, um, a bit confused. We can sometimes see the
trouble coming in time to replan thoughtfully — if we're nearly clairvoyant. Usually, we have
to improvise. How a group improvises tells us much about the group.
- Unnecessary Boring Work: II
- Workplace boredom can result from poor choices by the person who's bored. More often boredom comes from
the design of the job itself. Here's Part II of our little catalog of causes of workplace boredom.
- Just-In-Time Hoop-Jumping
- Securing approvals for projects, proposals, or other efforts is often called "jumping through hoops."
Hoop-jumping can be time-consuming and frustrating. Here are some suggestions for jumping through hoops
efficiently.
- Seven More Planning Pitfalls: III
- Planning teams, like all teams, are vulnerable to several patterns of interaction that can lead to counter-productive
results. Two of these relevant to planners are a cognitive bias called the IKEA Effect, and a systemic
bias against realistic estimates of cost and schedule.
- Lessons Not Learned: I
- The planning fallacy is a cognitive bias that causes us to underestimate the cost and effort involved
in projects large and small. Mitigating its effects requires understanding how we go wrong when we plan
projects by referencing our own past experience.
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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed