Guide \u00b7 When it grinds<\/p>\n\n\n\n
Updated: 24 July 2026<\/p>\n\n\n\n
You argue and can’t move forward? Most conflicts in a leadership or founder duo are experienced as an interpersonal problem \u2013 but they’re a structural problem. The five typical patterns, a self-assessment and first steps.<\/p>\n\n\n\n
Contents<\/strong><\/p>\n\n\n If you’re in the middle of it right now: this can be sorted. The most important sentence first \u2013 most duo conflicts aren’t a relationship problem but a structural one. Unclear roles, missing decision rules, unspoken expectations. That’s a relieving message, because structure can be repaired.<\/p>\n\n\n\n Unlike a team conflict, a conflict in a leadership duo affects the top \u2013 and the top is visible. The team senses it immediately, decisions stall, and because both carry responsibility, neither can simply overrule the other. That’s exactly why it helps to move the conflict from the personal to the structural level.<\/p>\n\n\n\n How it feels:<\/strong> It feels like stubbornness: each insists on their view, nothing moves.<\/p>\n\n\n\n What’s structurally behind it:<\/strong> Behind it isn’t stubbornness but a missing rule: no one ever set who decides in doubt.<\/p>\n\n\n\n First step:<\/strong> First step: play through a single fundamental decision and set who makes it in the end.<\/p>\n\n<\/div>\n\n\n\n How it feels:<\/strong> One pulls more but doesn’t say so \u2013 until frustration builds.<\/p>\n\n\n\n What’s structurally behind it:<\/strong> The load split was never made explicit, so it grows crooked.<\/p>\n\n\n\n First step:<\/strong> First step: honestly write down the actual split, not the felt one.<\/p>\n\n<\/div>\n\n\n\n How it feels:<\/strong> You get contradictory information and puzzle over decisions you never made that way.<\/p>\n\n\n\n What’s structurally behind it:<\/strong> Without a unified line, others use the gap \u2013 usually not maliciously, but because they can.<\/p>\n\n\n\n First step:<\/strong> First step: agree that important answers are given in coordination.<\/p>\n\n<\/div>\n\n\n\n How it feels:<\/strong> It ran well for a long time, now everything suddenly grinds.<\/p>\n\n\n\n What’s structurally behind it:<\/strong> You never defined roles because it worked without \u2013 until it didn’t.<\/p>\n\n\n\n First step:<\/strong> First step: retroactively define who’s responsible for what.<\/p>\n\n<\/div>\n\n\n\n How it feels:<\/strong> You argue over individual decisions that are actually symptoms.<\/p>\n\n\n\n What’s structurally behind it:<\/strong> Your goal images were never aligned \u2013 you’re steering for different harbours.<\/p>\n\n\n\n First step:<\/strong> First step: separately write down where you want to be in two years, and compare.<\/p>\n\n<\/div>\n\n\n\n Five questions for self-assessment \u2013 answer them honestly, each on its own:<\/p>\n\n\n\n\n\n
Why duo conflicts differ<\/h2>\n\n\n\n
The five typical patterns<\/h2>\n\n\n\n
The unclear final decision<\/h3>\n\n\n\n
The uneven load<\/h3>\n\n\n\n
The team plays you off<\/h3>\n\n\n\n
Grown together without roles<\/h3>\n\n\n\n
Different goal images<\/h3>\n\n\n\n
Which pattern is yours?<\/h2>\n\n\n\n
\n\n
First steps you can take alone<\/h2>\n\n\n\n
\n\n
When it no longer works alone<\/h2>\n\n\n\n
\n\n