Managing Conflicts Constructively

How to disagree without falling out? It’s a crucial skill, in life and at work. And it is a topic that is close to my heart. I sometimes struggle to disagree with friends, family and colleagues without hurting relationships. So I invited Harvard's Julia Minson to join me on Speak Like a CEO, and she reveals why smart people struggle with conflict. Her insights surprised me: 💡The 'Winning' Illusion  We try to win the argument instead of trying to understand the other side.  This sabotages conversations and hurts the relationship. 💡Go beyond listening  Actively try to understand where the other person is coming from.  Signal “I am interested, help me understand.”  Say: “Tell me where you are coming from” 💡Disagree with grace   “I see it differently for x and y reasons, and that’s ok.” 💡"The 'HEAR' Framework for receptive communication. Hedging: “I think …” or “It may be that…” Emphasizing Agreement: “We both want to ..” or “I also think it is important…” Acknowledgement: “I understand that x is really important to you.” Reframing to the Positive: “You don’t” with “I like that you …” 💡Conversations have history.  Manage your emotions. Have a cheat sheet ready how you want to react when the same topic comes up. 💡Build a culture where disagreement leads to innovation not conflict. Train whole teams in disagreement to shift the culture fast. Disagreement must not be personally costly.  Foster a space where disagreement leads to innovation. Listen to the full episode on Apple or Spotify. ♻️ Please share with your network to help others disagree better. 📌 Follow me, Oliver Aust, for daily tips on leadership communication.

It might not look like it, but I’m actually quite approachable. Not when I’m grilling candidates on The Apprentice, perhaps, but definitely in work situations. I’m particularly mindful of creating a collegiate, non-threatening environment where colleagues feel safe sharing ideas, concerns, and especially mistakes. Here are four actionable ways you can enhance approachability and build trust with your team: 1. Be present and visible Approachability starts with visibility. If your team rarely sees you or feels they’re intruding when they do, they won’t speak up. Walk the floor, join informal conversations, and make time for spontaneous interactions. Your presence signals you’re open to hearing them, even outside formal meetings. 2. Think aloud and invite the input of others Explain your reasoning — and uncertainties — when making decisions. This creates space for others to contribute ideas or challenge assumptions. During meetings, outline options and explicitly ask for input. This builds trust and shows you value diverse perspectives. 3. Admit to your own mistakes Leaders who own their errors make it safer for others to do the same. Share a recent mistake in a team debrief and what you learned from it. This “models imperfection” and encourages a culture of learning from failure. 4. Use debriefs as learning moments After key projects or challenges, organise post-mortem meetings to review outcomes. Ask open-ended questions like, “What could we have done differently?” or “What should we carry forward next time?” These sessions will also repair tensions from stressful moments. Approachability is a leadership skill like any other. It takes effort and focus. But by fostering openness, you’ll build stronger relationships, improve performance and create a culture of trust. What techniques have you seen that bring out the best in people?

Many senior leaders I work with care deeply about innovation. And still, they experience a tension they don’t always state out loud. Control vs. curiosity. Alignment vs. disagreement. They know innovation doesn’t come from everyone just doing what they’re told. But they also believe that too much freedom, without enough structure, can quickly turn into chaos. What they often do not realize is that they do not need to pick a side. Instead, they need to learn how to hold both at the same time. In my work, I’ve seen that innovative teams don’t try to get rid of dissent. They embrace it and shape it. And they don’t just tell people to “be curious.” They use practices that make curiosity possible, every day. Here are a few principles that help leaders navigate this tension: 1. Keep dissent about ideas, not people. The best debates focus on the work: the data, the assumptions, the trade-offs. Not egos, titles, or who’s “right.” When leaders stay open (especially when they’re being challenged) it gives everyone else permission to do the same. 2. Give curiosity clear boundaries. Curiosity actually works better with structure. Be clear about where experimentation is encouraged, what constraints matter, and when decisions are final. Too much freedom without clarity is overwhelming. Clarity creates room to explore. 3. Don’t mix learning moments with performance moments. If every conversation feels like a test, people stop taking risks. Say out loud when the goal is learning, reflection, or trying things out. And protect those spaces. 4. Reward contribution, not agreement. If people get ahead by agreeing, that’s what they’ll do. If they get ahead by improving thinking, raising risks, and expanding options, you’ll get better decisions. 5. Remember: culture follows behavior, not demands or promises. Curiosity isn’t what leaders say they want. It’s what they notice, what they ask about, and what they act on, especially when things get tense. To me, innovation does not mean letting go of control. It’s about using control more thoughtfully, in ways that leave room for learning, challenge, and discovery. Leaders who get this right build teams and organizations that keep learning long after today’s problems are solved. #teams #collaboration #control #innovation #rules #practices #tension #learning #leadership

