Skip to content
Operational Risk Management | Part 1 of 8

What Counts as a Risk, and What Is Only a Concern

Cause, event, effect and one named owner: the four parts of a risk sentence, and why a register full of topics can never be rated or decided.

Ask a plant for its risks and you get a list in ten minutes. Suppliers. People. IT. The old roof. Energy prices. Every entry is true, and not one of them can be rated, owned or closed. That is the first problem of most registers: they collect topics instead of risks.

Four parts, one sentence

A risk is an event that has not happened yet, with a cause that makes it possible and an effect that can be counted. Write all three in one sentence and add the person who can act on it.

The cause answers why the event is possible here. In the example plant used throughout this series, a site for conveyor components with 320 people, the cause is that one machining center makes the drive housing and no second route exists, inside the plant or outside it.

The event answers what happens, in one sentence, at one point in time: MC-200 is out of production for more than three days.

The effect answers what it costs, in EUR and in days: eighteen days without housings. The plant makes 400 housings a day at a contribution margin of EUR 85, so a lost day costs EUR 34,000. Eighteen days are EUR 612,000, and the spindle repair adds EUR 8,000. The effect is EUR 620,000.

The owner is a person, not a department. Departments do not act. The operations manager does, because he can release a budget and call an external machining partner.

Why the discipline pays

A sentence with four parts can be rated, because the probability belongs to the event and the number belongs to the effect. A measure can attack either one: a buffer of finished housings shortens the effect, a second spindle in stock shortens the repair. A topic such as “our equipment is old” offers nothing to attack.

It also settles arguments. Two people who disagree about a risk usually disagree about the event. One is thinking of a four-hour stop, the other of a three-week breakdown. Those are two risks with different probabilities and different measures, and they belong in two lines.

Concerns, rewritten

Most concerns hide a usable risk. The work of the first week is to pull it out.

A concern sounds like The risk behind it sounds like
Our people are overloaded The only CNC programmer is unavailable for more than four weeks, no new programs are released, and the launch of the roller series slips 15 days
The suppliers are getting worse The single source for the drive motor stops delivering and 26 production days are lost before a second source can deliver
IT is a black box ERP and MES are unavailable for twelve days after an attack, picking and shipping run on paper and deliveries are late
The building is old Water comes through the roof above the parts store, five days are lost and EUR 60,000 of parts are scrapped

In the example plant, 38 raw entries from the collection round became 24 risks. Nine were duplicates. Five were concerns that nobody could turn into an event, and they were dropped with one line of reasoning, so they would not come back next year.

Where the boundary runs

This register works at the level of the site. Failure modes of a single part and process step belong to FMEA, where severity, occurrence and detection are rated per failure mode. What stays here is the plant level event: the line stands, with days and EUR. One register, one scale, one owner per line, and every entry a sentence a stranger could read out loud.

Newsletter

One Lean idea.
Every two weeks.