Trust is often treated as something that can be installed.
An organization changes leadership, announces a policy, redesigns its public face and explains what people should now expect. When trust doesn't follow, the obvious response is to improve the message. Explain the change more clearly. Demonstrate good intentions. Find better language for whatever the institution is trying to become.
Sometimes communication really is the problem.
Other times we're asking communication to carry something it can't carry by itself.
I can tell you that someone is trustworthy. I can explain why I trust them, introduce you personally and give you examples from twenty years of knowing them. All of that gives you information you didn't have before, and my own relationship with you may give the information additional weight.
What I can't give you is twenty years of having known them.
That distinction seems obvious between people, but it becomes easier to lose when we're talking about organizations. Reputation, credentials, policies, endorsements and branding can all provide evidence about what someone should expect. They can reduce uncertainty enough for a relationship to begin.
They aren't the relationship.
Trust develops through what happens afterward.
Someone says they'll do something and does it. Something goes wrong and we see how they respond. They make a mistake, acknowledge it and repair what they can. Or they avoid responsibility, change the story and leave somebody else carrying the cost.
One event rarely settles the matter. What accumulates is a history from which expectations become increasingly reasonable.
That's why repeated encounters matter so much. In a small town, a workplace, a business relationship or a long collaboration, today's behavior doesn't disappear when the interaction ends. There is likely to be another encounter, and both people may arrive carrying some memory of the previous one.
That changes the environment.
A business owner who mistreats a customer may encounter that customer at the grocery store next week. A newspaper that gets something wrong may hear about it from the person involved and then cover the same institution again six months later. Someone who makes a promise inside a long-running collaboration doesn't begin from zero the next time another promise is made.
The future gives the present consequences.
That doesn't automatically produce trust. Repeated interaction can produce distrust just as efficiently. A long history of broken promises is still a history.
What repetition provides is evidence.
This is one reason I think trust and familiarity are easy to confuse. Seeing someone repeatedly can make them feel familiar without making them reliable. Shared history can create loyalty that survives long after the evidence supporting it has changed. Communities can protect people who shouldn't be protected precisely because relationships are dense enough to discourage contradiction.
Proximity isn't virtue.
It simply makes certain kinds of feedback harder to avoid.
Distance changes the available evidence, but it doesn't eliminate it. I trust plenty of things built or operated by people I will never meet. I don't personally know the engineers who designed an aircraft before I board it, and I don't need a relationship with everyone involved in processing a payment before using a credit card.
Large systems developed other ways to carry evidence across distance.
Standards matter. Audits matter. Contracts matter. Professional reputations matter. Warranties, regulation, independent testing and a history of reliable operation can all make cooperation possible among strangers.
In some cases, the point of a good system is to reduce how much personal trust is required.
I don't need to trust a merchant's memory if I have a receipt. I don't need to trust that somebody will remember what we agreed to if the agreement is recorded. I don't need to know the person operating a remote server if the servi