People confuse risks with problems that already exist. How do we separate them?

Risk-issue confusion

Describe a risk as an uncertain event or condition and an issue as something already requiring resolution. Link them when appropriate without losing the distinction between prevention and response.

What to do now

  1. Check whether the event has occurred
  2. Record present facts separately from uncertainty
  3. Assign the appropriate response owner
  4. Connect related risk and issue records
Recommended action flow for risk-issue confusion: Check whether the event has occurred then Record present facts separately from uncertainty then Assign the appropriate response owner then Connect related risk and issue records. Escalate when misclassification delays a response to an active problem.

When to escalate

Escalate when

Misclassification delays a response to an active problem.

Who decides

The accountable risk owner

Example

Missing access today is an issue; the possibility of losing access next month is a risk.

Mistake to avoid

Debating terminology while a live disruption continues.

Prevent a repeat

Review whether response tasks and trigger conditions remain appropriate as the project changes.

Suggested ApprovedFlow setup

  • Documents
  • Tasks
  • Approvals

Store the risk assessment as a controlled project document and assign response tasks; do not assume a native risk engine is enabled. See the platform

Related cases

Practice references