How do you resolve a cofounder conflict?

How to Embrace Conflict

1. Have a Plan of Action (In Writing)
2. Address Conflict Head On.
3. Work to Understand Your Co-Founder’s Point of View.
4. Come Up With a Solution.
5. Don’t Abandon Your Stance Once the Conflict Starts.
6. Don’t Bulldog Your Way to a Decision.
7. Arguments Should be Collaborative and Data-Based.

How do you get co-founder?

Entrepreneurs can meet co-founders in person by going to networking events and connecting with like-minded individuals. They can also search groups on social media; LinkedIn, in particular, offers many groups founders can join to find a co-founder.

What does a cofounder do?

Co-founder is a term that exists to give equal credit to multiple people who start a business together. A co-founder may be part of the vision of a startup from the get-go, or they may be brought on very early by the original founder because they have skills the founder is lacking.

What are the most common problems with co-founders?

Every co-founder situation is different, but one common problem that keeps popping up revolves around how the founders engage in conflict: either not enough, or far too much. Founder drama happens even in situations where you wouldn’t expect it to crop up. Success will cover up many sins.

Can we predict co-founders’ relationship failures?

When psychologist John Gottman (author of the Four Horseman concept) identifies those behaviors in marital relationships, he’s able to predict relationship failure with uncanny accuracy. The same thing holds true for co-founders.

What makes a successful co-founder successful?

Successful co-founders actually embrace conflict, and are constantly in the process of resolving it. If you can’t argue and arrive at the best solution, you’re not doing the work to actually have a real, healthy working relationship.

Why do founders fight about everything all the time?

When founders are in a situation where they are fighting about everything all the time, it usually means that their individual roles are not well-defined enough. Two hacker founders refuse to give up ground over an architectural decision,  product-oriented founders with similar skill sets fight over direction and so on.