VaughnMartinReadiness OS
Explore the Platform Request a Meeting
Chapter 3 of 254 min read

Trust Is the Ultimate Deliverable

Quality cannot be inspected into a product after it is made. Inspection can find defects without changing the process that created them. Deming argued for redesigning the system instead, so that quality became a structural concern rather than something checked at the end.

Trust is not product quality, but the analogy raises a useful question: what systems and behaviors support trust inside an organization? Individual leadership behavior matters. Communication architecture, governance processes, and decision patterns may also shape whether trust outlasts particular leaders.

At a financial services organization I led through a significant transformation, I inherited a PMO built around one leader's exceptional capability. Her judgment, relationships, and communication were strong, and the organization moved when she was present. When she left for another division, the PMO's performance declined within six months. Her replacement was not incapable. The trust and context had never been transferred into the system. One case does not prove that trust is entirely structural, but it shows how a capability can stay tied to one person when practices are never made explicit.

The three conditions below are dimensions of trust that can support specific organizational capabilities.

Stephen M.R. Covey framed trust as an economic force rather than a soft virtue. High trust can make coordination faster and cheaper, while low trust adds verification time to transactions and initiatives.

Trust in Communication helps information move fast enough to support coordinated action. When people doubt that information is accurate, complete, or timely, they verify it before acting, and in a fast-moving Strategic Situation that delay can matter. Consider a hypothetical supply-chain disruption. The COO receives an accurate but incomplete report because the operations team is reluctant to surface negative context before it has a solution. Decisions made on that partial picture create commitments that constrain later options. That would point to a Trust in Communication problem: the system does not make it safe to raise difficult information before solutions are ready. A stronger communication architecture can make it easier to share uncertainty and possible severity early. It cannot guarantee that a response window stays open.

Trust in the System shapes whether people follow established processes or work around them. When governance reverses decisions without explanation, escalation paths produce inconsistent outcomes, or informal prioritization undercuts resource commitments, people lose confidence and look for informal routes. Workarounds create local optimization and divergence across the enterprise. An organization that leans heavily on informal relationships can stall when those relationships are unavailable.

Trust in Leadership supports commitment before all the answers are clear, and Strategic Situations often require some action before information is complete. In my experience, organizations mobilize better under incomplete information when people trust the direction they are given. They need to believe it reflects an honest reading of the situation, commitment to the organization's interests, and accountability for outcomes. That is less about confidence in a leader's intelligence than confidence that the leader will be candid when the news is uncomfortable.

I have spent long stretches rebuilding Trust in Leadership in organizations where leaders had presented reactive decisions as strategic. They had also projected confidence when the leadership team was uncertain. The damage went beyond individual reputations to the organizational architecture that needed Trust in Leadership to function. Teams that should have been moving waited to see how things developed. Resources that should have been committed were held back in case of another reversal.

In the case I observed, the Mobilization Tax on later initiatives was estimated to have doubled. People added verification time that stronger trust might have made unnecessary. Rebuilding trust took eighteen months of consistent behavior: transparent decisions, commitments honored or explicitly renegotiated, and honest acknowledgment of uncertainty. The path will vary, but rebuilding trust often takes repeated experience.

Leaders can do more than encourage individual transparency. They can build communication architecture that supports accurate information, governance processes people can rely on, and accountability structures that make outcomes visible. Daniel Coyle's study of high-performing groups describes practices designed into how groups operate. Such practices can help a capability outlast any one person. In the organizations I led where trust was strong, consistent systems and leader behavior both mattered. A trustworthy leader is important, but systems that support trust can help it survive leadership transitions.

PrevContentsNext