Risk professionals spend a lot of time thinking about the future. What might happen. When it might happen. How bad it might be, how likely, how manageable. There’s a certain discipline to that kind of thinking — a trained willingness to sit with uncertainty, to hold multiple possible futures simultaneously, to resist the comfort of false confidence.
What I’ve found, having spent the better part of my career inside major infrastructure programmes, is that the hardest part of the job has never really been about the future. It’s been about the present — specifically, about the quality of attention that gets paid to decisions in the moment they’re being made. Whether the people making them feel the weight of what they’re deciding. Whether the environment around them supports that or quietly works against it.
The thing that shapes that environment, more than anything else I’ve observed, is time. Not the lack of it — though that’s real enough. Something more structural. Something about what major programmes do to people’s relationship with time, with consequence, and with the decisions that connect the two.
You make a decision on a Tuesday afternoon. A reasonable one, based on the information you have. You write it up, it gets minuted, life moves on. And then you realise — not all at once, but gradually — that the consequences of that decision won’t be visible for three years. Maybe five. By then you’ll be somewhere else, the team will have changed, and nobody will remember the Tuesday afternoon. This is the quiet strangeness of working inside a megaproject. The gap between action and consequence is so wide that the normal feedback loops that tell us whether we’re getting things right simply don’t close.
when time bends
Megaprojects do something strange to time. They compress it in some places and stretch it almost beyond recognition in others — often simultaneously, often within the same week.
The compression is familiar to anyone who’s worked on a major programme. The gate review creates a gravitational pull. Everything bends toward it. Teams that were drifting suddenly have direction. Decisions that had been circling for weeks get made. There’s a friction to it that, briefly, gets things done. And then the review passes, the pressure releases, and the drift resumes.
The stretching is less visible but more consequential. A design decision made in the early stages of a programme will shape what’s possible several years down the line. A procurement choice will constrain options that haven’t even been imagined yet. These decisions don’t feel weighty in the moment — they’re made in meetings, between other meetings, by people under pressure to move on to the next thing. Their consequences live in a future that nobody in the room will fully inhabit.
This is the distortion. What feels pressing and what is consequential are rarely the same list. The distance between them is where most programmes quietly lose their way.
busy isn’t the same as consequential
I’ve watched highly capable people work themselves to exhaustion preparing for a review that, in retrospect, changed nothing. The decisions had already been made. The direction was already set. The review was a reporting event dressed as a decision point, and everyone in the room knew it — but the preparation happened anyway, because that’s what the programme expected.
Meanwhile, somewhere else in the same organisation, a decision that genuinely mattered was being made quietly, with insufficient time, by people who were too busy preparing for the review to give it the attention it deserved.
This is what manufactured urgency does. It doesn’t just waste energy — it displaces it. The gravitational pull of the visible deadline draws resources, attention, and political will away from the things that are actually shaping the outcome. And because the schedule rewards hitting milestones rather than making good decisions, the displacement goes largely unnoticed. You can have a programme that consistently meets its review dates and consistently makes poor consequential decisions. The two are not as connected as the governance framework implies.
Real urgency, by contrast, is quiet. It doesn’t announce itself. It accumulates in the margins of other conversations, in the risks that stay amber for too long, in the assumptions that everyone has quietly stopped believing but nobody has formally challenged. By the time it becomes visible, it’s usually too late to do much about it cheaply.
whose clock is driving this decision
One of the more disorienting experiences of working across different levels of a major programme is the realisation that people are not just doing different jobs — they’re inhabiting different versions of time.
- The person in the ministerial meeting is thinking about what can be announced before the next election.
- The person running the programme is thinking about what needs to be true for the next business case approval.
- The person managing the package is thinking about this month’s progress report.
- The contractor’s commercial team is thinking about the variation they submitted three months ago and haven’t heard back on.
All of them are nominally working toward the same outcome. In practice, they’re each solving a different problem on a different timescale, and those problems don’t always point in the same direction.
What makes this more than just an interesting observation is what it does to decision-making. A decision that looks sensible through one timescale can look reckless through another. Accelerating a milestone to meet a political deadline looks like responsiveness from above and like manufactured risk from below. Slowing down to resolve a technical issue looks like prudence from the delivery team and like delay from the programme board. Neither reading is wrong. They’re just looking at different parts of the elephant, on different timescales, with different consequences in mind.
The programmes that handle this well are the ones that make the misalignment visible rather than pretending it doesn’t exist. They create the conditions for an honest conversation about whose clock is driving a given decision — and what the cost of that is for everyone else on a different clock.
when next Friday beats year four every time
There’s a particular kind of meeting that happens on major programmes. Someone raises a concern — a technical risk, an interface issue, an assumption in the baseline that may not hold. It’s a legitimate concern. It gets discussed. And then, because there’s no immediate consequence visible, because the risk is real but distant, because there are more pressing things on the agenda, it gets noted and moved past. It will be revisited. It isn’t.
This happens not because the people in the room are careless or incompetent. It happens because the human mind is genuinely poor at weighting distant consequences against immediate ones. The risk that will materialise in a year or two competes for attention with the deliverable due next Friday, and next Friday wins. Not through any deliberate calculation — just through the ordinary operation of how attention and priority work when you’re busy and the future is abstract.
Megaprojects don’t just expose this limitation — they systematically amplify it. The longer the programme, the wider the gap between decision and consequence. The wider the gap, the harder it is to maintain the sense of stakes that keeps judgement sharp. And the harder it is to maintain that sense of stakes, the more likely that consequential decisions get made with insufficient care, by people whose attention is elsewhere, on timescales that don’t reflect the true weight of what’s being decided.
The result is a consistent pattern. Not dramatic failures of judgement — those are rare and usually visible. Quiet, incremental degradations of decision quality, accumulating across hundreds of small moments, in dozens of workstreams, over years. By the time the consequences arrive, the decisions that caused them are buried so deep in the programme’s history that drawing the line is almost impossible.
what long programmes do to the people inside them
There’s something nobody tells you about working on programmes that span years of your career. The work gets inside you in ways that shorter projects don’t. Not just professionally — the way you think about time, consequence, and effort starts to shift in ways that are difficult to articulate and easy to underestimate.
The best version of this is a kind of expanded patience. You learn to hold complexity without needing to resolve it immediately. You become more comfortable with ambiguity, more capable of sustaining attention across long arcs, more honest about what can and can’t be known at any given moment. These are genuinely valuable qualities, and long programmes can produce them in people who are paying attention.
The harder version is a kind of progressive detachment. The programme is so large, its consequences so diffuse, its timeline so extended, that the emotional connection between your work and its meaning starts to thin. You stop feeling the weight of the decisions because the feedback never comes. You stop pushing back as hard because you’ve learned that the thing moves slowly regardless. You become, without quite noticing, a person who processes rather than decides — who manages the work rather than shapes it.
I don’t think this is weakness. I think it’s what happens to most people, most of the time, inside systems that are genuinely too large for any individual to fully comprehend. The question worth asking — the one most programmes never ask — is what conditions allow people to stay galvanised rather than become numbed. What keeps the thread visible. What maintains the connection between the Tuesday afternoon decision and the consequence it will eventually produce.
the discipline that no schedule can teach
There’s a version of this piece that ends with a list of recommendations. Better feedback loops. More honest governance. Explicit conversations about timescale misalignment. All of that is true and none of it is wrong. But I don’t think it’s quite the point.
The deeper thing that megaprojects teach you — if you let them — is something about the relationship between action and meaning across time. Most of the work we do in the world has relatively fast feedback. We can tell, more or less, whether we’re getting it right. We adjust. We improve. Our judgement sharpens through contact with consequence. Working inside a programme that spans decades removes that luxury almost entirely. You act, and the consequences travel forward without you.
Living with that honestly requires a different kind of discipline than most professional environments demand. Not the discipline of the schedule — that’s easy, comparatively. The discipline of caring about decisions whose consequences you won’t see. Of maintaining the thread between the Tuesday afternoon and the three years hence, even when the programme gives you every reason to let it go. Of staying galvanised when the easier, more rational response to the environment is to become numb.
I don’t think this is something that can be fully taught or trained. It’s something you either develop — through experience, through reflection, through the accumulation of enough Tuesday afternoons to start taking them seriously — or you don’t. But I do think it can be encouraged. By leaders who model it. By programmes that create space for it. By a culture that treats the quality of consequential decisions as something worth measuring, not just the speed at which milestones are hit.
what you can actually do about it
None of what’s been described here is inevitable. It’s predictable — which is different. Predictable problems can be designed against. The question is whether the people with the authority to do so choose to.
There are five things that, in my experience, make a genuine difference.
1name the timescale misalignment openly. Not in an away-day exercise — in the actual decision-making room. Whose clock is driving this? What does it cost the people on different clocks? Making that question a normal part of programme governance changes the conversation more than most structural reforms.
2create explicit decision reviews, not progress reviews. Moments specifically designed to ask: what consequential decisions have we made in the last month, were they given the attention they deserved, and do any of them need revisiting? Most programmes have no equivalent of this. They review progress obsessively and decisions almost never.
3protect the people who raise distant risks. The meeting where the concern gets noted and moved past is so common partly because people learn that raising uncomfortable long-range issues doesn’t change anything and sometimes creates friction. That’s a culture problem, and culture is set by what senior people visibly reward and visibly tolerate.
4be honest about what manufactured urgency is costing you. If your team is regularly exhausted by preparation for reviews that don’t change decisions, that’s not just a morale issue — it’s a decision quality issue. The energy spent on the review is energy not spent on the things that matter. Naming that cost explicitly is the first step to doing something about it.
5build in the feedback loops the programme won’t naturally create. Find ways to revisit past decisions and understand what they produced. Not to assign blame, but to sharpen judgement. The calibration that short-cycle work produces automatically has to be deliberately constructed in a long programme. It won’t happen by itself.
The trains that run today were designed by people who in many cases never rode them. The cables that carry power were specified by engineers who retired before they were energised. The infrastructure that shapes how millions of people move through the world was built on decisions made in rooms that no longer exist, by people who couldn’t fully see what they were building toward.
That’s not a reason for humility alone — it’s a reason for a certain kind of ambition. To make the Tuesday afternoon decision as though it matters. Because it does. Even when nobody will remember it.
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.