Most risk information isn’t designed to support a decision. It’s designed to demonstrate that a risk function exists.
The cost of saying too much
There is a finding from the world of artificial intelligence that has been circulating quietly among researchers this year. When AI systems were forced to produce shorter, less elaborate answers, they became more accurate. Not just more efficient — more accurate. Larger, more capable systems were being outperformed by smaller ones on certain problems. The reason, on investigation, was over-elaboration. The bigger systems were hedging, qualifying, and explaining their way past the right answer.
This is measurable in AI because every word has a price tag. The billing statement makes the cost of verbosity impossible to ignore. You can see, in black and white, what saying too much actually costs.
Risk management has no such invoice. But the problem’s identical — and the cost is just as real.
The padding problem
Risk reports get longer. Register entries collect caveats. Presentations add slides. Narratives expand to cover every possible angle, and somewhere in that expansion, the thing someone actually needed to know gets buried.
This isn’t laziness. It isn’t poor professional practice. It’s a completely rational response to the conditions most risk professionals work in. In organisations where accountability is contested and decisions are visible, length signals effort and effort signals safety. A long report is harder to criticise than a short one. A comprehensive document implies diligence. A precise one invites the question: what did you miss?
So reports grow. Register entries multiply. And the people who most need to act on the information quietly stop reading it.
When everything is framed as equally important, nothing registers as urgent. The signal disappears into the noise it was surrounded by.
Decision latency — the hidden cost
The real damage isn’t confusion. It’s delay. Decision latency is the gap between a risk being known somewhere in the organisation and a decision being made about it. Information arrives, gets processed into a document, reviewed, consolidated, and passed upward. By the time it reaches someone with the authority to act, it may be weeks old and wrapped in so much qualifying language that the urgency has gone entirely.
The risk was known. The decision came too late. And when the post-project review asks why, the answer is always the same: the information was there. Nobody can quite explain what happened to it.
Verbosity compounds as it travels. A padded risk entry in a project register feeds into a programme review. The programme review feeds into a portfolio report. The portfolio report feeds into a board summary. At each stage, noise from the layer below gets inherited and amplified. What arrives at the top isn’t a distilled version of what was known at the bottom. It’s a degraded one.
The Minimum Viable Signal
Kaleido Decision Intelligence — Core concept
Minimum Viable Signal (MVS)
The minimum viable signal is the smallest amount of information needed to support a specific decision, delivered to the right person at the right moment. No more. No less.
It’s not about producing less. It’s about being deliberate: knowing what level of signal a decision requires, and resisting the default to say more than is needed. The discipline of defining the MVS before writing any risk output is a test of analytical clarity as much as communication skill.
Strip the padding away
The same risk entry - use the slider to see what’s left when the noise is removed. This is just a simple example for illustration.
87 words per stage
1 clarity
signal strength
The concept draws from a discipline already familiar in product development: the minimum viable product. The insight’s the same — that excess, not absence, is usually the problem, and that stripping back to the essential reveals both quality and gaps that elaboration conceals.
Applied to risk management, it reframes the job entirely. The goal of a risk function isn’t to produce comprehensive risk information. It’s to deliver the right signal to the right person at the right moment. Different decisions require different signals. The project team managing day-to-day delivery needs different information from the programme board deciding whether to escalate. The investment committee reviewing a business case needs something different again.
Three questions
Every piece of risk information — every register entry, every report, every escalation — should be preceded by three questions. If you cannot answer all three, the signal is not yet ready to send.
01 · Who is the decision-maker?
Not the team. Not the committee. The specific person with the authority and accountability to act on this risk. If you cannot name them, the signal has no destination.
02 · What are they deciding?
The specific choice in front of them — not the general topic, but the actual decision between options that this risk affects. What will they decide if they don’t receive this signal? What do you want them to decide instead?
03 · What is the minimum they need to know?
The single insight that changes the decision. If they already knew this, would they decide differently? If not, it’s not the signal — it’s context. Strip everything back until you reach the fact that actually matters.
The third question is also a diagnostic. If a risk owner can’t answer it — can’t state in a single sentence the one thing the decision-maker needs to know — that’s useful information. It usually means the risk itself isn’t yet understood clearly enough to be managed. Long risk narratives often conceal analytical uncertainty rather than reflect analytical depth. Compression is a test of thinking, not just communication.
Pick a scenario, choose the decision-maker, then identify which of three options is the Minimum Viable Signal. The tool will assess your choice. This isn’t perfect and simply to illustrate key concepts
1 · Scenario
2 · Decision-maker
3 · Signal chosen
4 · Assessment
What changes in practice
The shift is visible at every level of a project. At entry level, a risk that passes the single sentence test: one cause, one consequence, one implication for a decision in progress. At report level, a structure organised around decisions pending rather than risks catalogued. At escalation level, a clear trigger: the decision required, the deadline, and the cost of not deciding.
| Current default | MVS discipline |
|---|---|
| Risk register organised by category and probability | Risk outputs organised by decision in progress |
| Full narrative written for the record | Signal designed for the specific recipient |
| Escalation passes a risk entry upward | Escalation names a decision, a deadline, and a consequence |
| Length implies thoroughness | Brevity implies clarity |
| Supporting detail is embedded in the primary signal | Supporting detail is available on request, not in the lead |
The distinction, ultimately, is between a risk register and a decision register. The first records what’s known. The second records what that knowledge implies for action. Most projects have the first. Almost none have the second.
Where MVS does not apply
The MVS discipline isn’t universal. Regulated or compliance-driven risk documentation must be explicit, regardless of the decision context. Complex technical risks that require full narrative for auditability should retain that depth. Learning-focused reviews benefit from elaboration rather than compression. The discipline is about routing — applying MVS where it serves decisions, and retaining depth where it serves accountability.
The MVS and Signal Decay
The MVS sits alongside Kaleido’s Signal Decay Pyramid (covered in a previous article), which describes what happens to risk information as it travels upward through organisational layers — how signals are translated, filtered, diluted, and sometimes lost entirely before they reach the people who need to act on them.
The two frameworks address different parts of the same problem. The Pyramid describes what goes wrong with signals in transit. The MVS describes what good looks like at the point of origin — designing the signal correctly before it enters the system. Together they form a complete argument: information decay is inevitable without deliberate design at source.
Why this is a Decision Intelligence problem
Decision Intelligence is a discipline that sits at the intersection of data, risk, and human judgement. Its central proposition is straightforward: the value of information isn’t in its volume or its accuracy in isolation, but in its ability to improve a decision at the moment it needs to be made. A perfectly accurate risk assessment delivered too late, to the wrong person, in a format they can’t act on, has failed — regardless of its analytical quality.
Most organisations treat data, risk management, and decision-making as separate functions. Project teams and functions produce outputs. Risk teams produce registers. Decision-makers make decisions — often working around the formal information structures rather than through them, because experience has taught them the formal structures are too slow, too noisy, or too disconnected from the actual choices in front of them.
Decision Intelligence challenges that separation. It asks: what would it look like if information were designed from the decision backward? If the starting point were not “what do we know?” but “what do we need to decide, and what information would actually change that decision?” The MVS is one answer to that question, applied specifically to risk.
The value of information is not its volume or its accuracy in isolation — it is its ability to improve a decision at the moment it needs to be made.
This matters particularly in major programmes and infrastructure projects, where the volume of risk information generated is enormous and the decision windows are often narrow. The challenge is never a shortage of data. It’s almost always a shortage of the right signal, at the right moment, in a form the right person can use. Organisations invest heavily in risk identification and quantification, and comparatively little in the question of how that information reaches a decision and what happens when it does.
Decision Intelligence treats that gap as the discipline. Not the modelling, not the register, not the reporting framework — but the connective tissue between knowing and deciding. The MVS is part of that connective tissue. It’s the mechanism by which analytical work becomes decision support rather than record-keeping.
The implication for how risk functions are designed and evaluated is significant. If the measure of a good risk report is completeness, teams optimise for completeness. If the measure is whether the right decision was made at the right time with the right information, teams optimise for something entirely different.
Decision Intelligence proposes the second measure — and the MVS is one of the practical tools for getting there.
Working with Kaleido
The gap described in this article is the gap Kaleido was built to close.
We work with leaders and project teams across infrastructure, energy, and defence to bring Decision Intelligence into the way programmes are run. That means helping organisations frame the right problems before committing to answers, build investment cases that are honest about uncertainty, and put the analytical and governance structures in place that allow consequential choices to be made with clarity rather than momentum.
Our work spans strategic advisory, integrated risk and cost modelling, and digital programme controls — not as separate offerings, but as connected capabilities that serve a single purpose: ensuring that the decisions at the heart of a programme are as well-founded as the assets they produce.
If any of what this article describes feels familiar, we would be glad to talk.