All essays

Cyber leadership

Board reporting that survives the second question

Most risk dashboards survive the first question from the board. Few survive the second. The difference isn't design; it's whether every metric has an owner, a threshold and a decision attached.

Roy Biakpara, , 7 minute read

Most risk dashboards survive the first question from the board. “Are we on track?” is easy: a green tile answers it. It's the second question that exposes the programme: “How do you know?”

When that question lands, a weak report reaches for more data. A strong one reaches for an owner. Every metric that reaches the board should carry three things: a named accountable executive, a threshold agreed in advance, and a decision it is designed to prompt.

Fewer, truer signals

The instinct in most GRC functions is to demonstrate effort: forty KPIs, heat maps, trend lines. Boards read that as noise, and noise is where risk hides. I'd rather give a board six indicators tied directly to risk appetite than sixty that describe activity.

If a metric can't change a decision, it doesn't belong in the board pack.

Start by mapping each principal risk to the one or two indicators that would genuinely move if exposure changed. Then ask the owner to commit, in writing, to what they will do when the indicator crosses its threshold. That commitment is the real control. The chart is just how you show it.

Evidence, not narrative

Finally, make sure every number can be traced back to evidence without a heroic effort. If producing the board pack takes a fortnight of spreadsheet surgery, the pack is measuring your team's stamina, not your control environment. That's precisely the gap platforms like AccordaGRC exist to close: evidence collected as work happens, so reporting becomes a view rather than a project.

Next essayAI assurance without the theatre