Insight

The risk register

Most risk lists name what is tangible. The risks that really derail a change are human, and those are rarely on the list.

what is on the list the tool is not ready IT the budget has run out finance the planning is slipping project management what is not on it silence after the announcement passive withdrawal fatigue from the last round the sponsor drops away no owner, no first signal
The list you have, and the list that derails the change.

What this is about

A risk list in a change almost always names what is tangible. The tool is not ready, the budget has run out, the planning is slipping. Those are real risks and they belong there. But what derails a change is rarely the tool. It is the silence after the announcement, the group that quietly withdraws, the fatigue from the last round, the sponsor who stops showing up after go-live.

The risk register is where that second kind does appear. It belongs with the readiness heatmap: that shows where the organisation stands today, the register shows what can go wrong if you leave it alone.

From an amber or red zone to a risk

You start from the heatmap. For every amber or red zone you ask three questions. What is the risk here, in one sentence. What would you see first if it started to go wrong. And who does something about it.

Those three together turn a worry into a risk. Leave one out and what you have left is an opinion.

A risk without a first signal is an opinion

The second question is the hardest and the most useful. Silence is not a signal, because there is silence somewhere at all times. But “the team leaders have stopped asking questions in the weekly meeting” is one, and you notice it within two weeks. “The helpdesk gets more questions about the old way than about the new one” is another.

Whoever cannot name that signal has not made the risk sharp yet. That is no reason to drop it, it is a reason to spend another conversation on it.

The owner sits in the sponsor group

A risk gets an owner, and that is not the change manager. They do see the risk, but they rarely have the mandate to do anything about it. The owner is somebody from the sponsor group who holds the people, the time or the priority. That is the same rule as in ownership with a mandate: without a mandate an owner is a letterbox.

A risk nobody in the sponsor group wants to own is a finding in itself. Usually it means the risk is not believed yet, or that the person who holds it is not at the table.

How we go about it

We collect the risks in the same conversations in which we score the heatmap, not in a separate round. Whoever gives an amber or red cell usually has an immediate picture of what happens then. That picture is the risk. And we put the register beside the heatmap at the steering group, not as reporting but as the question of where we begin. Read more about how we work →

When this helps

As soon as the heatmap is there and you discuss the order of the rollout with the steering group. It also helps when the project’s risk list holds only technical lines, because then you know the human side sits with nobody. And it helps after a go-live, because the risks then shift from “does it land” to “does it hold”, and that is exactly what relapse after success is about.

Are the human risks on your list?

In a conversation we go through your risk list for what is not on it, and for who should own it.