Risk Management

I want to draw attention to an article that ran on June 20 in the monthly series' Claim Reduction' on the use of risk registers. See Project management tools with an eye on risk. What is your experience using risk registers?

A risk register is a valuable tool for managing risk, but like any tool, it must be used correctly. They must be more than a box exercise, and ideally need to be owned by the entire team. I've seen risk registers too often created and then left to die as they are forgotten. I am also leery of risk management specialists. Managing risks must be viewed as an integral part of the work, rather than an add-on. The team must consider both technical and non-technical risks broadly. As a final point, it is crucial to determine when each risk needs to be mitigated in the design process. The risk register is the ideal place to note this timing. Misalignment of risk mitigation and project maturity is a recipe for disaster. 

I want to draw attention to an article that ran on June 20 in the monthly series' Claim Reduction' on the use of risk registers. See Project management tools with an eye on risk. What is your experience using risk registers?

You make an excellent point, Mitch. Tracking risks is essential and projects I'm familiar with have primarily used spreadsheet-style Risk Registers to accomplish that. When applied conscientiously and reviewed frequently, they worked well. Otherwise they became places for legitimate concerns to languish. Subjective judgements and documentation/personnel burdens are themselves risk factors in effective use. 
I'm wondering if Risk Register software is helpful. Does anyone have experience with useful tools?

Bill Mc

A risk register is a valuable tool for managing risk, but like any tool, it must be used correctly. They must be more than a box exercise, and ideally need to be owned by the entire team. I've seen risk registers too often created and then left to die as they are forgotten. I am also leery of risk management specialists. Managing risks must be viewed as an integral part of the work, rather than an add-on. The team must consider both technical and non-technical risks broadly. As a final point, it is crucial to determine when each risk needs to be mitigated in the design process. The risk register is the ideal place to note this timing. Misalignment of risk mitigation and project maturity is a recipe for disaster. 

I want to draw attention to an article that ran on June 20 in the monthly series' Claim Reduction' on the use of risk registers. See Project management tools with an eye on risk. What is your experience using risk registers?

A risk register is a valuable tool for managing risk, but like any tool, it must be used correctly. They must be more than a box exercise, and ideally need to be owned by the entire team. I've seen risk registers too often created and then left to die as they are forgotten. I am also leery of risk management specialists. Managing risks must be viewed as an integral part of the work, rather than an add-on. The team must consider both technical and non-technical risks broadly. As a final point, it is crucial to determine when each risk needs to be mitigated in the design process. The risk register is the ideal place to note this timing. Misalignment of risk mitigation and project maturity is a recipe for disaster. 

I want to draw attention to an article that ran on June 20 in the monthly series' Claim Reduction' on the use of risk registers. See Project management tools with an eye on risk. What is your experience using risk registers?