Risk resistance is the objection to all or part of a risk plan's content. Typically, objectors are project sponsors or senior managers. Typical objections are that the risks in question are fictitious, or that the mitigation plan is too expensive. Since the organizational power of the objectors generally exceeds that of the risk plan's authors, authors often simply eliminate or downgrade the items with which objectors disagree.
Although risks rarely materialize as projected, something similar often does. A classic example is the flooding of New Orleans in 2005. Concerns about such catastrophes trace back at least to the Flood Control Act of 1965, but the resources provided over the years for mitigating flood risk were most inadequate. The result of these mitigation downgrades is the disaster following Hurricane Katrina.
Downgrading risk plans — or their funding — doesn't downgrade the risk or make risk mitigation any cheaper. Instead, it opens gaps between risk plans and reality. That's how risk resistance creates risk. Here are four methods for addressing risk resistance risk.
- Make risk plan revision traceable
- Document risk plan revision in a Risk Plan Revision History — a section of the project plan that documents the downgrading of risk probability estimates and risk mitigation budgets.
- Traceability facilitates corrective action when the organization is found unprepared for risks that do materialize. Record in the History the original risk plan elements, the reasoning supporting the modifications, and the dates of and parties to the downgrade decisions.
- Retrospectively review gaps between risk plans and reality
- After an unanticipated risk materializes, and its full impact on budget and schedule are known, review how it was addressed in the risk plan.
- Was the risk anticipated in the final plan? If not, was it addressed in any earlier versions of the risk plan? Were earlier versions of the plan downgraded? Use the Risk Plan Revision History to answer these questions.
- Measure risk response budgets and actuals
- Keep accurate historical data measuring both the budget and actuals for risk response.
- Managing risk more Document risk plan revision in
a Risk Plan Revision Historyeffectively requires narrowing the gap between risk plan budgets and risk response expenditures. Rarely do we have the necessary data available when we try to assess our risk performance. Start collecting it now. - Measure risk performance globally
- Mitigating risk by taking actions that harm other projects can be expensive to the organization.
- Some projects use political power to export the costs of their risk responses onto other projects. For example, reassigning people with rare skills — or holding onto them longer than planned — might aid one project, but it can harm others. To assign responsibility for these costs correctly, measure risk response costs across the entire organization, as opposed to per-project.
Objectors to risk plans, who often recognize the implications of the measures suggested here, might raise objections to implementing them. Begin advocacy or implementation only when you're prepared to meet those objections. Top Next Issue
Is every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. More info
Your comments are welcome
Would you like to see your comments posted here? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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:
- Films Not About Project Teams: I
- Here's part one of a list of films and videos about project teams that weren't necessarily meant to
be about project teams. Most are available to borrow from the public library, and all are great fun.
- 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.
- Nonlinear Work: When Superposition Fails
- Much of the work we do is confounding, because we consistently underestimate the effort involved, the
resources required, and the time required to get it done. The failure of superposition can be one reason
why we get it wrong.
- Seven Planning Pitfalls: II
- Plans are well known for working out differently from what we intended. Sometimes, the unintended outcome
is due to external factors over which the planning team has little control. Two examples are priming
effects and widely held but inapplicable beliefs.
- Rational Scope Management
- In project management, rational, responsible scope management helps us focus on the task at hand. But
rational scope management lets us adapt our work to changes in external factors, and changes in our
understanding of the problem.
See also Project Management and Workplace Politics for more related articles.
Forthcoming issues of Point Lookout
- Coming May 15: Should I Write or Should I Call?
- After we recognize the need to contact a colleague or colleagues to work out a way to move forward, we next must decide how to make contact. Phone? Videoconference? Text message? There are some simple criteria that can help with such decisions. Available here and by RSS on May 15.
- And on May 22: Rescheduling Collaborative Work
- Rescheduling is what we do when the schedule we have now is so desperately unachievable that we must let go of it because when we look at it we can no longer decide whether to laugh or cry. The fear is that the new schedule might come to the same end. Available here and by RSS on May 22.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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
rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed