Navigate Conflict & Create Psychological Safety

A startup is fast-moving and chaotic, and often staffed by smart young people with limited experience — conflict is guaranteed; unresolved conflict is optional. The move is to define how you fight before you fight, while you're calm, because you will not design anything sensible mid-argument. Two cofounders I worked with — long history, and yes, sometimes shouting in front of the team — made themselves a rule: if the voices start rising, either one says a magic word, the conversation stops on the spot, and within 24 hours they book a whiteboard session and hash it out properly. I thought that was amazing. They designed their conflict while they were calm, instead of improvising it while they were angry. Put a "how we resolve conflict" section in your relationship doc and actually invoke it.

The stakes are bigger than the two of you. Fighting in front of the team is the fastest way to teach everyone that conflict here is dangerous — and once people believe that, disagreement goes underground, which is where it does real damage. The inverse is also true: when the team watches the two of you stop, cool down and visibly repair, conflict stops being scary. Psychological safety isn't the absence of arguments; it's the confidence that arguments end well.

The line neither of you can see across

My intention is accessible only to me. My speech and behaviour are accessible to both of us. Your reaction is accessible only to you. Crossing the line means assuming what only the other person can know — and it's hiding inside almost every escalation. The cleanest example I've seen: a first-time manager who went to her report's desk every single day, looking over her shoulder, correcting and suggesting. Her intention: be an awesome, supportive manager. What landed: "she doesn't trust me, she thinks I'm a baby, she's micromanaging me, this is awful." Both were assuming across the line; neither said a word; the conflict arrived on schedule.

Safety is a team sport

Conflict design scales past the cofounder pair. Lencioni's Five Dysfunctions names vulnerability-based trust as the foundation under productive conflict — build it deliberately with Personal Histories, or the Blob Tree when words themselves are the obstacle. And because founders always hear the polite version, run an anonymous pulse check to find out whether people actually feel safe disagreeing. Before any conversation you're dreading: two minutes of prep — three things to get across, three emotions to bring into the room.