The 15-Minute Risk Check

The most beautiful risk matrix is worthless if the first time anyone opens it is on gate day.

We all know how it goes. At some point during the project, someone created a risk analysis - carefully, with colours, axes, probabilities. Then it was filed away. At the gate meeting, someone pulls it back out and everyone nods, because nobody knows whether the assumptions from back then still hold.

This is not a failure of individuals. It's a structural problem: risks are assessed once, but never continuously observed.

What we've learned at five is: it's not the most sophisticated tool that protects a project. It's the habit of pausing every two to three weeks for a moment.

Fifteen minutes. Five questions. No form.

The Five Questions

1. Which assumptions is this project still standing on?

Write down the three to five most important assumptions - not from memory, but from the last gate document. Then ask yourself: which of these have I actively tested in the past two weeks?

If the answer is "none", that's already a signal.

2. Which new signals have I been ignoring?

A supplier who's hesitating. A stakeholder who's suddenly harder to reach. A test result that doesn't quite fit. Write down what you've noticed but haven't yet evaluated. No need to dramatise - just name it.

These signals are often the earliest indicators of what later turns out to be decisive.

3. How likely is it to happen — today?

Take your most important risk. Re-estimate the probability — not based on the old matrix, but based on what you know right now.

Has it changed? By how much? Why?

If you can't answer that question without opening the old file, that's a clue: the risk doesn't live in the team's heads. It only lives in the document.

4. What would the impact be on time, cost, and scope?

Not in abstract categories like "high" or "medium" — but in weeks of delay, in resources, in project objectives.

"Medium" is not a basis for decisions. "Three weeks of delay and a threatened Gate 3 date" is.

5. What is the next countermeasure — and who is responsible?

One measure. One person. One date.

If you can't put those three things into a single sentence, it's not a measure yet. It's an intention.

How to Introduce the Check

Take the last five minutes of your next project meeting. Ask the five questions out loud. Write the answers somewhere visible — on a whiteboard, in a shared document, on a piece of paper.

No template. No tool. Just the questions and the willingness to answer them honestly.

Regular pausing doesn't reduce the number of risks. It sharpens the understanding of them. And that changes how a team walks into a gate meeting.

The moment projects become expensive or fail is almost always the same: when a risk that everyone had somehow sensed gets spoken out loud for the first time only on gate day.

Fifteen minutes every two to three weeks can prevent exactly that.

Picture is AI-generated.