\n<\/p>\n
The stakes are high for any founding team, so conflict should be expected, even encouraged. However, company culture is built on real reactions and interactions, not the values you put on the wall. If team members see co-founders or the leadership team getting heated and falling into unproductive fighting, that doesn\u2019t set a respectful, growth-minded tone.\u00a0<\/p>\n
Luckily, it\u2019s possible to repair this dynamic and do the work to learn how to navigate conflict in a healthy way. Ian Schmidt is a strategic adviser at Trimergence<\/a>, a consultancy that coaches leaders to become more effective from the inside out. On a recent episode of Build Mode<\/a>, Schmidt discussed how founders and teams need to update their personal operating systems.<\/p>\n \u201cBusinesses have a human operating system, and that human operating system needs an upgrade process over time, just like the product does and your go-to-market strategy,\u201d Schmidt said. \u201cSo we work with leaders and teams to map their operating system, how they think, how they manage conflict, how they do decision-making, and really provide them with what we call a noise-reduction algorithm.\u201d<\/p>\n In practice, that means that founders can create frameworks for working through conflict and change when the team is just two or three people, and if done correctly, it can scale with the company.\u00a0<\/p>\n Schmidt offered a framework that any founder, leader, or even team member can implement when conflict arises:<\/p>\n When a conflict doesn\u2019t go well, it\u2019s crucial to take stock of the conversation and own your part in it. Maybe you lashed out, escalated the conflict, or otherwise created a bad moment in front of the team. Don\u2019t try to rush a solution, take a second to self-audit, name what happened, and try to imagine how it may have impacted others.\u00a0<\/p>\n When conflicts get heated, it\u2019s very rarely a one-off issue. Take the time to see the pattern in this behavior. \u201cHow does this relate to something that I know about myself? Oh, my partner tells me this all the time, or I\u2019ve seen this over time growing up, or I\u2019ve received this feedback before. So you have both the situation and the pattern,\u201d said Schmidt.<\/p>\n Techcrunch event<\/p>\n \n\t\t\t\t\t\t\t\t\tSan Francisco, CA<\/span> After you\u2019ve reflected, go to your team members for any interpersonal repairs that are needed. In this conversation, it\u2019s most helpful to state what you think happened and how it may have impacted them, explicitly own your part in it, and ask them how it landed for them. Be open to receiving their experience and feedback and let that conversation lead into a recalibration.<\/p>\n That openness and ownership will lead to more trust on the team and more constructive conflict down the line.\u00a0<\/p>\n Listen to the full episode of Build Mode for more tactical advice for building your team.<\/p>\n Apply to Startup Battlefield:<\/strong><\/a> We are looking for early-stage companies that have an MVP. So nominate a founder (or yourself). Be sure to say you heard about Startup Battlefield from the Build Mode podcast. Apply here<\/a>.<\/p>\n TechCrunch Disrupt 2026:<\/strong><\/a> We\u2019re back for TechCrunch Disrupt on October 13 to 15 in San Francisco, where the Startup Battlefield 200 takes the stage. So if you want to cheer them on, or just network with thousands of founders, VCs, and tech enthusiasts, then grab your tickets<\/a>.<\/p>\n Use code buildmode15 for 15% off any ticket type.<\/strong><\/p>\n Isabelle Johannessen is our host. <\/em>Build Mode<\/em><\/a> is produced and edited by Maggie Nye. Audience Development is led by Morgan Little. And a special thanks to the Foundry and Cheddar video teams.<\/em>\u00a0<\/p>\n<\/div>\nPause and do an \u201cinternal 360\u201d on what just happened<\/h2>\n
Connect this incident to a pattern<\/h2>\n
\n\t\t\t\t\t\t\t\t\t\t\t\t\t|<\/span>
\n\t\t\t\t\t\t\t\t\t\t\t\t\tOctober 13-15, 2026<\/span>\n\t\t\t\t\t\t\t<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/div>\nGo to others who were impacted<\/h2>\n