← Back to Concept Contrast

Concept Contrast Fable

Signing off to take on risk, and the risk that remains after handling

Conclusion first:Risk acceptance is a management decision—determining that the current risk level is acceptable, adding no further controls, and bearing the consequences once signed. Residual risk is the amount of risk objectively remaining after risk treatment; no matter who signs, it is still there. The two are adjacent upstream and downstream in the same process: treatment produces residual risk, and decision-makers decide whether to accept the residual risk or add more measures. Mixing them up makes the signer think they have eliminated the risk, while the risk is actually still there.

Risk acceptance is a management decision—determining that the current risk level is acceptable, adding no further controls, and bearing the consequences once signed. Residual risk is the amount of risk objectively remaining after risk treatment; no matter who signs, it is still there. The two are adjacent upstream and downstream in the same process: treatment produces residual risk, and decision-makers decide whether to accept the residual risk or add more measures. Mixing them up makes the signer think they have eliminated the risk, while the risk is actually still there.

Fable

The water-level gauge on the dike and the signature book at the gate: numbers are measured, not signed into existence

In the river defense office there was a dike keeper and a gate officer. Every flood season, the dike keeper first built the first dike, dug diversion channels, and piled sandbags at weak sections. After that, he placed a water-level ruler against the gate opening and reported a number to the gate officer: water level in front of the gate, three chi seven. The gate officer took the number, glanced at the warning line—five chi—and then signed to confirm: if it does not exceed five chi, do not open the gate. This process ran for three years, and the crops of every village were preserved.

Then one summer, the rain fell for twelve days straight. The water level rose from three chi seven all the way to four chi five. The levee keeper measured and reported the number as usual, and the sluice officer signed off as usual: not yet at five chi, so the gate stays closed. Neither said anything more. On the third night, an old levee upstream cracked, water surged downstream, overtopped the sluice, and flooded two villages. When they investigated afterward, people came down from the province.

The investigation team found that the two people were looking at the same table but understanding different things. On the dike keeper's table, one line clearly read "Residual risk: four chi five," with response measures listed below—build dikes, divert floods, stack sandbags. The page the gate official signed was titled "Risk Acceptance," and he thought signing it meant the risk was already resolved. He did not know that building dikes only pushed the water level down from six chi to four chi five, not to zero. The dike keeper thought the gate official had signed only after seeing the residual risk figure; the gate official thought that once he signed, the water level would return to zero.

The investigation team posted a new flowchart on the yamen wall. The first column was initial risk—if left unaddressed, it would rise to six chi. The second column was treatment measures—after building the embankment, it was pressed down to four chi five. The third column was residual risk—four chi five, not zero. Only the fourth column reached risk acceptance—the gate officer's signature decision after reviewing four chi five. The signature governed the decision in the fourth column; the risk itself was only related to the number in the third column.

The yamen changed the system and required dual signatures. The levee keeper signed the disposition certificate, clearly stating in writing what he had done and how much risk remained after disposition. The gate official signed the acceptance certificate, confirming that he had seen the remaining risk figure, knew how much remained, and was willing to bear the consequences. The two signatures were not on the same line: one defined the boundary of disposition, the other defined responsibility for the decision.

After that, during an autumn flood, the water level reached four chi eight. The dike keeper reported "four chi eight remaining after handling," and the gate officer compared it with the evacuation route map from the neighboring village and signed to accept it. The next day the water level climbed to four chi nine, and the gate officer opened the gate one shichen early, so the water did not enter the village. During the retrospective, the investigation team wrote five words in the conclusion column: numbers are numbers, decisions are decisions.

When the old levee keeper retired, he left his apprentice one line: mitigation measures can lower risk, but cannot eliminate it. Reporting residual risk honestly is ten times more useful than making it look good, because the gate officer holds the lives of several villages in his hands.

Risk acceptance

A formal decision by management on the current risk level—determining that the residual risk is within acceptable limits, adding no further controls, and accepting the possible consequences. This is a management action with a signatory, an effective date and acceptance conditions.

Residual risk

The level of risk that still objectively exists after all planned treatments and control measures have been implemented. It is a measured value that does not change because of anyone's signature, and it serves as an input to risk acceptance decisions rather than an output of them.

Story Mapping

  • The dike keeper measures the water gauge: measuring residual risk—the objective remainder after treatment measures
  • The gate official signs to confirm the gate will not be opened: risk acceptance—management's formal decision on residual risk
  • Each thought the other understood the part they had not said: the misunderstandings each side upstream and downstream of the process assumed by default
  • The flowchart's four columns make it clear: residual risk and risk acceptance belong to different stages, with no equals sign between them
  • Dual-signature system: the disposition certificate governs what was done, the acceptance certificate governs how a decision was made after review
  • In the autumn flood, the numbers were reported clearly and decisions had a basis: in the correct process, assessment and sign-off each bear their own responsibility

Down to the AI system risk assessment process

When doing AI system risk assessment, first have the technical team report residual risk—how much risk exposure remains after content filtering, permission controls, and training data cleaning. Then have decision-makers perform risk acceptance—review the report, judge business tolerance, and sign to accept. There are two key disciplines: treatment measures can never reduce risk to zero, and honestly reporting residual risk matters more than making the numbers look good; the signer needs to understand that their signature governs the act of acceptance, and it does not change the actual value of the residual risk. Keeping the residual risk report and the risk acceptance record as two separate documents will make the audit trail much clearer.

京ICP备2026014272号