When water decisions look ready before they are: The fog of decision in water
The meeting is scheduled, the report is ready, the recommendation is clear. The capital forecast has been updated and the approval path is known. Everything points toward a decision that is ready to be made, and that is exactly where the difficulty begins.
One of the harder risks in water and wastewater leadership is a decision that looks complete before anyone has tested whether the confidence around it is supported by evidence. The people at the table may be experienced and careful, the technical work sound, the need real, and the decision can still carry more certainty than the evidence beneath it will bear.
This is the fog of decision. It rarely looks like confusion or poor judgement; more often, it looks like progress. A project moves from analysis to approval, the preferred option settles into place, and a risk that was named once gets carried forward as though naming it were the same as managing it. The organization is moving, but that motion can obscure whether the decision will actually hold once conditions change.
We’ve seen it. For example, picture a pump station sized and approved for a new development. The engineering is sound and the need is real. The whole business case rests on growth that everyone at the table expects to arrive. Then the development stalls. The station is built, the money is spent, and for the next few years it moves a fraction of the flow it was designed to carry. Nobody made an error anyone could point to. The decision rested on an assumption about the future that was never tested as hard as the engineering was, and by the time that assumption gave way, the concrete was already in the ground.
This is not an argument for waiting until the information is perfect, because it never is. Infrastructure ages while the options are still being studied. Forecasts rest on growth that may not arrive, and costs move between the day you scope a project and the day you build it. Regulations shift, public expectations rise, and the most experienced operator on staff can walk hard-won knowledge out the door the week they retire. This is the normal setting for the work. The problem begins when the decision process itself makes that uncertainty look more settled than it is.
Some exposure is harder to see than a stalled development. Evidence that is current in one department is out of date in another. The operators often know where the system is becoming harder to hold together, while the people approving the work see only a summarized line in a risk table that rates the same problem "moderate." A trade-off gets worked out in the corridor and never stated plainly enough to reach the approving body. A project has a clear owner for delivery, and no one in particular owns the question of whether the decision still makes sense five years on. None of this makes the decision wrong. It marks where the decision should be tested before commitment, while there is still room to change course.
Some of the fog comes from the pressures around the decision rather than the decision itself. A funding deadline compresses judgement. A council timeline narrows what staff feel able to put forward, and an election on the horizon can make a sound option feel untouchable for reasons that have nothing to do with water. Pressures like these shape what the organization sees, what it is willing to say out loud, and what it is prepared to test.
The pattern shows up across very different decisions: a utility approving a major renewal program, or a council weighing whether to bring in a private operator. In each case the paperwork can be in good order while the confidence behind it still needs a closer look.
Underneath any major commitment sit three practical questions. Can the people involved see trouble early enough to do something about it? If the main assumptions turn out to be wrong, is there enough room left to adjust? And once the approval is signed and attention moves elsewhere, will someone still clearly own the outcome? That last one turns sharp the moment responsibility crosses a municipal boundary and it is no longer obvious who answers for the service. The questions are simple to ask and difficult to answer well, which is usually where the real work turns out to be. A risk register is only worth keeping if it changes what people decide. The same is true of a forecast, which earns its place once leaders can say what would make it unreliable. Ownership is harder still: naming an owner for delivery is the easy half, and the real test is whether that ownership survives the long stretch after approval, when budgets, contracts, departments and leadership may all have turned over.
None of this is a case for slowing decisions down as a matter of habit. Water leaders have real work to do and communities that depend on it continuing, with infrastructure to renew and growth to service, all on timelines that rarely wait. Testing a decision earns its keep by showing where the exposure sits while the organization can still act on the answer, before it is locked into a course it cannot easily leave.
A gap like this is worth finding early, because of what it tells you. A particular gap might mean that important evidence never reached the people who needed it. It might mean the confidence in the room rests almost entirely on one person's knowledge, or that a preferred option became the answer before anyone named the trade-off it carried. Sometimes it means the organization is well prepared to deliver the project and much less prepared for what happens if the conditions around it shift. Signals like these are easier to act on early than late. After approval, once money is committed and expectations are set, changing course carries a political and financial cost that a pre-commitment conversation does not.
This is also a more practical way to talk about resilience. Resilience usually comes up after something has already gone wrong, when leaders are asking how quickly service recovered and what the organization should learn for next time. Those questions matter, but they arrive late in the story. Resilience also lives much earlier, in the quality of the decision that set the course in the first place. A decision is more likely to hold when the people making it have tested the evidence under their confidence, named the assumption that matters most, kept some room to adjust, and made sure accountability does not evaporate the moment the meeting ends. None of that removes the uncertainty. It makes the uncertainty visible enough to manage, which is a different and more achievable goal.
Capable organizations make exposed decisions all the time, and the cause is seldom a shortage of effort, care or technical skill. It is usually that the decision environment never gets tested with the discipline routinely applied to the technical work. The asset gets reviewed, the budget gets reviewed, the compliance implications get reviewed, and the decision itself, the part that ties all of them together, often receives the least scrutiny of all.
That last part is where BlueVector Strategy works. We help get ready for the big water commitments in front of it, so that leaders can see where their confidence is well supported, where the evidence still needs checking, and where accountability has to be made clearer before approval rather than after.
Water decisions will always carry uncertainty; the work is too complex and the stakes too high for anything else. The practical aim is better judgement at the point of commitment, while the organization can still do something with what it finds.
