Trust Fractures: Defining What Trust Would Look Like Here
In the last post, I shared how a simple assignment—to rewrite our culture code—uncovered something much deeper. The issue wasn’t integrity. It wasn’t effort. It was trust. More specifically, it was the absence of shared expectations that allow trust to function.
By the time my project partner and I finished reviewing the survey results, it was clear that the original assignment—to rewrite the culture code—could not be completed by editing what already existed. We finally had data to support what I knew intuitively.
The fractures we had uncovered were not the result of outdated wording. They were the result of something far more fundamental.
We did not share a common definition of trust.
Up until that point, trust had existed inside the organization as an assumption. It was something we believed we valued, something we referenced frequently, and something we expected from one another. However, when we examined how trust actually functioned in practice, it became clear that each person was operating from their own interpretation. Those interpretations were shaped by personal experience, individual preference, and unspoken expectations, which meant that even when everyone had the best of intentions, our behaviors did not always align.
The survey had made that reality impossible to ignore. It had shown us, in concrete terms, that trust was not breaking down because people lacked integrity. Trust was breaking down because we lacked shared language.
Trust Requires Shared Language
Without shared language, trust cannot become shared practice.
If people do not have a mutual understanding of what trust requires, they cannot reliably meet one another’s expectations. They cannot calibrate their behavior. They cannot repair fractures effectively when they occur. Instead, each person judges what they can see, and what they can see are actions, not intentions.
This realization fundamentally reshaped our approach to the culture code.
Rather than drafting aspirational statements about who we wanted to be, we began defining trust in behavioral terms. We identified the core tenets that we believed were essential to building and maintaining trust, and we expressed those tenets as actions. We chose phrases such as Practice Integrity, Be Intentional, and Stay Relevant, not because they sounded compelling, but because they reflected behaviors that could be observed, practiced, and reinforced.
From there, we did the more difficult work of defining what those actions actually meant.
Trust Requires Shared Practices
Under Practice Integrity, for example, we included behaviors such as listening first and talking straight in order to create transparency and clarify expectations. We outlined specific active listening skills and provided examples that translated principle into practice. Each value was supported by similar behavioral guidance, and each bullet point represented a deliberate effort to answer a single, essential question:
This is what trust will look like here.
That clarity mattered, because shared language alone is not enough to sustain trust. Trust requires shared practice.
Language creates understanding, but practice creates reliability. When people consistently behave in ways that align with shared expectations, trust becomes something others can depend on rather than something they have to assume. Over time, those consistent behaviors create a sense of safety, and that safety becomes the foundation upon which strong culture is built.
Trust Requires A Shared Foundation
Once we had completed the culture code, we presented it to the company. However, before introducing the new framework, we began by sharing the survey results.
As we walked through the data, the conference table grew quiet. People saw themselves reflected in the responses. They saw their colleagues. They saw the gaps in expectation that had created confusion, frustration, and distance. The fractures that had previously existed as private experiences were now visible and shared.
That moment created the conditions for something new, because it established a common starting point.
From there, we introduced the culture code, not as a correction, but as a shared agreement. We explained the values, the behaviors, and the reasoning behind them. We showed how those behaviors translated into daily interactions, and how practicing them consistently would allow trust to grow in ways that were both intentional and sustainable.
For the first time, trust inside the organization had both language and structure.
We had not repaired every fracture. Trust does not rebuild overnight, and no document, no matter how thoughtful, can accomplish that on its own. However, we had created something essential. We had created a shared foundation.
Trust was no longer dependent on interpretation. It was grounded in agreement.
That foundation changed the trajectory of our culture, and it marked the beginning of the long, ongoing work of living those values in practice.
I’ll continue this story in the next post, because defining trust and practicing it are only part of the journey. Maintaining trust over time requires vigilance, courage, and, at times, difficult decisions.
If you’re wrestling with what trust looks like in your organization and how to build the structure for it, you don’t have to do this alone. Explore ways to work with me by clicking the button below.
