We began our catalog of risk management strategies last time, exploring Denial, Shock, Acceptance, and Chaos. None of those four are particularly effective with respect to achieving our goals in the context of adversity. One more ineffective strategy remains to be explored before we examine some more effective approaches.
- Procrastination
- This strategy, usually executed unconsciously, involves repeated delay of planning to address acknowledged risks. We just can't seem to find time to sit down and plan for risks.
- Slogan: "Yes, we have to plan for that risk, but we're too busy right now. Maybe tomorrow."
- Advantage: Deferring planning enables the procrastinator to defer acknowledging the cost of managing risk, which can be helpful in persuading decision makers to undertake or continue the effort, because its full cost is unrecognized. Procrastinating also enables the procrastinator to claim that planning is "in progress" when actually it isn't.
- Danger: Procrastinating leads to a perception that the resources at hand are sufficient, when they might be wholly inadequate. It can also lead to delays so great that the organization can become unable to prepare for the risk prior to the actual risk event.
Let's look now at strategies that actually facilitate progress.
- Avoidance
- Avoidance is the choice to eliminate the possibility of loss by changing what you're doing. Other losses might happen, but not that one. For example, if we include an overview of the Marigold project in our presentation, we risk being asked about Issue 18, for which we have no answers yet. To avoid that risk, we decide not to provide a general overview of Marigold. Instead we'll discuss only Issue 17, which is almost resolved.
- Slogan: "If we use this other design instead, we can avoid that risk."
- Advantage: Finding Sometimes we can be so averse
to risk that we convince ourselves
that a risk-avoiding alternative
approach can achieve our goals,
when it actually cannota clever alternative to what we planned originally, and thereby avoiding a risk we would have borne under the original approach, can be both elegant and effective. - Danger: Sometimes we can be so averse to risk that we convince ourselves that a risk-avoiding alternative approach can achieve our goals, when it actually cannot.
- Limitation
- Limitation strategies reduce the probability of the risk event occurring, or reduce the size of the loss if it does occur, or both. Using limitation, we make the risk acceptable by reducing the expected value of the loss.
- Slogan: "We can reduce the probability of that risk (or the cost of that risk) if we do this."
- Advantage: The expected value of the loss associated with a risk event is the product PV, where P is the probability of the occurrence and V is the value lost. If we can reduce the expected value enough, we can proceed with confidence, even if the risk event occurs.
- Danger: Estimating probabilities is notoriously difficult. If we're wrong in our estimates, and the risk event occurs, we could be in trouble.
We'll continue next time with the last three of our risk management strategies. First in this series Next in this series 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
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:
- Some Causes of Scope Creep
- When we suddenly realize that our project's scope has expanded far beyond its initial boundaries —
when we have that how-did-we-ever-get-here feeling — we're experiencing the downside of scope
creep. Preventing scope creep starts with understanding how it happens.
- Team Thrills
- Occasionally we have the experience of belonging to a great team. Thrilling as it is, the experience
is rare. How can we make it happen more often?
- Communication Traps for Virtual Teams: II
- Communication can be problematic for any team, especially under pressure. But virtual teams face challenges
that are less common in face-to-face teams. Here's Part II of a little catalog with some recommendations.
- Durable Agreements
- People at work often make agreements in which they commit to cooperate — to share resources, to
assist each other, or not to harm each other. Some agreements work. Some don't. What makes agreements durable?
- Joint Leadership Teams: OODA
- Some teams, business units, or enterprises are led not by individuals, but by joint leadership teams
of two or more. They face special risks that arise from the organizations that host them, from the team
they lead, or from within the joint leadership team itself.
See also Project Management and Devious Political Tactics for more related articles.
Forthcoming issues of Point Lookout
- Coming April 24: Antipatterns for Time-Constrained Communication: 1
- Knowing how to recognize just a few patterns that can lead to miscommunication can be helpful in reducing the incidence of problems. Here is Part 1 of a collection of communication antipatterns that arise in technical communication under time pressure. Available here and by RSS on April 24.
- And on May 1: Antipatterns for Time-Constrained Communication: 2
- Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 2 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing those that depend on content. Available here and by RSS on May 1.
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