Article

Trust vs. Performance: The Navy SEAL Lesson

Why a high-performer with low trust is the most toxic element in your engineering team.

LeadershipTeamsSimon Sinek

Simon Sinek often shares a lesson he learned from the Navy SEALs, one of the most high-performance organizations on earth. When the SEALs evaluate their candidates, they don't just look at Performance (skills on the battlefield). They look equally at Trust (character off the battlefield).

On a simple 2x2 grid, the SEALs would rather have a "Medium Performer, High Trust" individual than a "High Performer, Low Trust" individual.

The Brilliant Jerk

In software engineering, we call the "High Performer, Low Trust" individual a Brilliant Jerk. This is the developer who can solve any bug and write massive amounts of code, but who treats their teammates with contempt, hoards knowledge, and makes everyone around them feel small.

The problem? While the "Brilliant Jerk" might have high individual output, they are a net negative for the Team Product. Their presence destroys the "Circle of Safety" and causes the rest of the team to move into "Survival mode."

This behavior creates a massive Cost of Secrecy. When knowledge is used as power rather than a shared resource, the team's ability to respond to change is paralyzed. If only one person knows how a critical system works, that person becomes a bottleneck for every feature and a single point of failure for every outage. By decoupling your technical value from your exclusive knowledge, you actually increase your impact as a senior engineer. You transition from being a "Solitary Expert" to a "Team Force Multiplier," which is the highest form of performance in any engineering organization.

Measuring Trust in Tech

Performance is easy to measure: tickets closed, lines of code, uptime. But how do we measure trust?

  1. Knowledge Sharing: Do they proactively mentor others, or do they build "Technical Silos" to ensure they are indispensable?
  2. Admission of Error: Can they say "I don't know" or "I made a mistake," or do they shift the blame to the "Junior" or the "Network"?
  3. Empathy in Code Reviews: Are their comments constructive and encouraging, or are they nitpicky and belittling?

The Leader's Choice

A manager sees a Brilliant Jerk and thinks: "I can't fire them, they're the only one who understands the legacy billing system."

A leader sees a Brilliant Jerk and thinks: "I have to fix this behavior or let them go, because they are preventing the rest of the team from reaching their potential."

High performance is a result. High trust is the foundation. If you build for trust first, the performance will inevitably follow.

Credits & References

  • Simon Sinek: Trust over Performance - The talk inspired by the Navy SEALs.
  • Marcus Thorne: Why High-Performance Teams actually Fail? - On the structural rot of ego.
  • Decoupled Leadership Series: Part 4 of the Simon Sinek series.

Next in Leadership Lessons from Simon Sinek

Ready for the next lesson?

Continue to Part 5: Next Article →

About the writer

Marcus Thorne

Head of Engineering

Discussion

Keep the conversation going

Log in to join the discussion.

No comments yet. The first thoughtful reply can set the tone for the whole thread.