Risks in your project’s rear view mirror may be closer than they appear
From the Easy in theory, difficult in practice Blog
by Kiron Bondale
My musings on project management, project portfolio management and change management.
I'm a firm believer that a pragmatic approach to organizational change that addresses process & technology, but primarily, people will maximize chances for success.
This blog contains articles which I've previously written and published as well as new content.
Recent Posts
Leading Through Crisis Means Leading Through Context
"It's the end. But the moment has been prepared for." - retirement lessons from the Doctor
Just because they are non-critical, doesn't mean they are not risky!
Just because they are non-critical, doesn't mean they are not risky!
How will YOU avoid these AI-related cognitive biases?
Categories
Agile,
Artificial Intelligence,
Career Development,
Change Management,
Communications Management,
Decision Making,
Governance,
Hiring,
Kanban,
Lessons Learned,
Personal Development,
PMO,
Portfolio Management,
Project Management,
Resource Management,
Risk Management,
Risk Management,
Schedule Management,
Scheduling,
Tools
Date
Risk management, like nearly all project management knowledge areas, is iterative. We don’t just identify risks at the beginning of our projects. As we learn more about what we are expected to deliver, our risk registers experience progressive elaboration in the same way as does our knowledge of our customer’s requirements or our work breakdown structure.
While this iterative nature of risk management helps to increase the currency of risk information, it does have a dark side.
The risks we’ve most recently analyzed might appear to be more relevant than those identified much earlier in a project’s life. Given how busy we all are, if those older risks have not yet been realized, it can be tempting to assume that they can be safely ignored. And when our vigilance drops, that’s usually when those risks will strike.
To protect against this, we need to implement countermeasures which won’t consume much effort, but can provide us with sufficient lead time to recognize that a risk may be realized so that we can execute response plans with a higher probability of success. This is why it is important to identify risk triggers which should be as specific as the risks they are associated with.
It’s also a good reason to consider going beyond simple probability and impact-based assessments of risk severity by incorporating the failure mode effects analysis practice of estimating how easy it is to detect that a risk is about to be realized. By doing this, a moderate risk with low detectability will gain importance relative to those which we can see a mile away.
Of course, none of this matters if risk information is not reviewed regularly.
You may want to review risk triggers for your key risks at each team meeting to find out if any have been detected. You might even consider creating a “Project’s Top Ten Most Wanted” cubicle poster highlighting the triggers tied to your most critical risks.
Whatever techniques you use, regular reviews of meaningful triggers can act as a gauntlet around your project, ensuring you don’t get rear-ended by a risk Mack Truck!
(Note: this article was first seen in kbondale.wordpress.com's rear view mirror in June 2015)
Posted on: August 07, 2018 06:59 AM |
Permalink
Comments (16)
Please login or join to subscribe to this item
Vincent Guerard
Coach - Trainer - Speaker - Advisor| Freelance
Mont-Royal, Quebec, Canada
Nice post, Kiron
Identifying trigger is not easy, not always possible.
Love the "Most wanted poster"
Thanks Vincent - we always need to find new and interesting ways to make risks matter to our stakeholders so humor might work where fear hasn't!
Kiron
Thanks for sharing Kiron!!
Good post, Kiron. Thanks for sharing good trigger ideas.
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates
New Westminster, British Columbia, Canada
You make some good points Kiron.
Damian Perera
Monitoring & Evaluation Specialist| Chrysalis
Mellawagedara, Western Province, Sri Lanka
FMEA is a good approach to anticipate risks or failures. Thanks
Tamer Zeyad Sadiq
Assistant Cost Manager| Turner & Townsend
Riyadh, Ar Riyad, Saudi Arabia
Risk analysis is iterative, always happen and must monitor the status periodical!!!
Thanks Rami, Damian & Tamer!
Kiron, I can't give vote here NO button but I gave you the highest rating.
anca stefanescu
Project methodology expert| BRD GROUPE SOCIETE GENERALE
Bucharest, Romania
I think usually in projects risks are closer than they appear. I think the problem is we judge them through our subjective human nature, instead keeping the rationale upfront. We have enough means to register, monitor, identify risks, what we do next and how we use them is the most important.
Thanks Riyadh - I appreciate that!
Thanks Anca - you are correct. Identification and analysis is academic if we don't effectively respond to key risks.
Drew Craig
Sr. Agile & Product Coach| Vanguard
Philadelphia, Pa, United States
Great points, Kiron. Thanks for sharing the post here. Love the title : )
Anish Abraham
Privacy Program Manager| University of Washington
Auburn, Wa, United States
Good one, Kiron and thanks for sharing.
Triggers are so important, but yes a top 10 most wanted is a good idea. Thanks Kiron.
Please Login/Register to leave a comment.
|
"The radical of one century is the conservative of the next. The radical invents the views. When he has worn them out, the conservative adopts them."
- Mark Twain
|