Project Management

Analysing Assumptions & Constraints

From the Risk Insights from The Risk Doctor Blog
by
David Hillson, The Risk Doctor, shares key tips on understanding and managing risk, blending thought-leadership with expert practical application. Managing risk is easy - find out how!

About this Blog

RSS

Recent Posts

HAPPY NEW YEAR: Two-faced risk management

Zero chance of a zero-risk project

Innovative risk management

Why some risks turn into surprises

Are project opportunities the same as scope screep?

Categories

risk analysis, risk identification, risk management, risk process, risk psychology, risk responses

Date

linkedin twitter facebook Request to reuse this  

Categories: risk identification


No-one knows the future with perfect certainty, which of course is why we need risk management. But sometimes we try to guess what might happen, and use that information as a basis for planning or decision-making. The proper name for such a guess is an “assumption”, and these are an important source of risk, for projects, businesses and life in general.

An assumption is a way of dealing with an uncertain future when there are a number of possible options. In its simplest form an assumption is a decision to proceed on the basis that one option will turn out to be correct and the others will not happen. For example, we might assume that our suppliers will deliver on time, or that our client will sign-off all approvals within two weeks, or that all key members of our project team will remain for the duration of the project. But what happens if we assumed the wrong thing? In most cases a false assumption would lead to a problem for the project, since we usually tend to assume that things will go the way we want.

Of course not all assumptions matter equally. There are some assumptions which might prove false without having a significant effect on the overall project, but there are others where a different outcome could be serious. Fortunately there is a simple process for testing how risky assumptions might be, and for including them in the risk process if necessary. A simple IF-THEN statement can be written for each assumption, in the form : 
“IF this assumption proved to be false, THEN the effect on the project would be …”

The IF side tests how likely the assumption is to be unsafe, and the THEN side tests whether it matters. Another way of describing this is to see the IF statement as reflecting probability, whereas the THEN phrase is about impact. And probability and impact are the two dimensions of risk. This simple approach can be used to turn project assumptions into risks. Where an assumption is assessed as likely to be false and/or it could have a significant effect on one or more project objectives, that assumption should be considered as a candidate risk.

This type of Assumptions Analysis is a powerful way of exposing project-specific risks, since it addresses the particular assumptions made about a given project.

There are however two dangers with this technique :
1.    The first weakness is that this technique can only consider explicit assumptions, which have been consciously made and openly communicated. There are however many implicit or hidden assumptions which we all make every day, some of which are very risky. 
2.    Secondly this approach tends only to identify downside risks, threats that a particular assumption may prove false and result in a problem for the project. Assumptions Analysis is not good at identifying opportunities because most of our assumptions are optimistic.

The first shortcoming can be overcome by a facilitated approach to identifying and recording assumptions, using someone independent and external to the project to challenge established thinking. To be fully effective, Assumptions Analysis needs full disclosure.

For opportunity identification, the technique can be extended to address and challenge constraints. These are restrictions on what the project can or cannot do, how it must or must not proceed. But some of these constraints may not be as fixed as they first appear – indeed some of them might be assumed constraints. In fact it might be possible for a constraint to be relaxed or perhaps even removed completely. In the same way that assumptions can be tested to expose threats, a similar IF-THEN test can be applied to constraints to identify possible opportunities: 
“IF this constraint could be relaxed or removed, THEN the effect on the project would be …”

Instead of making assumptions about the future, or accepting that stated constraints are unchangeable, being prepared to challenge assumptions and constraints can expose significant threats and opportunities which can then be addressed through the risk process.


Posted on: August 18, 2015 10:54 AM | Permalink

Comments (14)

Please login or join to subscribe to this item
avatar
Parag Tipnis Director of PM/PMO| UBS India
Also not all assumptions are binary. If an assumption turns out to be false, there might be several other possible things that could happen, some of them positive for the project and some negative. The IF-THEN analysis needs to be then drawn into some sort of tree diagram to explore and understand all possible outcomes/alternatives

avatar
John Reiling Seeking new opportunities | AcroVision Business Systems, Inc. Mendham, Nj, United States
Yes, Parag, agreed, but I think there could be a way to just make everything binary for simplicity. Otherwise, I think this is a nice way to explain risk and protocol for analyzing them.

