The Water Notice in Small Print

A town's water department planned to replace household meters with connected devices. Engineer Mila wrote a notice explaining remote readings and faster identification of unusual usage. The communications team reduced it to a cheerful leaflet. Details about how frequently readings would be collected moved to tiny text at the bottom, beside the installation company's logo.

During a public session, a resident asked whether hourly readings might reveal when a home was empty. Mila answered that patterns could suggest occupancy, although the department did not need to make that inference. The resident then asked why readings had to be hourly if bills were issued quarterly. Mila realised she had repeated the supplier's default setting without examining the department's actual purpose.

Frequent readings could help detect certain problems earlier, but storing them indefinitely was harder to justify. Mila proposed keeping detailed readings briefly for operational checks and retaining broader totals for billing. The supplier could support this, though configuring it would cost more. The finance team wanted to know why privacy had become an unexpected expense so late in the project.

Mila accepted responsibility for raising the issue late and revised the plan before installation began. The new leaflet stated the collection frequency and retention periods in ordinary print. Not every resident was satisfied, and several chose to request further information. Mila attended the next session with the complete technical settings rather than another slogan. She was still convinced that connected meters could be useful. She was less willing to treat usefulness as a complete explanation of how they should operate.