The weekly project meeting, second half. The Risks & Issues Log goes up on the screen. 61 rows, in the order they were raised, with a column that says Risk or Issue.
The team works through it line by line. Every issue gets a proper discussion, because everybody already knows about it and somebody wants to know what is being done. The risks get a glance. “Still open. Next.” By row 40, half the room has left for their next meeting.
Next Tuesday, row 31 looks different. Same description, same owner. The word in the second column now says Issue.
Risks are not issues. A risk is something that could happen in the future. An issue is something that has happened. Issues are the past, risks are the future, and the moment they share a list and a meeting, the past wins every time.
The Van that went Quiet
Picture a small delivery company with twenty vans and one mechanic. Every Monday morning, the owner, the drivers, and the mechanic go through the list of van problems and things to check. Written down as they come in, one long list.
A driver complains about a squeaking wheel on van 7. Loudly, every morning, for a week. Van 12 would not start on Thursday. Those get sorted first. The squeaky wheel gets the grease.
Further down the list, a quieter line: van 9, tires worn, replace before winter. Nothing is wrong with van 9. It drives fine. So that line gets a nod, and the meeting moves on.
The first frost arrives on a Friday. Van 9 slides into a ditch with a full load. Nobody is hurt, but the deliveries are a day late, a customer is furious, and the mechanic spends the weekend on a tow truck and a bent axle. The following Monday the list is longer, the mechanic is further behind, and the tire checks on the other vans slide another week.
On Monday, the owner thanks the mechanic in front of everybody for giving up his weekend.
Nobody has ever thanked him for the van that did not end up in a ditch.
The Fire Brigade
Every project manager is taught to keep a risk log, and the reasoning sounds right. You need to see issues coming. Right?
Wrong. You need to stop issues from happening. That is the whole point of managing risks: find what can go wrong, then take action to remove it, or at least make it a lot less likely.
Some risks cannot be removed or reduced much, for example because the mitigation would cost more than the damage. Those you watch closely, and you agree the response in advance. What happens, who acts, and with which money, on the day the risk turns into an issue. Watching tells you when. The response is the fallback.
A shared list and a shared meeting turn all of this around. Issues make noise. They block today’s work, somebody is already asking about them, and the Steering Committee wants to hear what is being done. Risks are quiet, right up to the moment they are not. So the team spends its time on the issues, and the risks grow into issues nobody prepared for. Which means more firefighting, which leaves even less time for the risks.
More and more projects keep a RAID log these days, with Risks, Assumptions, Issues, and Dependencies each on their own tab. That is a step forward. But in the project meeting and in the Steering Committee, the RAID log is still one item on the agenda. And the I still beats the R, every time.
At the front of the fire brigade, more often than not, is the project manager. Not always by choice. When something is going wrong, the organization wants to see the project manager dealing with it personally. It looks like leadership, and in the moment it feels like leadership. Meanwhile, nobody is looking at row 31.
A Schedule of Its Own
Any serious fleet worked this out long ago. Repairs come in when they come in. Maintenance runs on its own schedule, and a van does not skip its service because another van broke down.
Projects can do the same without extra bureaucracy.
Give risks their own slot. Separate tabs are not enough. Risks need their own time on the agenda: a short session every two weeks or once per sprint, with the people who own the actions. If they share a meeting with issues, risks go first, while everybody is still in the room.
Give every risk an owner, an action, and a date. Where the action costs money, reserve the money. A risk with “monitor” in the action column and nothing else is a risk nobody is managing.
Agree on the response for the risks you keep. Write down what happens when it turns into an issue, before it does.
Let the team leads handle the issues. Not every issue needs the project manager. Keep the project manager’s time for the risks nobody else is looking at.
Ask about risks first. The Steering Committee sets the tone. If its first question is about the top risks and what is being done about them, that is what the project manager will come prepared for.
Teams with an Agile background have a head start on issues. Impediments come up at the daily stand-up and get cleared. Risks have no ceremony of their own. Unless somebody gives them one, they wait.
Van 7 got its grease, by the way.
Van 14 got new tires the week before the frost. Nobody noticed.




I've seen the types of meetings you describe here far too many times!
Beyond separating risks and issues, another common behaviour I've seen is people turning up simply to discuss them rather than actively managing them between meetings. The discussions should focus on the decisions or support needed to mitigate risks or resolve issues, whether that's management direction, funding or other interventions, rather than a line by line audit.
I dread to think how many cumulative hours are lost going through logs only to hear 'yes, this risk is still up to date'. Next!