Skip to main content

Uncertainty is not Risk...

People tend to mix up the terms Risk and Uncertainty and use it interchangeably. They think that if there is uncertainty related to some task or some element of the project, then it is Risk. Some times yes and some times ‘No’ and it actually depdends.

Before getting into the details, let us define ‘Risk’ and ‘Uncertainty’.

"Risk is defined as what we stand to lose or gain, if certain events occur."

"Uncertainty refers to the lack of confidence that we express w.r.t events that we want to observe".

Risk is typically calculated using the formula “Risk = Probability of happening X Impact of the event” – when ‘the event’ happens. i.e. Risk is a function of Probability and Impact.

Expressing mathematically, Risk = f(probability, impact).

Probability has an element of Uncertainty Associated with it. Probability and hence uncertainty, is a factor in arriving at Risk.

This relation can be expressed mathematically as Risk = f[Probability(uncertainty), Impact]

People usually have this in mind when they mix up Uncertainty and Risk. But if we look into the equation above, we will see that it is not only the uncertainty, but also the impact, that determines whether a particular event that will happen in the future, qualifies to be a risk.

So while Risk definitely has an element of Uncertainty Associated with it, all Uncertainty translates into Risk, only based on the impact.

That is why it is not right to use Risk and Uncertainty Interchangebly.

Let me know what you think.


Popular posts from this blog

Kano Model of Customer Satisfaction - Notes to Self

Note: What follows is the notes taken from my study of Kano's model of Customer Satisfaction. I came across this model when i wanted to know if there was a structured approach that would help me prioritize features for software product development. 

To evaluate a product or service, following parameters are very important

The value provided - this helps attract customersThe Quality offered - This earns customer respectProduct or Service innovation - This helps differentiate from competition
But these are not perceived directly, but indirectly through the product and it's features. Kano's model help to group product features into 3 categories ( 6 categories, but only 3 are important) and there by makes it feasible to deliver value at a promised quality while offering innovation. 

The 3 important feature categories are 
Basic featuresLinear featuresExciters or DelightersBasic features are that must be present in the product to be successful. They are also referred to as must have…

Knowns, Unknowns and Project Management...

This article is a draft of a paper i started to write in september 2007 and left it where you see it today.  The purpose is to to come out with a conceptual framework through which “the knowledge needed to successfully execute a project” can be viewed and gauged and presents a brief outline of the same. As always comments are most welcome...
Financial Resources, Domain, Technology, Communication, Cultural Differences, Organizational Structure, Organizational Culture and Power Play within an organization are some of the factors that have an ultimate bearing on the success of a project.
All projects come in shades of grey is a fact that has to be acknowledged. For example, when we start a project, very rarely do we know everything about Project Requirement, Scope and other factors that impact the project. There will be lot of ambiguity and this ambiguity has to be accepted and put to proper use.
But the problem is that people usually look at these factors in black and white. This may be ac…

Aggressive Schedules - Few thoughts...

During my early years in the software industry, i used to look at people who worked in projects with aggressive schedules, in awe. The people working in such projects talked about, long hours, working week ends and heroic endeavors in their projects. The people who worked in such projects were given more awards and rewards, compared to others. i thought that this was the way to be.

After working in projects with aggressive schedules, I realized that what I saw was only the silver lining and there was a big dark cloud behind this ( talk about what experience can do for you). The common thread that linked all the projects was that all of them exhibited one or more of the following.
Project ended up delayed by more than 100% Project got cancelled Project got de-scopedProject has a high cost of maintenance.  Having been burnt up by working in projects with “Aggressive Schedules’, (henceforth denoted as AS), I understand that projects with aggressive schedules cause more damage than what we …