avatar
Abdullah Al Mamoon Deputy Managing Director & COO| United Commercial Bank PLC Dhaka, Bangladesh
It's a very good read. Short but informative with helpful tips. Thanks David for sharing this.

avatar
David Hillson The Risk Doctor| The Risk Doctor Partnership Petersfield, Hampshire, United Kingdom
@Parag. John is right that the simplicity of this approach is one of its attractions. Of course other things *might* happen if an assumption turns out to be false - but that is precisely why it is a risk! The false assumption introduces uncertainty into the project.

You could of course also develop a tree structure as you suggest, but then it is not an Assumptions Analysis, it is a Fault Tree Analysis!

avatar
David Hillson The Risk Doctor| The Risk Doctor Partnership Petersfield, Hampshire, United Kingdom
Thanks Abdullah, glad you like this approach. I hope you find it useful in identifying your risks!

avatar
Michael Adams Solutions Architect| LANL Los Alamos, Nm, United States
I read an interesting article from the Harvard Business Review about a year ago:
Performing a Project PRE Mortem
The ideas was to get the team together and "pretend" that we've hit the end of the line on this project. It failed horribly. We're doing a "postmortem" to figure out why it failed. Then everyone begins to explore from a psychologically different perspective, why the project failed. This allows them to identify assumptions that may be invisible to them from the opposite perspective, of what might go wrong with this?

avatar
David Hillson The Risk Doctor| The Risk Doctor Partnership Petersfield, Hampshire, United Kingdom
Thanks Michael. Pre-mortems are a great idea, and Gary Klein (who wrote that HBR article) wrote a whole book on the topic in 2002 (Intuition at Work). You can also use the more simple approach of producing a whole-project fault-tree, starting with failure and working backwards.

But don't forget that risk includes upside opportunities! So we also need to perform a positive pre-mortem (perhaps we call it a "pre-resurrection"?!), starting with the end-point that the project was a fabulous success. Then we work backwards to imagine how that could have come about. Taking that perspective, we can plot a path to success that might help us to avoid threats and capture opportunities.

So yes, pre-mortems are great, but we need to do two of them - one negative and one positive!

avatar
Michael Adams Solutions Architect| LANL Los Alamos, Nm, United States
David, that is a great idea! I really liked Klein's pre-mortem idea, but I particularly appreciate your suggestion of also analyzing the project from the perspective of how did we pull this off with such success? Pre-resurrection made me laugh! May I take that name? :-) I may explore this with some colleagues and write something up on it.

avatar
David Hillson The Risk Doctor| The Risk Doctor Partnership Petersfield, Hampshire, United Kingdom
That's fine Michael. If you write anything I'd be interested to see it.

avatar
Michael Adams Solutions Architect| LANL Los Alamos, Nm, United States
Hi David, here is an older article of mine, but it is one I'm particularly proud of :-)
I thought you might like it:
Humble Pie, Nutritious and Delicious
The Followup article is here:
The Humble Process

avatar
David Hillson The Risk Doctor| The Risk Doctor Partnership Petersfield, Hampshire, United Kingdom
Thanks Michael. Nice articles. I especially like the fact that you're "particularly proud" of these articles on ... humility! ;-)

avatar
Michael Adams Solutions Architect| LANL Los Alamos, Nm, United States
LOL...good point David! :-)

avatar
Vincent Guerard Coach - Trainer - Speaker - Advisor| Freelance Mont-Royal, Quebec, Canada
Thanks David,
I like the reminder of implicit or hidden assumptions, often overlooked.

avatar
David Hillson The Risk Doctor| The Risk Doctor Partnership Petersfield, Hampshire, United Kingdom
Thank you Vincent. These are the assumptions that usually come and bite us later! We need good techniques to expose these so that they can be tested. Have you heard of "assumption busting"?? It's a structured way of brainstorming to uncover and challenge untested assumptions. Also in the risk world there's a whole methodology based on assumptions, called ABCD (Assumption Based Communication Dynamics).

My personal hidden assumption relates to my health - I assume I will never be sick, in fact I think I'm probably immortal...! So I never include any contingency in my plans for poor health or days off work. I suspect this assumption is quite widespread?!

Please Login/Register to leave a comment.

ADVERTISEMENTS
ADVERTISEMENT

Sponsors