Crossing the River: Risk Needs an Owner, Not a Personality Contest

A group must cross a river.

Drive looks for a workable way across and focuses on the cost of waiting.
Connect gathers people, communicates the plan, and builds confidence to move together.
Sustain considers how every person will cross and what pace or support keeps the group intact.
Verify checks depth, current, weather, structure, equipment, and failure points.

The group needs urgency and caution, but neither is the decision rule by itself.

The risk lesson

Good risk decisions make five things explicit:

Outcome if action succeeds
Consequence if it fails
Evidence and uncertainty
Safeguards and recovery
Person authorized to accept residual risk

“I am comfortable with risk” is not authority to expose customers, employees, money, or critical systems. “I need more evidence” is not authority to delay forever when delay has its own consequence.

Business example

A critical vendor tool is unavailable. The fastest workaround is to share one administrator account.

Drive sees customer work waiting.
Connect sees people needing a simple path.
Sustain sees the disruption and ongoing workload.
Verify sees lost accountability, excessive access, and credential exposure.

The answer is not “security says no.” Define a safe temporary path: named accounts, minimum privilege, time-limited approval, activity record, removal owner, and a recovery/normalization date. If no safe path exists, the authorized risk owner decides how to reduce service rather than letting any individual improvise the exposure.

Try this

For one current exception, complete:

We are trying to achieve…
If we wait, the consequence is…
If the workaround fails, the consequence is…
The minimum safeguards are…
The residual risk owner is…
The exception expires…
Evidence of removal/recovery will be…

BOS links: Security, Continuity, Control, Operations.
Misuse warning: Risk tolerance is not risk competence, legal authority, or ethical permission.