A featured contribution from Leadership Perspectives: a curated forum reserved for leaders nominated by our subscribers and vetted by our Environmental Business Review Advisory Board.

San Jose Water

Suzanne DeLorenzo, PhD, Director of Water Quality

Why Risk Communication Belongs on the Schematic

Suzanne DeLorenzo

Suzanne DeLorenzo

Public Trust Advocate

Spend enough years around water treatment and you start to see the world in barriers. We never trust a single step, so we layer them — coagulation, then filtration, then disinfection — so that if one has a bad day, the next is there to catch it. We design each one around the ways it might fail, watch for the first sign of trouble, and maintain it before anything goes wrong.

That discipline is why a glass of tap water is usually unremarkable. In my work, unremarkable is success.

But there’s one barrier I almost never see on the schematic. It sits past treatment, past the last sample point, past the moment the water leaves our hands. It’s where a technically correct result becomes something a real person has to understand and use.

I think of it as the communication barrier.

When it fails, we tend to blame the day: an anxious customer, a confusing headline, or a reporter on a deadline. But those are the conditions we’re working in, not the root cause. If communication is truly part of protecting public health, then we owe its failures the same seriousness we’d give any failure in the plant.

Some failures start with the information itself. A report can be technically accurate and still leave someone with the wrong idea. Source-water monitoring, treatment results, and delivered water answer three different questions. Put them side by side without explaining the distinction, and a customer may reasonably conclude that anything detected anywhere in the system came out of their tap.

We may have followed every reporting requirement and still failed to communicate what the result meant.

The fix isn’t to say less. It’s to say it better: the number, the context and the practical meaning presented together. A result should never have to explain itself.

The other failures are just as predictable. Go quiet, and someone else fills the silence, usually with something less accurate. Reach for jargon, and a true answer starts to sound like a dodge. Reassure before you’ve listened, and people feel handled. Say slightly different things from three corners of the utility, and ordinary uncertainty starts to look like concealment. That’s not bad luck. It’s just how this barrier breaks.

The operational responsibility does not end when the water leaves the plant.

Like every barrier, it needs monitoring. We wouldn’t wait for filter breakthrough before checking turbidity. Communication has leading indicators too: questions stacking up at the call center, a cluster of complaints from one pressure zone, the same worried phrase at three community meetings. Those aren’t interruptions to the real work. They’re the instrument telling us where the barrier is getting thin.

It also needs redundancy. A critical message should not depend on one expert being available. Operations, water quality, customer service, communications and leadership should work from the same facts and the same plain-language explanation, so a customer lands on the same answer no matter which way they reach us. The partners we lean on outside the utility, health officials, community organizations, should know the story before the hard day, not meet it in the middle of one.

Finally, the barrier needs maintenance. That work is mostly invisible: drafting templates, testing language on people who did not write it, deciding who speaks, and updating materials as the science changes. It’s easy to postpone because nothing appears broken until a crisis makes the neglect visible all at once. A simple boil-water FAQ is the clearest example I have. It’s built from fifteen years of the same questions, nearly every worry a customer has ever brought me during an event, answered in one place and ready to publish the moment a notice goes out. The work happened on the quiet days, so the page is already there on the loud ones.

You can’t build it in the middle of the emergency, any more than you’d rebuild a filter while it’s in service. In the moment, the most useful response is usually straightforward: say what we know, admit what we don’t, explain what we’re doing, and tell people when they’ll hear from us next. But even the clearest message won’t hold if the system carrying it was never kept up.

The operational responsibility does not end when the water leaves the plant. It continues where water quality becomes public understanding. Customers may never see us optimize a coagulant dose or calibrate an analyzer. They see what we tell them, when we tell them, and whether our answer helps.

The last barrier is the one between a sound result and a person who can trust what it means. We have been relying on it all along. It’s time we put it on the schematic and gave it the same care as everything upstream.

The articles from these contributors are based on their personal expertise and viewpoints, and do not necessarily reflect the opinions of their employers or affiliated organizations.