The Story People Tell When Nobody Introduces Themselves

I sometimes wait for my neighbours to go back inside before I take the bins out.

Not because I dislike them, and not because anything is wrong. Sometimes I just cannot be bothered with the interaction.

I just want to complete the mission.

And I have been thinking recently that infrastructure and community can end up in a similar kind of relationship. It isn’t always hostile or malicious; it is just distant enough for assumption to fill the gap.

Because when people do not really know each other, they tend to borrow a version of each other from somewhere else. The operator becomes the villain. The contractor becomes the one who arrives, fixes, builds, and disappears. And “the community” becomes a vague category of people assumed to be resistant, emotional, uninformed, or somehow difficult by default.

None of those descriptions are accurate enough to hold the truth. That is part of the problem.

Community engagement often begins at the point where pressure has already arrived, a planning issue, a concern, a complaint, or a sudden public meeting. By then, the story has often already formed on both sides, and once assumption hardens, everything gets harder.

What has struck me in some of these conversations is how often “the community” is spoken about as though it means people with less intelligence, less context, or less right to question. As though local residents are there to be managed, reassured, or corrected, rather than engaged as intelligent adults with a legitimate stake in what is happening around them.

I think that assumption does more damage than people realise. The issue has never really been that communities are incapable of understanding infrastructure. More often, they have simply not been invited into the conversation in a way that respects their intelligence.

At the same time, the assumptions do not only travel in one direction. People in and around communities can also speak about operators, owners, and contractors as though they are automatically extractive, secretive, indifferent, or fair game for whatever frustration needs somewhere to land.

And sometimes there is a strange asymmetry in those conversations. People rightly ask difficult questions about water, energy, land, and impact. They should. But occasionally those questions also reveal how distant most of us are from our own systems of use and dependence. It is easier to scrutinise a building than to examine the infrastructure quietly sustaining our own lives.

That is not hypocrisy so much as a reminder of how invisible infrastructure has become.

And perhaps that is why the starting point matters so much. Because if people only meet each other when there is pressure, they are not meeting as people; they are meeting as symbols. The resident becomes “the objector.” The operator becomes “the corporation.” The contractor becomes “the disruption.” And the actual human beings disappear behind the role they have been assigned.

I think this is one of the reasons story matters more than people assume. Not because story makes infrastructure fluffy, but because story gives people somewhere human to meet before assumption takes over.

Language matters too, as does tone and who is actually in the room. There is a profound difference between engaging people through those who understand a place from within, and trying to interpret a community from a polite, corporate distance.

Because community is not a category. It is not a comms challenge. It is not a faceless group of “locals.” It is people, intelligent, complicated, varied people. Some informed, some not. Some generous, some difficult, and most somewhere in between.

Just like the people inside the industry.

Perhaps that is the point.

If people only meet each other when there is pressure, they are not really meeting at all. They are meeting through assumption, role, and distance.

So perhaps the work is simpler, and harder, than it sounds.

To start building understanding alongside infrastructure.