I once asked a technician, on a site visit that had nothing to do with him specifically, how long he had worked there. Eleven years, he said. I asked what he was proudest of. He thought about it for a while, longer than the question should have required, and said, "Honestly? That most days, nobody has to know I exist." He didn't say it bitterly. He said it like a fact he had made peace with a long time ago. I found I couldn't stop thinking about it.

Every organisation runs on two kinds of work. One kind is visible, it gets measured, presented, celebrated at the end of the year. The other kind is only noticeable in its absence. Done well, it produces nothing anyone particularly registers: systems keep running, buildings stay operational, nothing breaks. It is a strange feature of organisational life that this second kind of work. Often the work everything else quietly depends on, tends to earn attention only at the exact moment it fails.

We have seen this pattern often enough across engagements to trust it as more than a coincidence. Recognition systems, left undesigned, default to visibility, and visibility defaults to crisis. The clearest sign is almost always the same: when you ask people in these roles what communication from leadership actually looks like, the honest answer is that it arrives almost exclusively as a problem to be solved. Over years, in the absence of anything else, that silence quietly becomes a message of its own, not about competence, but about whether the work, and the person doing it, matters at all outside a crisis.

We saw this clearly with a large organisation whose distributed technical workforce kept physical infrastructure running across dozens of sites. The engagement began as a retention question, capable, experienced people were leaving roles that were, by most external measures, secure and fairly paid. Exit conversations hadn't produced a clear answer; nobody pointed to pay, nobody described the work as unmanageable.