"Most leaders think their teams need to get better at change. The truth? Their teams need to get better at disagreeing." Across SEA, stakeholders keep telling me: "We can handle change. We just can't handle how fast everything changes." But here's what I see when I dig deeper: Teams don't break because change happens. Teams break because they can't adapt together. And the World Economic Forum December 2025 report confirms this: Flexibility will be critical economic skills from 2026–2030. Not new frameworks. Not better tools. Human capabilities. COMB has been solving this exact problem for nine years, long before WEF made it official. Earlier this year, I worked with a cross-functional team in crisis where marketing said product was too slow. Product said operations was too rigid. Operations said everyone dumped last-minute requests. Leadership labeled it "lack of adaptability." But during our COMB session, the real issue surfaced: A manager said honestly: "We don't struggle with change... We struggle because we don't trust how people will respond when we speak honestly." That was it. Teams cannot adapt to external uncertainty when they feel unsafe with internal uncertainty. Because adaptability isn't just technical. It's emotional. When people don't feel safe, they: ❌ Won't challenge ideas ❌ Won't ask crucial questions ❌ Won't disagree constructively ❌ Won't reveal blindspots ❌ Won't collaborate at speed This is why psychological safety isn't "soft culture work." It's the backbone of competitive advantage. For nine years, COMB has been developing what we call "soft power skills", the human capabilities that drive organizational adaptability. Long before WEF identified flexibility as critical, we've been training teams across Indonesia and Singapore to master constructive conflict, emotional regulation, and trust-building under pressure. Most teams avoid conflict because they only know destructive conflict: defensive reactions, personal attacks, shutdowns. But we teach the real engine of adaptability: Constructive conflict. Where teams learn to say: "I see it differently, here's why" or "Help me understand your constraints." When teams master constructive conflict: �� Speed increases dramatically 💥 Decision-making sharpens 💥 Innovation accelerates 💥 Client communication improves 💥 Silos dissolve naturally Because trust isn't built when people agree. Trust is built when people can disagree safely. What the WEF identifies, COMB operationalizes. From 2026–2030, companies will rise or fall on one capability: how well their people adapt to uncertainty together. Lead Beyond Yourself. Rise Beyond Limits. If your teams hesitate, avoid difficult conversations, or slow down when the world speeds up — is it really a skills issue or a safety issue? Ready to build adaptability as your competitive edge? Let's talk. #softpowerskills #teamadaptability #psychologicalsafety #futureskills #organizationalchange #cassandracoach

𝑨 𝒕𝒆𝒂𝒎 𝒎𝒆𝒆𝒕𝒊𝒏𝒈 𝒈𝒐𝒏𝒆 𝒘𝒓𝒐𝒏𝒈. 𝑨 𝒍𝒆𝒔𝒔𝒐𝒏 𝒐𝒏 𝒍𝒊𝒔𝒕𝒆𝒏𝒊𝒏𝒈 𝒕𝒉𝒂𝒕 𝒔𝒕𝒂𝒚𝒔 𝒇𝒐𝒓 𝒍𝒊𝒇𝒆. 🎧 Tension filled the room. The cross-functional team was meeting after a major project miss, and everyone was on edge. One voice broke the silence. “This failed because your team didn’t deliver on time.” Instant defensiveness. “That’s not true — we were waiting on inputs from you.” Voices rose, emotions ran high, and listening turned into waiting for a pause to defend. Finally, the project leader stepped in quietly and said — “Can we pause for a second? I want to really understand what happened — not who to blame.” The energy shifted. There was a moment of silence. Then one person spoke — “Honestly, we didn’t know the priority had changed. We were still working on the older specs.” Someone else added, “I didn’t realize that. That explains why timelines slipped.” In that instant, blame turned into clarity, defensiveness into dialogue. No one had to “win” the conversation — they just had to listen to understand. That’s what active listening does — it transforms conflict into connection. 💡 𝗞𝗲𝘆 𝗧𝗮𝗸𝗲𝗮𝘄𝗮𝘆𝘀 1. Most leaders hear to respond; few listen to understand. 2. Active listening diffuses tension, builds safety, and enables truth. 3. Listening isn’t passive — it’s a leader’s most powerful tool 🪞𝗥𝗲𝗳𝗹𝗲𝗰𝘁𝗶𝗼𝗻 𝗣𝗿𝗼𝗺𝗽𝘁𝘀 𝗳𝗼𝗿 𝗟𝗲𝗮𝗱𝗲𝗿𝘀 1. When was the last time you caught yourself listening just to reply? 2. What if your next response started with curiosity, not defense? 3. How would your team conversations change if everyone felt truly heard? As we continue The Inner Edge: Team Leadership Series, we’ll explore how authenticity and empathy shape stronger teams and braver leaders. 📩 Subscribe to 𝑻𝒉𝒆 𝑰𝒏𝒏𝒆𝒓 𝑬𝒅𝒈𝒆 — your weekly lens into modern leadership, mindset, and meaning. #TheInnerEdge #TeamLeadership #ActiveListening #LeadershipDevelopment #EmotionalIntelligence #hr

