Trust Fractures: How We Surfaced What Was Really Happening
In my previous post, I shared the moment I realized something wasn’t right in our organization. Not because of a single dramatic failure, but because of a quiet, persistent dissonance between who we believed ourselves to be and what I was actually experiencing. For a long time, I assumed that dissonance was mine alone to carry. I assumed it was a reflection of my own exhaustion, my own sensitivity, or my own inability to cope with the demands of leadership in a growing company.
I was wrong.
When my colleague and I began meeting off-site, our early conversations were careful and exploratory. We didn’t begin by diagnosing problems or assigning blame. We began by comparing observations. Small things. Moments that felt off but were easy to dismiss in isolation. Interactions that lingered in memory longer than they should have. Situations where the outcome didn’t quite match the intention behind it.
At first, I spoke cautiously, anxious not to appear to be pointing fingers unfairly or just complaining to complain. I half-expected her to reassure me that everything was fine or to confirm my deeper fear that I was the problem. Instead, she recognized what I was describing immediately. Not every example was the same, but the underlying patterns were unmistakably familiar to her as well. She had seen hesitation where clarity should have existed. She had seen communication break down in subtle ways. She had felt the same quiet strain beneath the surface of an organization that was getting by… but it wasn’t thriving.
That realization didn’t fix anything overnight, but it changed how I understood what was happening. What had previously felt like personal failure began to reveal itself as something structural and shared. We weren’t dealing with isolated frustrations or personality conflicts. We were beginning to see the outline of trust fractures.
Trust Fractures Don’t Announce Themselves
Trust fractures rarely announce themselves dramatically. They don’t arrive in the form of betrayal or open conflict. More often, they appear as hesitation. A team member carefully editing an email, not to improve clarity but to avoid being misunderstood. A question left unasked because the person asking it isn’t sure how it will be received. A conversation that should have resolved uncertainty but somehow leaves everyone less certain than before. These moments, taken individually, are easy to rationalize or ignore. Over time, however, they accumulate. They begin to erode the shared confidence that allows teams to move quickly, communicate openly, and rely on one another fully.
As we continued talking, we began to notice that these fractures existed on multiple levels. Some were relational. People were more guarded than they appeared on the surface. They were slower to voice concerns, more likely to carry uncertainty privately, and more cautious about how their words might be interpreted. Other fractures were operational. Expectations weren’t always as clear as they needed to be. Ownership of certain responsibilities felt ambiguous. Communication systems that had worked well at an earlier stage of the company’s growth were beginning to show strain under increased complexity.
None of this was the result of bad intentions. In fact, the opposite was true. Everyone cared deeply about their work and about one another. That was part of what made the fractures so difficult to identify. Trust had been assumed because the people involved were trustworthy. But trust isn’t sustained by intention alone. It has to be actively supported by the structures and behaviors of the organization itself.
Once we understood that trust fractures were present, we faced a more difficult question: how do you surface something people may not feel safe naming directly? Our private conversations had given us insight, but they represented only a small portion of the organization’s experience. If we were going to understand what was really happening, we needed to create a way for everyone’s perspective to be heard.
When Expectations Only Exist In Our Heads
We decided to design a survey for the team. Not as a performance evaluation and not as a mechanism for assigning blame, but as a tool for listening. We asked questions about clarity, communication, support, and whether people felt they had what they needed to do their jobs well. We made the responses anonymous, not because we distrusted our team, but because we wanted to remove every possible barrier to honesty. Our goal wasn’t to confirm our assumptions. Our goal was to see reality more clearly.
When the responses came back, we were stunned. Not because they revealed resentment or hostility, but because they revealed just how differently people understood the same basic expectations. In many cases, we had assumed alignment where none actually existed. One question asked about expected response times for internal communication while working remotely. The answers ranged from “within five minutes” to “within one business day.” No wonder trust was fracturing. If one person believes a delayed response signals disengagement, while another believes they are operating fully within expectations, both walk away disappointed. One feels ignored. The other feels unfairly judged.
This is one of the most important and most dangerous dynamics in any organization: we judge ourselves by our intentions, but we judge others by their actions. The person who planned to respond later knows they care, knows they’re responsible, knows they’ll follow through. But the person waiting on the response doesn’t have access to those intentions. All they have is what they can see. And what they can see is silence.
That gap—between internal intention and external experience—is where trust begins to fracture.
Seeing that pattern was sobering, but it was also clarifying. The trust fractures weren’t the result of individual failure. They were the result of a system that had evolved faster than its internal trust structures. Once we had language for that reality, it became impossible to ignore. What had once felt vague and personal now had shape and definition.
Naming the fractures didn’t repair them. But it made repair possible.
Clarity Changes What You Can See
Clarity doesn’t eliminate hard conversations, but it makes them productive. It shifts the focus from defending individual intentions to strengthening shared systems.
In my next post, I’ll share what it actually took to begin repairing those fractures—and why rebuilding trust requires far more than simply asking people to try harder.
If this part of the story feels familiar to you, you’re not alone. And you don’t have to figure it out by yourself.
