We recognize that risk is a concept.
It is a useful concept as it helps us get a better handle on future uncertainties.
The AgileBCP risk lens can (and should) be applied BEFORE a disruption event – and AFTER a disruption event.
Nature’s warning color – red – is used to stimulate discussion. A ‘red flag’ calls for serious and immediate considerations. Orange – important but probably not immediate, Yellow – cautionary and needing to be watched closely, Green – sound but still keep an eye on it.
Risk puts on notice the need for conversations about what ought to be done – and what does not need to be done. Indeed the only reason for risk assessment is in order to inform action – or inaction. Risk assessment has no inherent merit. It ought not to be academic. Risk exists, as a concept, in order to inform decisions.
Once a decision is made, any implementation plan(s) should be kept as long as necessary but as short as possible. Specifying what needs to be done and what is needed to do it. Implementation plans are then supported by standard management practices of monitoring the achievement of the required outcomes by ensuring the plans are on track, on budget, and on time.