Tools for founders to navigate and move past conflict

Conflict in a founding team is not a sign of weakness — it is an inevitable consequence of bringing together ambitious people with high stakes. The problem arises when founders cannot resolve this conflict constructively. Instead of dialogue, there is escalation. Instead of growth, stagnation. And instead of trust, it gets cold. The thing is, company culture is built not on values written on a wall, but on how people actually react in difficult moments — how leaders behave when emotions run high, when decisions are tough, when visions diverge.

Ian Schmidt, strategic advisor at Trimergence — a consulting firm specializing in leadership coaching — has a clear observation: most founders have never learned how to handle conflict. Not because they are bad people, but because no one taught them. In a discussion about Build Mode, Schmidt points to something that sounds simple but changes everything: founders must update their personal operating systems. It's not about being nice for the sake of being nice. It's about building a working framework that scales with the company — from three people in a garage to hundreds of employees.

Why conflict in founding teams is inevitable (and why that's good)

Founders are by definition people who cannot help but act. They are possessed by a vision, self-confident (sometimes overly so), and have strong opinions about almost everything. When you bring two or three such people together, conflicts are not only possible — they are guaranteed. And that is completely normal.

The real problem emerges when the team has no tools to work with these conflicts. Then instead of constructive debate, personal animosity appears. Instead of problem-solving, there is a power struggle. Instead of growth, there is decision paralysis. Schmidt emphasizes that most founding teams fall into the trap of unproductive arguments, where emotions usurp the place of logic. Leaders lose control, say things they don't mean, and then everyone walks on eggshells, afraid of the next outburst.

Company culture is not built in onboarding processes or in values documents. It is built in real interactions — in how the team responds to stress, how it solves problems, how it says "no" to each other without aggression. If employees see that co-founders fall into the trap of unproductive arguments, it sends a signal: here, conflict is something to avoid, not something to solve constructively. This sets the tone for the entire organization.

Personal operating systems — what does that actually mean

Schmidt uses an interesting metaphor: each person operates like an operating system. They have built-in programs that run automatically — reactions to stress, communication patterns, ways of dealing with frustration. We typically install these programs in childhood and youth, and most of us never update them. We operate on old code that is not adapted to the reality we live in now.

For a founder, this means that if they learned in childhood that conflict is something dangerous, they will either avoid it or escalate it aggressively. If they learned that their opinion must always be right, they will be defensive when someone questions it. If they learned that emotions are weakness, they will suppress them until they explode. These automatic programs run in the background, without our awareness, but they completely shape how we behave under pressure.

Updating the operating system means consciously rebuilding these automatic programs. It is not a one-time training. It is long-term work on oneself — recognizing patterns, understanding where they came from, and consciously choosing a different way to react. For a founding team, it means that everyone must be ready for this work.

Building frameworks from the start

The best time to build the ability to resolve conflicts constructively is now — when the team is still small. Schmidt suggests that if founders do this work when there are only two or three people, they can build frameworks that will scale as the company grows. This is key: you cannot wait until conflict becomes unbearable. You need to be proactive.

One concrete tool that Schmidt recommends is establishing a common language around conflict. This means the team must talk about how it will work with conflicts before they appear. For example: How will we tell each other that something hurts? What signs signal that a discussion is becoming unproductive? When should we break and come back to it later? What does "constructive conflict" mean to us?

These conversations can be uncomfortable. Founders typically want to act, not talk about how they will act. But this is an investment. If the team goes through this conversation now, when there is no crisis, it will have solid foundations when things heat up. It will have a common vocabulary, common rules, common understanding of what is acceptable and what is not.

Practical tools to apply right away

Schmidt points to several concrete practices that founding teams can implement immediately. The first is regular team retrospectives — not just about the product, but about how the team works together. What went well in communication? Where did we stumble? What can we change? This is not a criticism session, but an opportunity for collective learning.

The second practice is setting boundaries for emotional conversations. This does not mean suppressing emotions — it means consciously deciding when and how to express them. For example: if a discussion gets too heated, the team can have a rule that they take a 15-minute break and then come back to it. It is simple, but it changes everything — it gives everyone time to cool down and return to rational thinking.

The third practice is individual coaching sessions for each founder. Not everything can be solved in a group. Sometimes a founder needs to work alone on their triggers, their reactivity patterns, their unresolved issues. This may sound like a luxury, but it is an investment in the team's ability to function.

• Regular team retrospectives — not just about the product, but about dynamics
• Jointly established protocol for difficult conversations — when to break, when to return
• Individual coaching for each leader — to work on their own patterns
• Open communication about how we feel — not just what we think
• Regular feedback loop — telling each other how we are doing

Scaling frameworks as the company grows

When a company grows, the dynamics of conflict change. When there are five people, everyone is in one room and sees everything. When there are fifty, a layer of managers appears, silos, politics. If the foundations are not solid, chaos grows exponentially. That is why it is important that the frameworks built at the beginning are scalable.

Schmidt suggests that if the founding team learns to work constructively with conflict, it can teach the entire organization. When new employees join, they see that leaders can argue without aggression, that they can change their minds, that they can admit mistakes. This becomes a cultural norm. Instead of a company where people avoid conflict, a company emerges where people can resolve it constructively.

This means that investment in conflict resolution capabilities at the three-person stage pays off many times over when the company has a hundred people. You don't have to start from scratch then, teaching the entire organization new habits. The culture has already embedded it.

The resistance that will appear along the way

If this sounds ideal, it is because it sounds ideal — but reality is more complicated. Most founders will resist this work. They will think it is psychobabble, that they should focus on the product instead. They will feel uncomfortable talking about emotions and patterns. They will want a quick fix, and this is not quick.

Schmidt does not hide this fact. This work is hard, uncomfortable, and sometimes painful. It requires founders to look at themselves in the mirror and admit that they can behave worse than they would like. It requires them to say "I'm not right" or "I was afraid, so I reacted aggressively". This is really hard for people who usually win.

But without this work, conflicts will repeat. They will grow. And at some point the team will fall apart — either because one of the founders leaves, or because everyone will be so tired of the atmosphere that nothing will happen. History is full of companies that had a great idea, a great product, great timing — but the founders could not work together.

Polish perspective: where are we

In the Polish startup ecosystem, this conversation is relatively new. We have a culture where action, results, and strength matter. Conversations about emotions, about reactivity patterns, about personal operating systems — this sounds to many people like a luxury for the weak. But the Polish tech scene is growing rapidly, and with it the number of teams that fall apart for exactly the reasons Schmidt describes.

Polish companies that survive and scale globally will be those that learn this lesson. Not because it is nice or comfortable, but because it works. Teams that can work constructively with conflict are more creative, faster at decisions, more resilient to stress. This is business logic, not psychology.

For Polish founders, this means it is worth investing in coaching, in facilitation, in learning conflict management. It is worth talking about it openly — not as a weakness, but as a skill that needs to be developed like any other. The earlier the team does this, the better.

The final lesson: conflict is not the enemy

If we take a step back, Schmidt's main lesson is simple but profound: conflict in a founding team is not a problem to be eliminated, but a resource to be managed. Teams that do not argue do not think. Teams that do not argue do not innovate. Teams that do not argue usually do not develop either.

The problem arises when conflict is unproductive — when it is personal, aggressive, destructive. But constructive conflict, where people argue about ideas, about direction, about priorities — that is a sign of health. It means everyone is engaged, that everyone cares, that everyone has something to say.

For founders who want to build companies that survive and grow, this means one thing: start with yourself. Update your personal operating system. Learn to handle conflict constructively. Invite your team to this work. Build frameworks together. And then, when difficult moments come — and they will — you will be ready. Not because conflict will disappear, but because you will know how to go through it without destroying what you are building together.