Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 8, Issue 22;   May 28, 2008: Managing Risk Revision

Managing Risk Revision

by

Prudent risk management begins by accepting the possibility that unpleasant events might actually happen. But when organizations try to achieve goals that are a bit out of reach, they're often tempted to stretch resources by revising or denying risks. Here's a tactic for 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."

Damage to the Interstate 10 Twin Bridge across Lake Pontchartrain

Damage to one of the low causeway sections of the Interstate 10 Twin Bridge across Lake Pontchartrain, following Hurricane Katrina in 2005. The storm surge brought by the hurricane raised the water level high enough to trap air beneath the concrete causeway's spans, causing them to float off the bridge pier caps. (See Chen, et al., Analysis of the Interstate 10 Twin Bridge's Collapse During Hurricane Katrina). The bridge was built in 1963, when the effects of hurricane storm surge were already understood, though not as well as they are now. Two other nearby bridges, a railroad bridge and the US 11 bridge, withstood the storm with only minor damage. The US 11 bridge opened February 18, 1928. It survived, in part, because its concrete girders are arched, and therefore trapped a smaller volume of air under its spans, reducing their effective buoyancy during the storm surge.

Back in 2001, the exposure of New Orleans to hurricane risk was so well known that it was the subject of a superb article in Scientific American (See M. Fischetti, Drowning New Orleans). Moreover, the storm's effects on the bridges were entirely predictable — explaining them entailed no new engineering discoveries. One can easily speculate about how the outcome of Katrina might have differed if resources for risk study and mitigation had been made available, but one also wonders what disasters elsewhere are yet preventable. Photo by Commander Mark Moran, Lt. Phil Eastman and Lt. Dave Demers, NOAA. Courtesy U.S. National Oceanic and Atmospheric Administration.

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. Go to top Top  Next issue: Virtual Presentations  Next Issue

How to Spot a Troubled Project Before the Trouble StartsProjects 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 USD 19.95. Order Now! .

Your comments are welcome

Would you like to see your comments posted here? rbrenmBwvPUKQUTjGfLuEner@ChacfYCRzmgLDJbFRtnGoCanyon.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.

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:

Icelandic currentsRestarting Projects
When a project gets off track, we sometimes cancel it. But since canceling projects takes a lot of courage, we look for ways to save them if we can. Often, things do turn out OK, and at other times they don't. There's a third choice, between pressing on with a project and canceling it. We can restart.
A white shark off the California coastNine Project Management Fallacies: Part 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 projects successfully.
The interior of an Apple store, location unknownPersonnel-Sensitive Risks: Part I
Some risks and the plans for managing them are personnel-sensitive in the sense that disclosure can harm the enterprise or its people. Since most risk management plans are available to a broad internal audience, personnel-sensitive risks cannot be managed in the customary way. Why not?
Erecting a floating bridge in Korea (1952)When Change Is Hard: Part II
When organizational change is difficult, we sometimes blame poor leadership or "resistance." But even when we believe we have good leadership and the most cooperative populations, we can still encounter trouble. Why is change so hard so often?
Magic Lantern Slide of a dog jumping through a hoopJust-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.

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

Forthcoming issues of Point Lookout

Balancing talk time and the value of the contributionComing March 29: Virtual Blowhards
Controlling meeting blowhards is difficult enough in face-to-face meetings, but virtual meetings present next-level problems, because techniques that work face-to-face are unavailable. Here are eight tactics for controlling virtual blowhards. Available here and by RSS on March 29.
kudzu enveloping a Mississippi landscapeAnd on April 5: Listening to Ramblers
Ramblers are people who can't get to the point. They ramble, they get lost in detail, and listeners can't follow their logic, if there is any. How can you deal with ramblers while maintaining civility and decorum? Available here and by RSS on April 5.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenbxTfPycUkwwCcLmhner@ChacEsvFlQthlflLmtXwoCanyon.com or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

Reprinting this article

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

