Skip to content

Research & Insight

When nobody did anything wrong

← Back to Library

What Holds Us Together? Issue 2

I spent two days recently trying to confirm the cancellation of a service that never did what it promised. Four calls in, nobody had been rude and everyone was following the process. Each transfer added to an experience that kept getting worse, and nothing I was told matched what was actually happening to me. For each person I spoke to, this may have been one call handled correctly. From where they sat, nobody did anything wrong. I still came away trusting the company less than when I started.

When something goes wrong, a natural question for management is whether someone made a mistake. But what if everyone acted as they believed they should? What if each team met its own expectations and the experience still fell apart?

Human beings do not experience an organization as a collection of separate functions. We experience what happens to us. We connect one conversation to the next, compare what we were promised with what happened and draw conclusions about whether we can rely on the people involved.

In the first issue, I described a person at a junction in an unfamiliar building, choosing between the familiar route back and a sign pointing down a corridor they had never seen. That person is not responding only to the accuracy of the arrow. They are interpreting the sign through everything the environment has already told them and everything experience has taught them about whether guidance can be relied upon.

The same thing happens when we deal with an organization. Each interaction becomes part of our understanding of it. A reassuring conversation may change that understanding. Another unexplained transfer may confirm what we already feared.

Narrative is one of the ways we make those connections and draw meaning from experience. The stories involved are not limited to formal storytelling. They include the explanations we construct every day. This organization cares about people. Nobody here can help me. If I call again, I’ll have to start over.

Two people can encounter the same information and draw very different conclusions. Each is interpreting it through their own experiences and the stories they tell themselves about how the world works. Those stories shape what they expect, what they believe and whom they trust. An organization’s story enters that existing understanding. People may recognize something in it, question it or find that it conflicts with what experience has taught them.

When words and actions repeatedly diverge, people learn to trust the actions. But that gap does not always come from someone knowingly breaking a promise. It can emerge while everyone is doing what they believe their job requires.

One person answers the question they are responsible for. Another passes the file to the appropriate team. Someone else follows a policy intended to prevent mistakes. Each action makes sense on its own. Together, they leave a person repeating their story, waiting for an answer and wondering whether anyone is going to help.

This is difficult to see from within the organization. The call was handled, the file was passed on, the policy was followed. Measures of those individual steps can show that things are working. They tell us much less about what happens between those steps, or what it takes for someone to get through all of them.

The person dealing with the organization experiences those connections directly. They may not know why a file moved between departments, but they know they had to explain the same problem four times. They may not know which team owns the decision, but they know they still do not have an answer.

Asking people to walk us through what happened reveals what separate reports miss. What were they expecting? What did they understand from each conversation? Where did they have to repeat themselves? At what point did they stop believing someone would help?

One person’s account does not establish how often a problem occurs. It does give us something specific to investigate. We can look for the same experience in other accounts, examine where responsibility changes hands and test whether the process works as intended for the person using it.

That understanding also matters to the stories an organization tells. Narrative can help people understand a difficult process, see why a decision was made or know what to expect next. Sometimes a clearer explanation is exactly what is needed. But we need to understand the experience before deciding that communication is the answer.

A good story is not evidence of trustworthiness. If the experience contradicts it, the story gives people another promise to compare with what actually happens. If it reflects their experience and helps them make sense of it, it can build understanding and connection.

Where trust has been broken, explanation is not enough. Repair begins with acknowledgment, accountability and changed behaviour. In my case, one person finally took responsibility and followed through. That did not erase the frustration, but it did rebuild some trust.

An organization still needs to take responsibility for the experience, even when everyone followed the process. That means looking at what happened across the whole experience and what needs to change.

Sometimes distrust may be telling us something important about the system itself.

← Back to Library