The best meeting I ever had with Bruno was a fight. Not a shouting match — neither of us is the type. But a genuine, sustained disagreement about the direction of PipelineRoad that lasted most of an afternoon and left us both drained and slightly irritated. We walked away with a decision that was better than either of our original positions, and a deeper respect for each other’s thinking.
Most co-founder relationships don’t survive disagreement. Most teams don’t, either. Not because the disagreements are too severe, but because nobody ever taught them how to disagree without it becoming personal, political, or corrosive.
Productive disagreement is a skill. It’s arguably the most important skill a team can develop, and it’s the one that gets the least deliberate practice.
Why Teams Avoid It
The default mode in most organizations is artificial harmony. People nod along in meetings, suppress their reservations, and then complain in private. This isn’t politeness — it’s cowardice dressed up as professionalism.
The reason is obvious: disagreement feels risky. If you challenge someone’s idea, they might take it personally. If you push back on the founder’s strategy, you might get labeled as “not a team player.” If you question a decision that’s already been made, you might be seen as difficult.
So people stay quiet. And the company pays for it in bad decisions that nobody challenged, strategies that nobody stress-tested, and problems that everyone saw coming but nobody raised.
I’ve been guilty of this from both sides. I’ve stayed quiet when I should have spoken up, and I’ve created environments where people felt they couldn’t push back on me. Both failures had real costs.
The Architecture of Good Disagreement
Disagreeing well isn’t about being blunt or “radically candid” or any of the other frameworks that give people permission to be abrasive under the guise of honesty. It’s about structure.
The first principle is separating the idea from the person. This sounds simple and is extraordinarily difficult in practice. When someone presents a strategy they’ve spent weeks developing, challenging the strategy feels like challenging them. The only way through this is to make it explicit: “I think your analysis is thorough. I disagree with the conclusion, and here’s why.”
That framing — acknowledging the work while questioning the outcome — creates space for the other person to engage with the disagreement without feeling attacked. It’s not a trick. It’s genuine respect for their effort combined with genuine conviction that they’re wrong.
The second principle is arguing from evidence, not authority. “I’m the founder, so we’re doing it my way” is not disagreement — it’s a power move. It ends the conversation without resolving anything, and it teaches the team that their input doesn’t matter. The worst version of this I’ve seen is the leader who asks for input, ignores it, and then wonders why nobody speaks up anymore.
When Bruno and I disagree, we argue with data, with examples, with analogies to past situations. Sometimes one of us is clearly right and the other concedes. More often, the truth is somewhere between our positions, and the argument itself is what surfaces it.
The Emotional Discipline Required
Here’s the part nobody talks about: disagreeing well requires emotional regulation. Not suppression — regulation. You have to feel the discomfort of being challenged and choose not to react defensively. You have to notice when your ego is driving your position and consciously set it aside.
I’ve gotten better at this over the years, but I’m far from perfect. There are moments when someone challenges an idea I’m attached to and I feel the temperature rise. The impulse is to defend, to explain, to escalate. The discipline is to pause and ask myself: am I defending this idea because it’s right, or because it’s mine?
That question, asked honestly, resolves about half of all disagreements before they become conflicts.
What Productive Disagreement Produces
When a team gets good at disagreeing, something remarkable happens: the quality of decisions improves dramatically. Ideas get stress-tested before they hit the market. Strategies get refined before they consume resources. Problems get surfaced before they become crises.
More subtly, trust deepens. When you know your colleagues will tell you the truth — even when it’s uncomfortable — you stop second-guessing whether their agreement is genuine. You stop wondering what people really think. The meeting becomes the actual conversation instead of a performance that precedes the real conversation in the hallway afterward.
At PipelineRoad, the moments I’m most proud of are not the moments we agreed brilliantly. They’re the moments someone on the team told me I was wrong, I listened, and we changed course. Those corrections — uncomfortable in the moment, invaluable in hindsight — are what keep a company on track.
The Rule I Try to Follow
I’ve adopted a simple personal rule for disagreement: if I wouldn’t be willing to say it directly to the person’s face, with genuine respect, I shouldn’t say it at all. And if I have something I would say directly to their face, I’m obligated to say it.
This eliminates the two failure modes: the cowardice of staying silent and the cruelty of talking behind someone’s back. What’s left is direct, respectful, constructive friction. The kind that makes teams better and relationships stronger.
It’s not comfortable. But the alternative — a team that agrees on everything — should worry you far more than a team that argues well.