Risk
How to present risk in a way that strengthens credibility by making uncertainty, likelihood, impact, mitigation, and residual risk visible.
Avoiding risk makes a proposal less credible
A plan that only presents the best case invites doubt.
Decision-makers usually ask which risks matter most and whether the team has thought them through.
Risk is not a list of bad things that could happen
Useful risks connect directly to outcomes, dependencies, or important assumptions.
Framework: Risk → Likelihood → Impact → Mitigation → Residual Risk
Risk — what could go wrong?
Likelihood — how likely is it?
Impact — what happens if it occurs?
Mitigation — what reduces probability or impact?
Residual Risk — what uncertainty remains afterward?
Likelihood helps prioritize
A catastrophic but extremely unlikely risk may deserve less attention than a moderate, highly probable one.
Impact should describe real consequences
Delay, cost overrun, weak adoption, quality issues, compliance exposure, stakeholder conflict, or technical limitation can all be impacts.
Mitigation should be an action, not reassurance
“We will monitor closely” is weak mitigation.
Pilots, phased rollout, fallbacks, buffers, approval gates, backup vendors, and technical spikes are concrete actions.
Residual Risk makes the proposal more mature
Not every risk can be reduced to zero.
Stating what remains shows that the team is not overclaiming.
Risk should connect to an owner and trigger
Important risks should have an owner and a signal that determines when action is required.
Applying this on Forwork
A Forwork Proposal can include Risk, Likelihood, Impact, Mitigation, Owner, Trigger, and Residual Risk.
After approval, Work Tracking can continue from the same risk record.
Conclusion
Do not try to prove the plan has no risk.
Prove that the important risks have been seen, prioritized, and given a response .
Risk → Likelihood → Impact → Mitigation → Residual Risk.