Why It’s Important to Disagree with Your Co-Founders Early

While I don’t always ask this question, when I do, it provides me enormous context to how the founding team works together. What do you and your co-founders fundamentally disagree on? Over the years, I’ve heard many different answers to this question. “We disagreed on which client to bring into our alpha.” “On our last hire.” “Our pricing strategy.” And so on. As long as you contextualize the point of friction, and elaborate on how, why, and what you do to resolve it, then you’re good. There’s no right answer, but there is a wrong answer.

The answer that scares me the most is: “We agree on everything.” Or some variation of that. While people may share a lot of similarities, even potentially the same Myers Briggs personality type (although I do believe people are more nuanced than four letters), no two people are ever completely the same. Take twins, for example. Genetically, they couldn’t be any more similar. Yet, to any of us, who’ve met any pair of twins in our lifetime know they are vastly different people.

Priorities lead to disagreements

One of my favorite counterintuitive lessons from the co-founder and CEO of Twilio, Jeff Lawson, is: “If your exec team isn’t arguing, you’re not prioritizing.” He further elaborates:

“As an executive team, we never actually argued — which is a strange thing to bother a CEO. But in fact, something always felt not quite right to me when we always agreed. Clearly, we must not be making good enough decisions if we all agree all the time.

“What I came to realize was that the reason why we didn’t argue is we weren’t prioritizing. One person says, ‘I like idea A,’ and the other person says, ‘I like idea B,’ and you say, ‘Great, put them both down, we’ll do it all!’ And in fact, when you look back on those documents at the end of the year, we rarely got around to very much of anything in those documents.

“Be vigorous not just about what makes the list, but the specific order in which priorities fall. “We realized it’s not just about all the things we could do, but the order of importance — which is first, which is second. Now you get disagreements and a lot of vigorous, healthy debate.”

Starting the tough conversation

Admittedly, it’s not always easy to have these tough conversations with the people you trust most. In fact, often times, it’s even harder to have these conversations because you’re scared about what it can do to your relationship. Arguably, a fragile one at best. At the end of last year, Yin Wu, founder of Pulley, shared an incredible mindset shift when building an all-star team, which led to my conversation with her.

You’re a team driven to change the world we live in. And to do so, you need a system of priorities.

One of the best ways I’ve learned to address conflicts – explicit and implicit, the latter more detrimental than the former – is taking the most obvious, but the one that most people try to avoid. Address the elephant in the room at the beginning.

I love the way Elizabeth Gilbert approaches that elephant, “The truth has legs. It’s the only thing that will be left standing in the end. So at the end of the day, when all the drama has blown up, and all the trauma has expressed itself, and everyone has acted up and acted out, and there’s been whatever else is happening, when all of that settles, there’s only going to be one thing left standing in the room always, and that’s going to be the truth. […] Since that’s where we’re going to end up, why don’t we just start with it? Why don’t we just start with it?”

When it hasn’t happened yet

If you haven’t disagreed with your team yet, you either haven’t established your priorities or one or the other or both has yet to bring it up. A mentor of mine once told me, “Whatever you least want to do or talk about should be your top priority.” And the goal is to sit down with your team and figure it out. To come into the conversation suspending immediate judgment and trying to see where your other team members are coming from.

As the CEO of a startup or a leader of a team, you don’t have to use every piece of feedback or input you get from your teammates. But you should make sure your teammates feel heard. That you’ve put thought and intention behind considering their ideas and opinions. Whether you choose to deviate from your teammates’ opinions or not, you should clearly convey the rubric that you used to make that decision. And why and how it aligns with the company’s mission.

In closing

And of course, the follow-up to the first question about disagreement would be: How often do these disagreements happen? And how do you move forward after the disagreement comes to light?

I go back to a line Naval Ravikant, co-founder of AngelList, once said, “If you can’t see yourself working with someone for life, don’t work with them for a day.” Indubitably, you’re going to be working with your co-founders for a long time. And if you haven’t dissented with your co-founders – or for that matter, other team members, investors, and customers – yet, you will. And knowing what, how and why you disagree with others can be invaluable for your company’s survival and growth.

This past weekend I heard a new phrasing of disagreement I really liked from a friend of mine. “Creative conflict.” I’m adding that phrase to my dictionary from now on. And well, this is my preface to you all before I do.

Prioritize. Communicate. And embrace creative conflict.

Photo by Ming Jun Tan on Unsplash


Stay up to date with the weekly cup of cognitive adventures inside venture capital and startups, as well as cataloging the history of tomorrow through the bookmarks of yesterday!

2 Replies to “Why It’s Important to Disagree with Your Co-Founders Early”

  1. Couldn’t agree more. My co-founder and I spend the 1st year arguing over every little detail of the product. It was exhausting. And frustrating. And was the key to building a fantastic product.

Leave a Reply

Your email address will not be published. Required fields are marked *