When is a Risk not a Risk II
Dr David Hillson looks a bit deeper at risk management, and explores the challenges and confusions between the different types of risk
Another common challenge in risk identification is to avoid confusion between causes of risk, genuine risks, and the effects of risks. The PMI PMBoK Guide (Third Edition Exposure Draft) says that "A risk may have one or more causes and, if it occurs, one or more impacts". In the most simple case, one cause leads to a single risk which in turn could have just one effect, though of course reality is considerably more complex. How do these three differ?
- Causes are definite events or sets of circumstances which exist in the project or its environment, and which give rise to uncertainty. Examples include the requirement to implement the project in a developing country, the need to use an unproven new technology, the lack of skilled personnel, or the fact that the organisation has never done a similar project before. Causes themselves are not uncertain since they are facts or requirements, so they should not be managed through the risk management process.
- Risks are uncertainties which, if they occur, would affect the project objectives either negatively (threats) or positively (opportunities). Examples include the possibility that planned productivity targets might not be met, interest or exchange rates might fluctuate, the chance that client expectations may be misunderstood, or whether a contractor might deliver earlier than planned. These uncertainties should be managed proactively through the risk management process.
- Effects are unplanned variations from project objectives, either positive or negative, which would arise as a result of risks occurring. Examples include being early for a milestone, exceeding the authorised budget, or failing to meet contractually agreed performance targets. Effects are contingent events, unplanned potential future variations which will not occur unless risks happen. As effects do not yet exist, and indeed they may never exist, they cannot be managed through the risk management process.
Examples include the following :
- As a result of using novel hardware (a definite requirement), unexpected system integration errors may occur (an uncertain risk), which would lead to overspend on the project (an effect on the budget objective).
- Because our organisation has never done a project like this before (fact = cause), we might misunderstand the customer's requirement (uncertainty = risk), and our solution would not meet the performance criteria (contingent possibility = effect on objective).
- We have to outsource production (cause); we may be able to learn new practices from our selected partner (risk), leading to increased productivity and profitability (effect).
About the author:Dr David Hillson PMP FAPM FIRM MCMI is an international risk management consultant, and Director of Risk Doctor & Partners (www.risk-doctor.com). He is a popular conference speaker and award-winning author on risk. He is recognised internationally as a leading thinker and practitioner in the risk field, and has made several innovative contributions to improving risk management. His recent emphasis has been the inclusion of proactive opportunity management within the risk process, which is the topic of his latest book.
David is an active member of the global Project Management Institute (PMI) and was a founder member of its Risk Management Specific Interest Group. He received the 2002 PMI Distinguished Contribution Award for his work in developing risk management over many years. He is a Fellow of the UK Association for Project Management (APM) and a Fellow of the UK Institute of Risk Management (IRM), as well as being a member of the Chartered Management Institute. David can be contacted at david@risk-doctor.com
StumbleUpon
Comments
dhillson said:
incorporating risk? <p>Tom, <br/>Interesting comment, thanks. Sorry for the long delay in posting this reply, but I had problems logging into NMK as a registered user. <br/> <br/>Anyway, how to ensure ?optimum level of risk?? You?re absolutely right that too much risk management can stifle creativity and innovation etc ? BUT only if risk is perceived as synonymous with threat. When you realise that there are upside positive risks, aka opportunities, which the risk process can and should manage, then the position becomes more clear. <br/> <br/>The right level of risk-taking includes minimising bad risks (threats) and maximising good risks (opportunities) in order to optimise the risk exposure and achieve the defined objectives. <br/> <br/>I think this is covered in my NMK article ?When is a risk not a risk? (Part I)?, where I say this : <br/> <br/>?One other question arises from the concept of risk as "uncertainty that could affect objectives" - what sort of effect might occur? In addition to those uncertainties which if they occur would make it more difficult to achieve objectives (also known as threats), there are also uncertain events which if they occur would help us achieve our objectives (i.e. opportunities). When identifying risks, we need to look for uncertainties with an upside as well as those with a downside.? <br/> <br/>Hope this helps, and thanks for starting this debate. <br/>David Hillson <br/></p>
Tom said:
how can we increase risk? <p>Very clear introduction to the subject of risk. <br/> <br/>How does this fit in with ideas about the optimum level of risk? It seems to me that minimizing risks has its own dangers, such as stifling free thinking, innovation and entrepreneurialism. How should management incorporate risk into their processes, to maximise these benefits?<br/></p>
You must be logged in to comment.