Managing Risk Revision

To manage risks properly, we must allocate resources to implement a risk management plan. Some resources must be allocated in advance of anticipated risk events, and some must be held in reserve "just in case."

Many organizations have difficulty allocating these resources, especially when resources are thin and risks haven't yet materialized. The temptation to hope that all will go well can lead some to attempt projects with insufficient reserves for risks. And it can lead others to deny that specific risks can ever occur.

For example, despite decades of widely accepted predictions, the U.S. government failed to provide adequate resources to New Orleans for hurricane-induced flood risk mitigation and planning.

In the project environment, at best, project managers or risk officers identify risks and propose resources to mitigate them. Project sponsors and organizational management then review these proposals for sufficiency and reasonableness. They negotiate with the project staff as necessary, and then they allocate appropriate resources for risk mitigation and management.

In many organizations, things rarely work that way. Organizations commit themselves to risk plans that amount to little more than naïve hopes and wishes for the best. How does this happen?

In some cases, the available resources cannot cover all identified risks unless everything breaks favorably. When someone identifies a risk that's expensive to manage, risk revision, exclusion, or denial enables those involved to commit to the effort despite resource shortages. When this happens, risks that do materialize can threaten the project — or worse, threaten the enterprise.

What can organizations do to manage risk revision?

One approach involves adding to the project plan an Appendix of Revised or Excluded Risks — risks that someone proposed, but which were edited before inclusion in the risk plan, or excluded altogether. For each revised risk, the appendix includes the original proposed risk, a revision history with dates, the arguments in favor of and against such revisions, and the names of all involved in each revision decision. The Appendix of Revised or Excluded Risks serves several purposes.

Audit trail

If the organization someday decides how particular risk types are to be addressed, the Appendix becomes a useful tool to help project teams bring their projects into compliance.

Deterrence

When available resources
can't cover all identified
risks, we sometimes
revise the risks

To whatever extent organizational politics or intimidation play any role in risk revision or exclusion, the knowledge that revision decisions will be recorded in the Appendix might deter some intimidators or some who abuse political power to achieve their ends.

Support for organizational learning

The Appendix could provide useful data for project retrospectives, or even earlier, if trouble does appear during the project's execution.

If you think risk revision and denial aren't happening in your organization, you might want to add that observation to your Appendix of Revised or Excluded Risks.  Top    Next Issue

Projects never go quite as planned. We expect that, but we don't expect disaster. How can we get better at spotting disaster when there's still time to prevent it? How to Spot a Troubled Project Before the Trouble Starts is filled with tips for executives, senior managers, managers of project managers, and sponsors of projects in project-oriented organizations. It helps readers learn the subtle cues that indicate that a project is at risk for wreckage in time to do something about it. It's an ebook, but it's about 15% larger than "Who Moved My Cheese?" Just . 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.

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:

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.

Remote Facilitation in Synchronous Contexts: III

Facilitators of synchronous distributed meetings (meetings that occur in real time, via telephone or video) can make life much easier for everyone by taking steps before the meeting starts. Here's Part III of a little catalog of suggestions for remote facilitators.

Long-Loop Conversations: Clearing the Fog

In virtual or global teams, conversations can be long, painful affairs. Settling issues and clearing misunderstandings can take weeks instead of days, or days instead of hours. Here are some techniques that ease the way to mutual agreement and understanding.

Managing Non-Content Risks: I

When project teams and their sponsors manage risk, they usually focus on those risks most closely associated with the tasks — content risks. Meanwhile, other risks — non-content risks — get less attention. Among these are risks related to the processes and politics by which the organization gets things done.

Down in the Weeds: II

To be "down in the weeds," in one of its senses, is to be lost in discussion at a level of detail inappropriate to the current situation. Here's Part II of our exploration of methods for dealing with this frustrating pattern so common in group discussions.

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

Forthcoming issues of Point Lookout

Coming August 21: Perfectionism and Avoidance

Avoiding tasks we regard as unpleasant, boring, or intimidating is a pattern known as procrastination. Perfectionism is another pattern. The interplay between the two makes intervention a bit tricky. Available here and by RSS on August 21.

And on August 28: Playing at Work

Eight hours a day — usually more — of meetings, phone calls, reading and writing email and text messages, briefing others or being briefed, is enough to drive anyone around the bend. To re-energize, to clarify one's perspective, and to restore creative capacity, play is essential. Play at work, I mean. Available here and by RSS on August 28.

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.