Why infrastructure projects need decision intelligence, not just better controls — and how the loops that drive underperformance can be changed.
Deepak Mistry · Head of Strategic Advisory · Kaleido Projects
Overview
Infrastructure projects are usually described in terms of cost, schedule, scope, risk and benefits. But underneath every performance failure is something more fundamental: a decision. Major projects aren’t shaped by one big decision. They’re shaped by thousands made over time, often under pressure and with incomplete information.
This article argues that improving infrastructure outcomes requires treating projects as decision systems — not just delivery systems. It examines the reinforcing loops that drive underperformance, introduces decision intelligence as the discipline that connects evidence to action, and offers a practical framework for making major project choices more consciously and more accountably.
Infrastructure projects are usually described in terms of cost, schedule, scope, risk and benefits. These are the right categories. They are the language through which performance is reported, challenged and governed.
But underneath every cost movement, schedule delay, scope change or risk exposure is something more basic: a decision.
A decision to approve a design before it was ready. A decision to start works before information was mature. A decision to release contingency. A decision to accept a risk quietly rather than escalate it. A decision to hold the programme together with optimism long after the evidence stopped supporting it.
Major projects aren’t shaped by one big decision. They’re shaped by thousands of decisions made over time, often under pressure and with incomplete information. Some are formal. Many aren’t. Some are deliberate. Others are embedded in behaviours, meeting dynamics, assumptions that go unchallenged, and trade-offs that never get named.
This means that a project’s performance isn’t only the result of how well it is planned or controlled. It’s also the accumulated result of how well it decides.
To improve infrastructure outcomes, we need to stop treating projects only as delivery systems and start treating them as decision systems.
More control isn’t the same as better decisions
When a project starts to struggle, the response is usually predictable. More reporting is requested. More dashboards are created. Governance meetings become more frequent. Risk registers are reviewed. Assurance activity increases. Plans are re-baselined.
All of this has value. Projects need controls. They need visibility, governance and reliable information.
But here’s the difficulty. Better information doesn’t automatically produce better decisions. A dashboard can show that a project is under pressure without helping leaders understand what choices are still available. A risk register can document threats without changing how risk is acted upon. A governance meeting can approve a paper without properly testing whether the decision behind it is sound. A report can describe uncertainty while the project continues to behave as if the future is certain.
The instinct to add more controls is understandable. But it often rests on a false assumption: that the problem is insufficient information rather than how information is connected to decisions. These are different problems. They require different responses.
The first leads to more reporting. The second leads to decision intelligence.
Projects behave like systems
Infrastructure projects are complex systems. They involve many organisations, contracts, disciplines, interfaces, approvals, communities and political expectations. Decisions don’t happen in isolation. They’re shaped by incentives, relationships, behaviours and feedback loops.
Consider a familiar pattern. A project is under schedule pressure. To maintain momentum, leaders approve work before the design is sufficiently mature. Activity increases. Milestones appear to be protected. Confidence may even improve in the short term.
But later, unresolved design issues surface. Interfaces are missed. Rework accumulates. Claims emerge. Costs rise. The schedule comes under even more pressure. That pressure then creates more incentive to make further premature decisions.
The Schedule Loop
The Cost Loop
The Reporting Loop
The Commercial Loop
The Governance Loop
Which of these loops are you carrying?
Tick any patterns you recognise from your current programme.
The Schedule LoopPressure leads to premature decisions, which create rework, which creates more pressure.
The Cost LoopCost pressure reduces early investigation, increasing uncertainty, which creates greater cost pressure.
The Reporting LoopOptimistic reporting delays escalation, reduces options, and makes later reporting more defensive.
The Commercial LoopCommercial tension reduces transparency, which creates late surprises, which increases tension.
The Governance LoopPressure to present certainty hides uncertainty, making governance less able to intervene early.
Tick the patterns you recognise. Your pattern will appear here.
In each case, the visible problem is only the surface. The deeper issue is the system of decisions, behaviours and relationships that keeps producing the same result.
These loops persist not because projects lack information, but because they lack a consistent discipline around the decisions that sit inside those loops. Schedule pressure produces premature decisions because the question are we ready to decide? is never formally asked. Optimistic reporting persists because nobody is accountable for naming the assumptions behind a forecast. Commercial tension reduces transparency because decisions about what to share are made instinctively, not deliberately. Governance loses its grip because the quality of what’s presented is never properly challenged.
Why this is a relational problem, not just a process one
There’s a line that comes up regularly in post-project reviews. The information was available. It just didn’t reach the right people in time, in the right form, with sufficient honesty.
That’s not a process failure. It’s a relational one.
On major programmes, the quality of decisions is shaped by whether people are willing to surface uncertainty early, share bad news before it compounds, discuss options before positions harden, and treat risk as a shared project issue rather than a contractual weapon. These behaviours aren’t guaranteed by having a risk register or a governance framework. They emerge from — or are suppressed by — the quality of relationships between the organisations and individuals involved.
When relationships are defensive or fragmented, the decision environment deteriorates. People escalate late. Risks get softened in the telling. Assumptions go untested because testing them would be uncomfortable. Governance receives a partial version of reality, often presented in the most favourable light available.
When relationships are stronger, the dynamic changes. Teams surface problems earlier because they trust that doing so won’t be punished. Options are explored more honestly. Assurance becomes a source of learning rather than a late-stage hurdle. Project controls become part of decision support, not just performance reporting.
This is why relationship quality isn’t a soft issue. On major infrastructure projects, it’s part of the decision infrastructure.
Governance as a test, not a theatre
Much of what passes for project governance focuses on process compliance — whether the right paper was submitted, whether the right forum approved it, whether the right box was ticked.
This matters. But it isn’t sufficient. A governance process can be technically correct while adding little or no value to the quality of the decisions it approves.
The real test of governance isn’t whether a decision was approved through the right forum. It’s whether the forum improved the quality of the decision.
Did it clarify the real choice? Did it expose weak assumptions? Did it compare options? Did it make uncertainty visible? Did it test whether risks were understood and owned? Did it connect the decision to outcomes and benefits? Did it create clear follow-through and accountability?
If governance does these things, it becomes part of the project’s intelligence system. If it doesn’t, it becomes theatre: a process that creates the appearance of control while leaving the decisions that actually shape performance largely untouched.
What this looks like in practice
Consider a project facing pressure to begin construction. The programme is politically visible. The team wants to demonstrate progress. The design isn’t fully mature, but there’s confidence — expressed with varying degrees of conviction by different people in the room — that outstanding issues can be resolved during delivery.
The conventional framing
The decision is framed narrowly: can we start works now? The yes-or-no answer tends to follow the dominant pressure in the room. Political urgency beats design maturity. Confidence beats evidence. The decision gets made, but the assumptions behind it are never properly named, and the risks are never clearly owned.
A decision-intelligent approach would frame the question differently. Not whether to start construction, but whether to accept a defined level of design maturity risk — with all that implies for cost, schedule, safety, claims and future optionality.
What options genuinely exist? Proceed in full. Defer. Resequence. Start only enabling works. Narrow the scope. Increase contingency. Strengthen interface controls. Apply decision gates by design package. The full list is rarely written down. It’s rarely even discussed.
What assumptions must be true for this to work? That outstanding design issues are minor and resolvable quickly. That interfaces are well understood. That the contractor can absorb late change. That contingency is sufficient. That approvals won’t create further delays. Each of these should be tested explicitly, not assumed collectively.
None of this means the project should always wait. Sometimes proceeding under uncertainty is the right call. The aim isn’t to slow projects down. It’s to prevent false speed: the appearance of progress that creates greater delay, cost and conflict further down the line.
Decision Intelligence: The layer that connects everything else
Decision intelligence is the discipline of improving how important decisions are framed, informed, governed, made and learned from. On a complex infrastructure project, that discipline provides a practical bridge between systems thinking and delivery performance. It doesn’t replace project controls, risk management, assurance or governance — it changes the quality of what happens inside them, by making the decision itself the unit of focus rather than the information surrounding it.
It helps leaders move beyond asking what does the data say? and towards better questions:
- What decision are we actually making?
- What outcomes, benefits or commitments does this decision affect?
- What options are still genuinely available?
- What evidence supports each option, and where does it come from?
- What assumptions are we relying on — and what happens if they are wrong?
- What risks and uncertainties surround this decision?
- Are we ready to decide, or are we simply under pressure to give an answer?
These questions do specific work. What decision are we actually making? interrupts the tendency to answer a narrower or easier version of the real question. What options are still genuinely available? challenges the momentum that drives premature commitment. What assumptions are we relying on? surfaces the hidden fragility in plans that look more certain than they are. Are we ready to decide? creates a deliberate pause before the schedule loop runs — or before the governance loop accepts a paper it should have challenged.
Decision intelligence isn’t another dashboard. It’s the layer that connects the disciplines projects already have — evidence to assumptions, assumptions to risks, risks to options, options to decisions, decisions to actions, actions to outcomes, outcomes to learning. Without this connected thread, projects can become very capable at producing information while still making poor choices.
Decision Readiness
Not all decisions are equal — and not all decisions are ready to be made. The pressure that drives reinforcing loops also drives premature commitment: the feeling that a decision must be reached before the analysis is complete, the options are understood, or the assumptions behind the preferred option have been tested.
Decision readiness isn’t about perfection. It isn’t about eliminating uncertainty — all major infrastructure decisions are made under uncertainty, and waiting for certainty that never arrives is its own kind of failure. It’s about being conscious of the gaps before committing: knowing what you know, knowing what you’re assuming, and knowing what you don’t yet know.
The eight questions below form a practical framework for assessing whether a decision is ready to make. They’re drawn from the same logic as the reinforcing loops described earlier in this article — each question is designed to surface the kind of fragility that those loops exploit. Use the assessment as a prompt before a major decision goes to governance, or as a retrospective lens on decisions that didn’t land the way they were intended.
Decision Readiness Assessment — Eight Questions
Use the guidance under each heading to rate your current position. Your readiness assessment will appear once all eight are rated.
This tool is simply for illustrative purposes, not intended to be a comprehensive assessment.
01 · The Choice
▲ Strong: The decision is clearly defined and distinct. Everyone involved would describe it the same way. ◆ Partial: Understood informally but not written down or tested for shared understanding. ▼ Weak: Framed as a binary, conflated with adjacent decisions, or described differently by different stakeholders.
02 · The Outcomes
▲ Strong: Explicitly connected to named outcomes and programme commitments. Trade-offs are understood. ◆ Partial: Outcomes referenced but not formally mapped. Some commitments may be affected but unconsidered. ▼ Weak: Focus is on delivery milestones. Benefits and commitments haven’t been considered.
★ Critical dimension
03 · The Options
▲ Strong: Multiple options developed in enough detail to compare, including pause, defer and resequence. ◆ Partial: More than one option exists but alternatives haven’t been properly developed. ▼ Weak: There is effectively one option. The question is how to implement it, not whether to.
04 · The Evidence
▲ Strong: Clearly sourced and independently verified. The team can distinguish what is known from what is assumed. ◆ Partial: Good data in some areas but gaps elsewhere. Not all evidence independently challenged. ▼ Weak: Largely internal and self-generated. Little independent verification or challenge.
★ Critical dimension
05 · The Assumptions
▲ Strong: Key assumptions explicitly named, written down, and tested. Ownership of each is clear. ◆ Partial: Understood informally but not systematically named or tested. Some remain unexamined. ▼ Weak: Assumptions are embedded in the plan rather than surfaced. They haven’t been named or tested.
06 · The Uncertainty
▲ Strong: A range of outcomes has been considered. The decision is robust across that range, or contingency is calibrated accordingly. ◆ Partial: Uncertainty acknowledged but the plan reflects a single scenario. Limited sensitivity testing done. ▼ Weak: Uncertainty not addressed. The plan is single-point and treats the future as certain.
07 · The Risks & Opportunities
▲ Strong: Risks identified, owned, and directly connected to this decision. Opportunities also considered. ◆ Partial: Risks documented but may not be directly connected to this decision. Ownership unclear in places. ▼ Weak: Risks exist in a register but haven’t been connected to this decision. Ownership unclear or contested.
08 · The Follow-Through
▲ Strong: Clear actions, owners and timelines follow. A review mechanism exists to assess whether the intended outcome is achieved. ◆ Partial: Actions identified but ownership or timing unclear. No formal review mechanism in place. ▼ Weak: The decision will be made without a clear mechanism to track what happens next or learn from the outcome.
Completing and recording this assessment creates a traceable thread from evidence to decision to outcome. It helps governance bodies focus on the quality of the decision rather than simply the quality of the paper. And it creates the institutional memory that most projects lack: a clear account of what was known, what was assumed, what was decided, and what happened next.
Breaking the Loop
The reinforcing loops described in this article aren’t inevitable. They are patterns — and patterns can change. The same feedback mechanism that drives underperformance can, with different inputs, drive improvement.
Decision intelligence creates the conditions for a different kind of loop. When assumptions are surfaced before they become problems, less fragility gets built into plans unexamined. When options are genuinely compared rather than presented as a formality, premature commitment becomes rarer. When governance consistently tests rather than approves, teams learn that the quality of evidence matters — and bring better evidence. When follow-through is built into every significant decision, outcomes get reviewed, learning gets embedded, and the next decision benefits from the last.
This is what it looks like in practice to shift from a decision-reactive programme to a decision-intelligent one: not dramatic transformation, but the gradual replacement of destructive loops with corrective ones. Pressure becomes a prompt to examine options rather than abandon them. Uncertainty becomes something to be named and owned rather than hidden in a point-estimate plan. Governance becomes a genuine test of decision quality rather than a process to be navigated.
It doesn’t happen all at once. The relational conditions need to exist — the trust, the honesty, the shared language. The governance structures need to support it. It requires sustained commitment from leaders willing to ask harder questions and accept more uncomfortable answers than they might otherwise receive.
But the starting point is always the same: a decision made more consciously than the last one.
Better outcomes come from better decision systems
Major projects don’t fail only because people lack data. They fail because evidence, assumptions, risks, relationships and behaviours aren’t connected — early enough, honestly enough — around the decisions that matter.
More controls can help. Better data can help. Stronger governance architecture can help. But none of these things improves performance unless they change the quality of the decisions being made.
A decision-intelligent project turns systems thinking into practical governance. It makes uncertainty discussable. It connects technical, commercial, stakeholder and delivery evidence. It improves the conditions in which people work together. It creates a clearer line between what was known, what was assumed, what was decided and what happened as a result.
The test of any project intervention isn’t whether it creates more information. It’s whether it changes the relationships, behaviours and decisions that determine what the project will keep producing over time. Better projects need better decision systems.
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, nuclear and defence to bring Decision Intelligence into the way programmes are run. That means helping organisations understand the reinforcing loops that drive performance, frame the right problems before committing to answers, and put the 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. kteam@kaleidoprojects.co.uk