Some of the most important breakthroughs I have witnessed started with someone saying, “I do not think that is right.”
That sentence can be an extraordinary gift. It can also begin a destructive argument. The difference is what happens next.
I have spent much of my career building companies, leading teams, and solving difficult problems alongside talented, passionate people. I have watched disagreement sharpen ideas and strengthen relationships. I have also watched it become personal. People grow defensive, evidence becomes ammunition, and everyone starts protecting a position instead of solving the problem.
The intensity can be identical. The first conversation produces heat. The second produces progress.
I call the second constructive friction. It is not the absence of conflict. In fact, conflict about a task, a decision, or an assumption can be healthy. The distinction I care about is between disagreement that advances a shared purpose and destructive conflict that shifts the objective toward defeating or diminishing another person.
Conflict becomes destructive when winning against each other matters more than winning together. I believe in living a Non-Net Sum Zero life. That conviction is easy to express and considerably harder to practice when you are certain you are right.
The Uncomfortable Truth About My Own Leadership
I have seen dysfunctional conflict in teams I have led. More importantly, I helped create some of those environments. I write these posts partly for my kids, and perhaps partly out of an overwhelming sense of Catholic guilt. The path forward starts with a confession.
Early in my career, I was intensely driven. I had high expectations, strong opinions, and an almost insatiable desire to accomplish more. Those traits helped me build businesses. They also created problems.
A mentor once told me, “I have never seen anyone press the gas pedal through the firewall on the post-race victory lap.” I was proud when he said it. His face indicated I should not have been. He was right.
What I did not understand was how much of my drive came from something deeper.
I was trying to fill a cavern in my own sense of self-worth and value.
Achievement became evidence that I mattered. Success provided validation, but the validation never lasted. There was always another problem to solve, another mountain to climb, another opportunity to prove myself.
That struggle did not remain internal. It shaped how I led.
When your sense of worth is entangled with your ideas, someone questioning an idea can feel like someone questioning your value. I could encourage people to challenge my thinking while making that challenge harder than it needed to be. I could believe I was pursuing the best answer while simultaneously being invested in my answer being the best.
I did not set out to discourage dissent. But intention and impact are different things. People pay attention to the way a leader reacts, not just what a leader says. A defensive reply, a prolonged interrogation, a dismissive expression, or subtle retaliation can teach an entire room that disagreement comes at a cost.
Then the room gets quiet. The leader may interpret that silence as alignment. It might actually be resignation.
An individual’s unresolved insecurity can become an organization’s operating culture. A leader’s hunger for validation can become a team’s habit of agreement. A leader’s fear of being wrong can become an organization’s inability to learn.
There is a hard truth here: leaders often create the very behaviors they later complain about.
It took years of personal development, introspection, mentors, coaches, my forums, meditation, and Courtney to see into my blind spots. It took learning that an idea could be wrong without making me wrong. That was not a management technique. It was personal work, and I am still doing it.
Strong Molecules. Stronger Teams.
My background in computer science and mathematics has shaped how I understand organizations. I often look for underlying systems, relationships, and principles that explain why something works. This is not an attempt at first-principles thinking. It is how my brain is wired by genetics, education, and experience. Molecular bonding offers a useful analogy for teams.
At an atomic scale, attractive and repulsive interactions help determine whether a configuration is stable. The full physics is considerably more complex, but the intuition matters: stability does not mean there are no opposing forces. It means the interactions produce a configuration that can hold together.
The goal is not maximum attraction or maximum friction. It is a strong, stable bond capable of withstanding stress.
Teams have a similar challenge. Trust creates connection. Shared purpose creates alignment. Respect helps preserve dignity when people disagree. Different experiences, perspectives, and convictions create the tension that tests assumptions and improves decisions.
Without sufficient connection, the team remains a collection of individuals. Without space for disagreement, the team becomes an echo chamber. And when challenge turns into contempt or humiliation, relationships can fracture.
Strong teams are not built by eliminating tension. They are built by creating bonds strong enough to withstand it.
There is another dimension to this analogy. A molecule can exhibit properties that its constituent atoms do not possess individually. Water is an obvious example. Its properties emerge from the arrangement and interactions of hydrogen and oxygen, not merely their presence.
The same possibility exists in a team. Complementary capabilities and strong relationships can create collective intelligence beyond what any member could accomplish alone. Strong bonds make the team resilient enough to handle friction. They also make it possible for something greater to emerge.
Composition alone is insufficient. Structure and relationships matter.
So leaders should ask more than whether they have assembled the best individuals. What is the nature of the bonds between them? Are they built on trust or dependence? Shared purpose or shared insecurity? Mutual respect or mutual avoidance? Can people challenge each other and become better for it?
From Needing to Be Right to Wanting to Get It Right
Ego can disguise itself as confidence, conviction, or an uncompromising commitment to excellence. Sometimes those qualities are exactly what they appear to be. But the question beneath them is worth asking: Am I fighting for the best outcome, or for the outcome that validates me?
I have strong opinions. The people close to me know that. They also know there are entire subjects, including sports, horror films, home repair, and, oddly, geography, on which I have very little to contribute.
There is nothing wrong with defending a well-founded position vigorously. The problem begins when changing your mind feels like losing yourself.
A leader who cannot be challenged eventually becomes a leader who cannot be corrected.
By my later years at Contegix, I rarely overrode the executive team’s decisions in our strategy meetings, even when every teammate, and I mean every teammate, knew I had entered the room with a different view. That was not because my convictions disappeared. I had to learn to distinguish arguing for an idea from insisting on owning the answer. I cannot claim I always got that balance right, but I became more deliberate about leaving room for the team’s judgment.
The less I needed an idea to validate me, the more freely I could let other people challenge it. The more freely we challenged ideas, the greater the opportunity to improve them.
That is the transformation: from needing to be right to wanting to get it right.
Safe Enough to Be Challenged
I am skeptical of the notion that healthy teams should always feel comfortable. Comfort can be wonderful. It can also conceal avoidance.
We sometimes call silence kindness when we are really protecting ourselves from an uncomfortable conversation. We tell ourselves we are preserving a relationship while allowing a problem to grow. There is a difference between being nice and being respectful. Respect sometimes requires telling someone what they need to hear, not merely what they want to hear.
Honesty is not permission to be cruel. Humiliation and aggression are not evidence of courage. But respect should not require dishonesty.
Some of the most valuable people in my life have been willing to tell me things I did not want to hear: Courtney, my best friends Ben and Pete, my forum mates, and my mentors. Not because they wanted to win, but because they cared enough to challenge me.
This is where Amy Edmondson’s research on psychological safety matters. Psychological safety is not protection from difficult questions. It is a shared belief that people can take interpersonal risks, including admitting mistakes, voicing concerns, and challenging assumptions, without fear of humiliation or punishment.
People often need to feel interpersonally safe before they are willing to become intellectually uncomfortable.
Safety alone is not enough. Teams need standards, accountability, difficult questions, and the courage to confront reality. A team where everyone feels safe but nobody is challenged is not the destination. Neither is one where everyone is challenged but nobody feels safe.
The objective is an environment where people are safe enough to be challenged and trusted enough to challenge others.
What Problem Are We Solving?
Constructive friction requires shared purpose, but shared purpose alone does not resolve every disagreement. Two people can care deeply about the same company while holding very different views about risk, timing, growth, and capital. They also need a fair way to examine evidence, make decisions, and move forward.
Software development reinforced this for me. A good code review is not about proving one developer smarter than another. It improves the software. An architecture discussion should expose assumptions, identify tradeoffs, and lead to better decisions. The best engineers can debate an implementation intensely, settle on a direction, and then execute together. They do not confuse disagreement with disloyalty.
When a conversation turns personal, a leader’s job is not automatically to end the disagreement. It is to restore its purpose. I find these questions useful:
- What problem are we actually solving?
- What evidence would cause each of us to reconsider our position?
- Are we examining an idea, or questioning someone’s worth or motives?
- What tradeoffs do we disagree about?
- Who owns the decision, and how will we commit once it is made?
Those questions do not guarantee agreement. They help distinguish a productive challenge from an argument that has lost its way.
And some conversations require more than better questions. If people have been humiliated, punished for dissent, or repeatedly ignored, trust must be repaired. You cannot ask for constructive friction while preserving conditions that make honesty unsafe.
The Bonds We Leave Behind
The more I reflect on my career, the more I believe leadership is measured as much by the environments we create and the people we become as by the problems we solve. The absence of conflict does not prove the presence of trust. Sometimes it proves the absence of courage. Or worse, the absence of caring.
This is not just a workplace lesson. Courtney and I have tried to teach Avery, Gabe, and Owen that being part of a family means working through disagreement rather than escaping it. We built structures that required cooperation and compromise, sometimes over something as ordinary as choosing dinner. The decision mattered less than learning to listen, challenge, give ground, and remain connected.
Our family mission statement says, “We focus on our bond. We do all of this together because we are always stronger together.”
That is what I want for my family and for the teams I have had the privilege to lead. Not people who never disagree, but people whose bonds are strong enough to disagree honestly, learn from each other, and build something none could build alone.