🔹 Day 9 – Product Manager Interview Prep Series 🔹 Behavioral-Based Question 📌 Q: How will you manage a conflict or disagreement within your team? 🧠 Why is this question asked? Product Managers work at the center of cross-functional teams, where disagreements are inevitable—whether it’s with designers, engineers, or stakeholders. This question tests your emotional intelligence, communication skills, and ability to drive alignment without authority. Great PMs don’t avoid conflict — they manage it constructively. 🛠 How to approach it: Structure your answer with STAR method: Situation – Set the context Task – What was your role/responsibility Action – What steps did you take Result – What was the outcome Focus on these themes: • Active listening • Staying neutral and empathetic • Aligning on shared goals • Facilitating collaboration over forcing decisions • Avoid blaming or emotional reactions • Show maturity, patience, and people-first thinking ✅ Sample Answer: “In one of my past roles, I was driving a critical feature launch under intense time pressure. A disagreement arose between the design and engineering teams — design wanted a sleek interaction that required custom components, while engineering raised concerns over tech debt and timeline risk. I scheduled a joint session, where I gave both sides equal space to share their perspectives. I reframed the discussion around the shared goal: delivering a user-friendly solution without compromising quality or deadlines. We brainstormed a simplified version that retained the core experience and could be reused across modules, pleasing both teams. This experience taught me the power of listening first, aligning on objectives, and creating a safe space for compromise. The feature shipped on time and became one of our highest-rated experiences.” 💡 Pro Tip: Conflict isn’t a red flag — it’s a natural part of product development. What matters is how you de-escalate and bring people together. Highlight your ability to be the bridge, not the boss. 💬 How do you usually handle disagreements at work? Share your experiences 👇 #PMInterviewPrep #ProductManagement #BehavioralQuestions #ConflictResolution #LeadershipSkills #Teamwork #ProductThinking #LinkedInNewsIndia #Leadership #Teamwork #Collaboration #CareerGrowth #PMLife

Sometimes, I fight with my co-founders. We’re all opinionated and stubborn – but over time, we’ve found a solution that works for us. We developed a simple framework to guide us through conflicts: identify whose domain a decision falls under and give them the final say if we can’t agree. Here are some examples of cofounder conflicts we’ve faced and how we’ve resolved them. 1️⃣ If it’s a debate about some engineering decision, we can all share our opinions, but when push comes to shove, Prajwal has the final say. I personally hate Python and would have much rather preferred our backend in Node.js, but Prajwal insisted on Python, and I had to trust his judgment. He knew what he was doing. 2️⃣ When it comes to pricing strategy or sales motions, it’s Neel's call. More than once, I’ve questioned Neel's decision to say no to certain customers, but he’s the one most deeply entrenched in the sales process every day, and he always has the final say. In hindsight, his intuition has been spot on. 3️⃣ When it comes to product and design — how our product and website look, feel, and function — that’s my domain. We’ve had some fiery debates about things as large as how to integrate a major new feature, to things as small as what color a button should be. Everyone brings valuable perspectives, and I love hearing their opinions, but ultimately, it’s my role to gather that input and make the final call. It’s crucial to note that this doesn’t mean we make decisions in isolation. We still argue passionately and challenge each other. It’s only when we’re in a complete deadlock that we adopt this framework to move forward. One exercise we did recently that has really helped us is mapping out every key activity in the company — from tech architecture to customer feedback management to even organizing team parties. By explicitly defining our areas of ownership, we eliminated confusion and gave each of us the freedom to lead. The only way a system like this works is if there’s trust. If you’re constantly second-guessing your cofounders or unable to let go of certain decisions, it’s a sign that you haven’t built enough trust yet. Without that trust, you’ll either end up micromanaging each other or splitting your work inefficiently. #startups #cofounders

