← Back to Concept Contrast

Concept Contrast Fable

Risk register and risk owner: one writes risks down, the other makes sure someone owns them

Conclusion first:In project governance documents, risk registers and risk owners are often mentioned together, so some teams assume that once a register is built, someone is naturally responsible, and once an owner is designated, control naturally exists. The register is a recording tool that answers what risks exist and their respective statuses; the owner is an accountability role that answers who tracks each risk and who triggers response actions. If either is missing, risks will slip through.

In project governance documents, risk registers and risk owners are often mentioned together, so some teams assume that once a register is built, someone is naturally responsible, and once an owner is designated, control naturally exists. The register is a recording tool that answers what risks exist and their respective statuses; the owner is an accountability role that answers who tracks each risk and who triggers response actions. If either is missing, risks will slip through.

Fable

The hospital's shift handover log

The ICU of a top-tier hospital had a shift handover notebook. During nurse handovers, all patients' special precautions were written in the notebook: Bed 3 had unstable blood pressure, Bed 7 had a drug allergy, Bed 9 needed a blood gas analysis at dawn. The notebook sat on the nurses' station counter, and the first thing every nurse did at handover was flip through it.

The new head nurse found the notebook densely written, but many entries toward the back remained stuck in "pending observation," with no one signing off on the outcome. Bed 3's unstable blood pressure had been written for seven days, appearing at every shift handover, yet in those seven days not one record clearly stated who was tracking it, whether the orders had been adjusted, or whether the blood pressure trend was improving or worsening.

The head nurse changed the rules: every high-risk entry in the handover log must be tagged with the responsible person for that shift. When writing that Bed 3's blood pressure is unstable, add a nurse's name and the time tracking began. At the next shift handover, the responsible person must update the status: improving, worsening, or unchanged. Entries without a responsible person's signature don't count as a completed handover.

In the first week of enforcing the rules, a typical problem surfaced. Four entries in the handover log had never been assigned an owner—all written hastily by nurses while busy, no one claimed them, so no one followed up. The head nurse printed the unclaimed items and posted them on the whiteboard, and every morning meeting started by going through the unclaimed list until every item had a name signed to it.

During a hospital infection inspection half a year later, the inspection team randomly selected twenty shift-handover records to check the closed-loop handling rate. The pass rate had risen from sixty percent before the rules were changed to ninety-two. The inspection team asked the head nurse what she had done right, and the head nurse said she had done only one thing: every risk written in the notebook had to have one person sign and take responsibility. The notebook is the container, the signature is the engine.

Later, the nursing department extended this lesson to the whole hospital: when any risk registration tool is procured or launched, the acceptance criteria must include two items—whether each entry can be linked to an owner, and whether owner changes are recorded. The tool itself does not solve the responsibility problem, but if the tool does not support responsibility linkage, responsibility records will scatter across chat logs and verbal handovers.

At the year-end review meeting, the director of nursing wrote only six words: registration is not management. No matter how thick the notebook or how many entries, an entry without a signature is just a line of description. Turning description into management action depends on a person standing behind that signature line.

Risk Register

A document or system that records identified risks, including risk descriptions, levels, status and handling, serving as a tool for storing and managing risk information.

Risk owner

The individual or role responsible for tracking and responding to a particular identified risk, responsible for monitoring changes in risk status and initiating response measures when trigger conditions are met.

Story Mapping

  • The ICU duty handover log records all precautions: risk register, a container for storing identified risks
  • Each high-risk record is marked with the responsible person on duty: risk owner, responsibility attribution for each risk
  • Four records were never assigned an owner and no one claimed them: a typical governance gap where a registry was built but no owner was assigned
  • Unclaimed items are reviewed on the whiteboard every morning meeting: organizational mechanisms supplement tool gaps—use process to ensure every item has an owner
  • Registration is not management: containers provide visibility, signature lines provide driving force

Applying it to an Agent project

When establishing a risk register after an Agent project starts, assign an owner directly to each risk. The owner does not need to be a technical expert, but must clearly understand the monitoring frequency, trigger conditions, and escalation path for the risk they own. In the weekly meeting, spend five minutes reviewing entries in the register whose owners have not updated their status for more than seven days—these are risks that were written down but no one is managing. When choosing tools, prioritize options that support linking each item to an owner and automatic reminders.

京ICP备2026014272号