CTO Fraction

Why The Phrase “Trust but Verify” is an Oxymoron

Has anyone told you to “trust but verify”? This phrase has become so popular that it sounds as if the saying is true. As if you can have both trust and the need for verification at the same time. However, is that true?

The Origin of the Phrase

“Trust but Verify” is a Russian proverb which was adopted by Ronald Reagan in the 80s. Today, it is a phrase used in the business world. Some have gone so far as to promote it as a good leadership practice.

But can this innocent phrase be what it says?

It is “either/or” but not “both/and”

We believe one cannot simultaneously have their cake and eat it too. Yet, at the same time we also buy into the idea that one can be trusted but also needs to be checked.

Is that even possible?

Trust” by definition means: “assured reliance on the character, ability, strength, or truth of someone or something”

Verify” by definition means: “to establish the truth, accuracy, or reality of”

Therefore, if I am sure that something is true, do I need to establish its truth?

When we get into our car, we trust that the brakes will work; therefore, we do not verify their proper functioning before every trip to the grocery store.

When we board an airplane, we trust that all its gear is in good working order; therefore, we do not ask the mechanics to show us proof.

When we get on a roller coaster we trust that someone already ensured our safety. Therefore, we do not go and inspect the whole track and train cars ourselves.

We are either in a state of trust or doubt. Trust does not require verification, but doubt does.

One might say, ‘Well, I am scared of flying and feel very nervous every time I get on an airplane.’ However, despite these feelings, that person still boards the airplane. However, that person got on the airplane anyway. One demonstrated their trust with their action – they boarded the plane. Fear and trust are two separate things.

To borrow from the style of Yoda:

Trust or trust not. There is no trust AND verify.

An Example

Alex Honnold is known as the first person to climb a route on El Capitan in Yosemite National Park, in a “free solo” style. He knew that one mistake meant certain death. That’s why he spent 18 months training and preparing for this one climb. In this video Alex explains that on the day of the climb “It felt as comfortable and natural as a walk in the park”.

Why did he not attempt the climb right away? Because he did not trust himself at first. Therefore, he needed to perform hundreds of roped climbs and choreograph every single move on that daunting wall. He needed to “verify” his ability, time and time again, in order to gain his own trust that he could do it flawlessly without dying.

After months of training and verifying, he crossed the bridge from not trusting himself, to having complete trust. Only then did he attempt the dangerous climb.

What Does the Phrase Actually Mean?

I have heard the phrase “Trust but verify” said in business settings to managers and leaders who are responsible for their team’s delivery. The times when I heard it, was when something went wrong, or not as expected. While those saying the phrase normally mean well, I believe this phrase in reality says something different from what it sounds like.

I believe the phrase actually says “Don’t trust and verify”. However, this is an uncomfortable thing to say, because it implies that we do not trust the people we work with. Therefore, it is easier to sugarcoat the real message with “Trust but verify”. It does not make us look bad while it still encourages the verification act.

Verification is a Good Thing

Verification is often necessary, especially when the stakes are high. Leaders and managers should verify many aspects of their team’s work. In a healthy team culture people should not be offended when someone verifies their work.

That is why many software teams have Quality Assurance members and Testers. That is why companies have content editors. It is the cycle of improving something by getting more eyes on it.

Of course, verification can be taken too far and turned into micromanagement. This leads me to the next section.

Trust is Also a Good Thing

Building trust with those we work and live with is an important aspect of relationships. In the business place trust needs to be built and exercised.

No one likes to have a superior constantly looking over their shoulder and checking their work. Most people who care about their work appreciate a sense of responsibility and ownership. They want to be trusted.

Trust is not a guarantee that something will/won’t happen. Trust is only our level of assurance, or belief. Things can still go wrong even when we trust. However, that is when we lose trust and go back to having the need to verify.

There are also degrees of trust. I trust you for this but not for that. I believe you can complete X, but not Y. Trust is built over time and it takes many repetitions. The more repetitions that confirm our beliefs, the more our trust grows.

Unsure how to steer your software development forward?

In navigating the intricate balance between trust and verification within your tech startup or software company, have you considered the impact of seasoned leadership on bridging this gap? As a Fractional Chief Technology Officer, I specialize in steering companies through the challenges of launching and scaling their technology and processes.

Aiming for more? Understand how a Fractional CTO can refine and enhance your business processes.

Conclusion

Trusting blindly is not a good thing, especially when the stakes are high. On the other hand, never trusting and verifying everything can be impractical and offensive to people.

Aiming for balance, with a constant goal of increasing trust over time while decreasing the need to verify, is a healthy approach.

I believe that the phrase “Trust but verify” is an oxymoron, because we cannot have trust and the need to verify at the same time.

Are we using the phrase because we have not thought about what it says or, because our corporate culture does not allow for transparent conversations?