I once worked with a team that was, quite frankly, toxic. The same two team members routinely derailed meeting agendas. Eye-rolling was a primary form of communication. Side conversations overtook the official discussion. Most members had disengaged, emotionally checking out while physically present. Trust was nonexistent. This wasn't just unpleasant—it was preventing meaningful work from happening. The transformation began with a deceptively simple intervention: establishing clear community agreements. Not generic "respect each other" platitudes, but specific behavioral norms with concrete descriptions of what they looked like in practice. The team agreed to norms like "Listen to understand," "Speak your truth without blame or judgment," and "Be unattached to outcome." For each norm, we articulated exactly what it looked like in action, providing language and behaviors everyone could recognize. More importantly, we implemented structures to uphold these agreements. A "process observer" role was established, rotating among team members, with the explicit responsibility to name when norms were being upheld or broken during meetings. Initially, this felt awkward. When the process observer first said, "I notice we're interrupting each other, which doesn't align with our agreement to listen fully," the room went silent. But within weeks, team members began to self-regulate, sometimes even catching themselves mid-sentence. Trust didn't build overnight. It grew through consistent small actions that demonstrated reliability and integrity—keeping commitments, following through on tasks, acknowledging mistakes. Meeting time was protected and focused on meaningful work rather than administrative tasks that could be handled via email. The team began to practice active listening techniques, learning to paraphrase each other's ideas before responding. This simple practice dramatically shifted the quality of conversation. One team member later told me, "For the first time, I felt like people were actually trying to understand my perspective rather than waiting for their turn to speak." Six months later, the transformation was remarkable. The same team that once couldn't agree on a meeting agenda was collaboratively designing innovative approaches to their work. Conflicts still emerged, but they were about ideas rather than personalities, and they led to better solutions rather than deeper divisions. The lesson was clear: trust doesn't simply happen through team-building exercises or shared experiences. It must be intentionally cultivated through concrete practices, consistently upheld, and regularly reflected upon. Share one trust-building practice that's worked well in your team experience. P.S. If you’re a leader, I recommend checking out my free challenge: The Resilient Leader: 28 Days to Thrive in Uncertainty  https://lnkd.in/gxBnKQ8n

Promotion comes with a deadly risk: People stop correcting you. Not because you’re scary. Because you’re too sure. Blockbuster owned Friday nights. Nokia owned the phone. Kodak owned film. They didn’t lose because they weren't good. They lost because they thought they knew better than others did. I’ve lived the same pattern in many innovative companies. As leaders rise, friction disappears. 🚫 Meetings get “clean.” 🚫 Questions get shorter. 🚫 Pushback gets polite. Then it vanishes. You still feel informed. You’re just hearing less truth. Here’s what certainty does: 🚫 It turns disagreement into “they don’t get it.” 🚫 It trains the room to wait for your answer. 🚫 It makes new ideas feel like noise. That’s how judgment becomes a blind spot. And blind spots don’t hurt until the stakes are high. Leaders who hold up under change stay coachable. They listen early, not after the miss. Seven habits that keep the room honest: 1️⃣ Start with: “What am I missing?” Ask it before you argue. 2️⃣ Give dissent time. If someone pushes back, don’t rush past it. 3️⃣ Don’t take the last word. Leave space so the real issue can surface. 4️⃣ Treat “We tried that before” as a warning. New people. New context. Don’t assume the same difference. 5️⃣ Pull in the quiet voices. Ask them first. 6️⃣ Name your misses out loud. It tells the team truth won’t get punished. 7️⃣ Say “Why not try it” more often than “That won’t work” Stop debating. Start testing. Better questions beat confident answers. When the pace picks up and the heat rises, the best leaders stay teachable. When have you gotten a better outcome by letting go of the answer? ♻ Repost for the leaders who want more truth in the room. ➕ Follow Betsy Tong for frameworks on leading.

