Project Management

Please login or join to subscribe to this thread

Unknown - Unknown Risks

linkedin twitter facebook   New Practitioners   Risk Management   Using PMI Standards  
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
We are more familiar with the Known-Unkown Risks but I'm sure everyone has encountered some unknown-unknown risks in their own projects / industry. Can you give an example of a U-U Risk you encountered and what action you had to take? how did it impact the project?
Sort By:
< 1 2 3 >
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
Mar 23, 2016 1:13 PM
Replying to Stéphane Parent
...
My biggest U-U risk was a province-wide power outage during development. You can plan and mitigate localized outages, it is more difficult to find alternatives in broad-based disasters.
This is very true Stephane.
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
Mar 23, 2016 1:41 PM
Replying to Thomas Walenta
...
Hi Rami,
agree, you can never identify all risks. The U-U risks are then what is left over, I heard the them residual risks for them.
As risk identification depends on the experience and knowledge you have available about the project, you will have higher U-U risks with less of own capability. Risk checklists or risk breakdown structures can mitigate that risk.
Example: when I did my first project with subcontractors, I just did not understand the implications and pitfalls of contract negotiation, understanding, control etc.. Only the problems that arose as a surprise (that were U-U risks for me), gave me the opportunity to learn.
I totally agree with you on this Thomas .. Thanks.
avatar
Anonymous
Feb 02, 2016 7:43 PM
Replying to Bruce Gay
...
One example of unknown unknowns, or unexpected or unforeseeable program conditions, was the enterprise-wide firing and consolidation of multiple Chief Information Officer (CIO) positions at my organization. Several CIOs were key stakeholders and enthusiastic supporters of the program I was managing. Our program leadership, myself included, had to navigate the new landscape of "executive stakeholders" to build support for our efforts. We had to take additional steps to communicate the benefits of the program and to gain trust of the new CIOs. In the end, the impact on the project team was minimal.
Thanks.
< 1 2 3 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Time is an illusion, lunchtime doubly so."

- Douglas Adams

ADVERTISEMENT

Sponsors