Ten Approaches to Managing Project Risks: I

Discussing risk in general terms is always difficult, because many professions have their own ways of thinking about it. For now, let's regard risk as the chance of losing an asset. We measure the chance as a probability. We measure the asset in units of value.

If the probability of loss in a given time interval is P, and the value of the asset is V, the expected value of loss in that time interval is PV. In a large number of identical trials, our average loss per trial would be PV.

Sound decisions about enterprise resources do consider risk. For example, in estimating a project budget, we might consider the possibility that one of our suppliers might deliver a subsystem three months late. To manage this risk, we might reserve resources to deal with it if it occurs. If the cost of dealing with this event is V, and the probability of it occurring is P, then the reserves required are PV.

That's one example of a strategy for dealing with a risk. Fortunately, it isn't the only strategy available, and in many cases we can do much better. Here's Part I of a summary of the possible strategic options for dealing with risk, emphasizing ineffective (but very common) approaches.

Denial

Those in denial are those who reject the reality of the risk event.

Slogan: "That'll never happen. You're such a worrier!"

Advantage: Denial lets Those in denial are those
who reject the reality
of the risk eventus feel that preparation is unnecessary, because there's no risk. It can be a comforting illusion, especially for those reluctant to allocate resources to managing risk.

Danger: If the risk event occurs, we're unprepared. Worse, we can become disoriented when we find that our view of the world is fiction.

Shock

Shock happens when we're blindsided by the unexpected.

Slogan: "OMG, nobody could've anticipated that."

Advantage: If the unexpected doesn't happen, we can remain in a state of blissful ignorance.

Danger: If the unexpected happens too late for us to take remedial action, disaster is possible.

Acceptance

Acceptance is the strategy for those who don't want to prepare.

Slogan: "That might happen. We'll deal with it then."

Advantage: It requires no advance resource allocation. If the risk event doesn't occur, no resources are expended.

Danger: It can lead us to believe that we have less need for resources than we actually do. Acceptance is a prudent strategy only when PV is very small.

Chaos

This approach happens when we're so distracted by immediate events that we cannot plan for future risks.

Slogan: "Heavens! We've been meaning to plan for that. We clean forgot!"

Advantage: By focusing our resources elsewhere, we do accomplish some tasks. Without a risk plan, allocating resources to risk management becomes unnecessary.

Danger: If risk events arrive before we can allocate resources to risk planning, the risk response can be inadequate, and full-scale disaster is possible.

We'll continue next time with three more risk management strategies.  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

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:

The Weaver's Pathway

When projects near completion, we sometimes have difficulty letting go. We want what we've made to be perfect, sometimes beyond the real needs of customers. Comfort with imperfection can help us meet budget and schedule targets.

Emergency Problem Solving

In emergencies, group problem solving is unusually challenging, especially if lives, careers, or companies depend on finding a solution immediately. Here are some tips for members of teams that are solving problems in emergencies.

Risk Management Risk: I

Risk Management Risk is the risk that a particular risk management plan is deficient. It's often overlooked, and therefore often unmitigated. We can reduce this risk by applying some simple procedures.

The Risks of Too Many Projects: I

Some organizations try to run too many development projects at once. Whether developing new offerings, or working to improve the organization itself, taking on too many projects can defocus the organization and depress performance.

The Planning Dysfunction Cycle

Some organizations consistently choose not to allocate enough resources or time to planning for their most complex undertakings. Again and again, they decline to plan carefully enough despite the evidence of multiple disappointments and chaotic performance. Resource contention and cognitive biases conspire to sustain this cycle of dysfunction.

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