Avoiding conflict doesn’t prevent harm. It actually limits your team’s ability to do their best work. I often see this play out in the friction between fundraising and programs. Everyone’s trying to move fast, meet urgent needs, and serve the mission - sometimes without the full picture. I once worked with a brilliant, committed development lead. She worked tirelessly to unlock new resources. But sometimes, a fundraising win came at a quiet cost to the program team: fatigue, shifting priorities, and disrupted service delivery. I’ll never forget when she proposed a Saturday morning event involving direct-service staff and youth. It wasn’t an outrageous ask, but the timing was rough. The team was already stretched thin, and this extra commitment felt like too much in a moment of burnout. We’d hit an impasse. And as the Program Lead, I knew we had to address it head-on. I sat down with her and said: “𝘐 𝘩𝘢𝘵𝘦 𝘤𝘰𝘯𝘧𝘭𝘪𝘤𝘵. 𝘐𝘵 𝘨𝘪𝘷𝘦𝘴 𝘮𝘦 𝘢𝘯𝘹𝘪𝘦𝘵𝘺. 𝘉𝘶𝘵 𝘐 𝘸𝘢𝘯𝘵 𝘵𝘰 𝘶𝘴𝘦 𝘵𝘩𝘪𝘴 𝘮𝘰𝘮𝘦𝘯𝘵 𝘵𝘰 𝘴𝘵𝘳𝘦𝘯𝘨𝘵𝘩𝘦𝘯 𝘰𝘶𝘳 𝘸𝘰𝘳𝘬𝘪𝘯𝘨 𝘳𝘦𝘭𝘢𝘵𝘪𝘰𝘯𝘴𝘩𝘪𝘱. 𝘞𝘩𝘦𝘯 𝘵𝘩𝘦𝘴𝘦 𝘢𝘴𝘬𝘴 𝘤𝘰𝘮𝘦 𝘶𝘱, 𝘵𝘩𝘦𝘺 𝘤𝘢𝘳𝘳𝘺 𝘤𝘰𝘴𝘵𝘴 𝘵𝘩𝘢𝘵 𝘢𝘳𝘦𝘯’𝘵 𝘢𝘭𝘸𝘢𝘺𝘴 𝘷𝘪𝘴𝘪𝘣𝘭𝘦. 𝘐 𝘵𝘳𝘶𝘴𝘵 𝘺𝘰𝘶 𝘵𝘩𝘢𝘵 𝘵𝘩𝘦𝘺’𝘭𝘭 𝘢𝘥𝘷𝘢𝘯𝘤𝘦 𝘵𝘩𝘦 𝘰𝘳𝘨𝘢𝘯𝘪𝘻𝘢𝘵𝘪𝘰𝘯. 𝘉𝘶𝘵 𝘐 𝘯𝘦𝘦𝘥 𝘢 𝘭𝘪𝘯𝘦 𝘰𝘧 𝘴𝘪𝘨𝘩𝘵 𝘐 𝘤𝘢𝘯 𝘢𝘶𝘵𝘩𝘦𝘯𝘵𝘪𝘤𝘢𝘭𝘭𝘺 𝘢𝘭𝘪𝘨𝘯 𝘸𝘪𝘵𝘩. 𝘛𝘩𝘢𝘵’𝘴 𝘸𝘩𝘢𝘵 𝘩𝘦𝘭𝘱𝘴 𝘮𝘦 𝘩𝘢𝘷𝘦 𝘺𝘰𝘶𝘳 𝘣𝘢𝘤𝘬.” That conversation changed everything. Together, we created a simple tool: green flag, yellow flag, red flag - to assess new fundraising ideas based on programmatic organizational capacity. Conflict isn’t always about saying no. Sometimes it’s about learning how to say yes more intentionally, and together. If you’re facing tension on your team, don’t bury it. Use it to build trust and strengthen your capacity to lead. 𝐏𝐫𝐨𝐠𝐫𝐚𝐦 𝐟𝐨𝐥𝐤𝐬: 𝐰𝐡𝐚𝐭 𝐝𝐨 𝐲𝐨𝐮 𝐰𝐢𝐬𝐡 𝐟𝐮𝐧𝐝𝐫𝐚𝐢𝐬𝐞𝐫𝐬 𝐮𝐧𝐝𝐞𝐫𝐬𝐭𝐨𝐨𝐝? 𝐅𝐮𝐧𝐝𝐫𝐚𝐢𝐬𝐞𝐫𝐬: 𝐰𝐡𝐚𝐭 𝐜𝐨𝐧𝐭𝐞𝐱𝐭 𝐰𝐨𝐮𝐥𝐝 𝐡𝐞𝐥𝐩 𝐲𝐨𝐮 𝐟𝐞𝐞𝐥 𝐦𝐨𝐫𝐞 𝐬𝐮𝐩𝐩𝐨𝐫𝐭𝐞𝐝? Let’s trade notes and build better bridges.