What is the correct interpretation of the Risk Status Not Achieved and Achieved?

Carlos Blando
Kilo Contributor

As I understand:

If the risk event did not happen the best option is Not Achieved, which would be equivalent to closed, did not happen and will not happen.

If the risk event happened the option would be Achieved and could generate an Issue, Action or Decision.

If this interpretation is correct, why is the Not Achieved marked in red and the Achieved in green?

find_real_file.png

Any help will be appreciated.

 

Thank you

 

Carlos

 

 

 

 

 

 

 

 

3 REPLIES 3

Saiganeshraja
Kilo Sage
Kilo Sage
if you are able to mitigate the risk then it's considered as achieved(equivalent to closed).if you are yet to mitigate the risk then it's not achieved that why in red color.(equivalent to open) Mark correct and helpful

Saiganeshraja, thanks for your response. But I see some inconsistence because when you mitigate the risk, it is decreased their probability and/or impact, but it yet could be realized, it is not closed or achieved. There is a specific status for this situation: MITIGATE.

Frank67
Tera Expert

I always assumed this was a big specification/dev/test fail by Service Now that  appeared a while back (London/Madrid/New York days?). Like a lot of the SN documentation there is no advice on how to use it, just a description of what the statuses are. Which is fine except for the traffic lights being completely counterintuitive with what seems to be the most logical interpretation of the achieved/not achieved status.

Like you, our interpretation is:

Achieved = risk has been realised. Not a good thing, and should be red, not green. 

Not achieved = risk has not been realised. A good thing, and should be green, not red. 

Pending, avoid, mitigate, transfer, accept statuses are all pretty self-explanatory. 

I assume they haven't fixed it because people haven't complained, and/or old modules like project management get no love, they work reasonably well (once you work out how you'll apply them with your processes) and SN is too busy working on new stuff to enhance the old stuff.  We still use them, generally later in the project once the other statuses become less relevant, but it's annoying, for sure.