Changing How We Change: The Essence of Agility
MasteChanging How We Change: The Essence of Agilityry of the ability to adapt to unpredictable and changing circumstances is one way of understanding the success of Agile methodologies for product development. Applying the principles of Change Mastery, we can provide the analogous benefits in a larger arena. By exploring strategies and tactics for enhancing both the resilience and adaptability of projects and portfolios, we show why agile methodologies are so powerful, and how to extend them beyond product development to efforts of all kinds. Read more about this program. Here are some upcoming dates for this program:

Conflict Resolution Skills for Leaders
ConflConflict Resolution Skills for Leadersict is inherent in collaborative work. When conflict is constructive, it produces better outcomes. When it's destructive, it can be an insurmountable obstacle to success. In this program, we explore the connections between the outcomes of collaboration and conflict in both of its forms. And we emphasize the skills needed most by leaders. The leader's task is to manage conflict so as to ensure that the group achieves its objective with its capacity to collaborate intact, or even enhanced. Rick Brenner shows team leaders and team sponsors the techniques they need to manage team conflict for relationship safety and better outcomes. Read more about this program. Here's an upcoming date for this program:

Influencing Outcomes Without Authority
Your Influencing Outcomes Without Authorityability to influence others — whether upward, downward, laterally, or within a team — always depends on both the quality of your relationships with the people you influence, and on your perception and their perception of your personal power. In this program, Rick Brenner shows you the techniques for making things happen not by using formal organizational power, but by using informal, personal power. Read more about this program. Here's an upcoming date for this program:

Strategies for Leading Teams in Hard Times
When Strategies for Leading Teams in Hard Timesa project team is on task, the contributions of leaders are important, and little noticed. Sometimes the team encounters unexpected difficulty, or requirements change, or budgets are reduced, or any of a number of other things might happen. In these cases, the leader must make or facilitate decisions about how to respond or how to revise the plan. We get through it somehow. Hard times are something else altogether. Despondency, disillusionment, resource shortages, unexpected and severe failure of the plan, and toxic conflict can erode morale. How can leaders deal with such situations? Read more about this program. Here's an upcoming date for this program:

Strategies for Technical Debt: A Workshop for Enterprise Leaders
TechnTechnical Debt Management for Enterprise Leadersical debt is more than mere IT jargon. It's a metaphor that refers to the accumulation of technical artifacts that really ought to be retired, replaced, rewritten, re-implemented, or, if absent, created. We can find technical debt in almost any system, including those that seem to be working well. So what's the problem? The problem is the "interest charges." Systems carrying technical debt are more difficult to maintain, more difficult to extend or enhance, and more difficult to use, than they would be if we "retired" the debt. This engaging and eye-opening program points the way to a path that leads your organization out of technical debt, to make it more adaptable, more transformable, and more agile. Read more about this program. Here's an upcoming date for this program:

Creating High Performance Virtual Teams
Many Creating High Performance Virtual Teamspeople experience virtual teams as awkward, slow, and sometimes frustrating. Even when most team members hail from the same nation or culture, and even when they all speak the same language, geographic dispersion or the presence of employees from multiple enterprises is often enough to exclude all possibility of high performance. The problem is that we lead, manage, and support virtual teams in ways that are too much like the way we lead, manage, and support co-located teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance. Read more about this program. Here's an upcoming date for this program:

The Race to the South Pole: Ten Lessons for Project Managers
On 14The Race to the Pole: Ten Lessons for Project Managers 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. Lessons abound. Read more about this program. Here's an upcoming date for this program:

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
21st Century Business TravelAre your business trips long chains of stressful misadventures? Have you ever wondered if there's a better way to get from here to there relaxed and refreshed? First class travel is one alternative, but you can do almost as well (without the high costs) if you know the tricks of the masters of 21st-century e-enabled business travel…
Join the Organizational Politics Group at LinkedIn.comJoin the Office Politics, Workplace Politics and Organizational Politics discussion group at LinkedIn.com, the premier professional networking Web site.
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.