惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

MyScale Blog
MyScale Blog
F
Fortinet All Blogs
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
D
Docker
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
爱范儿
爱范儿
V
Visual Studio Blog
Last Week in AI
Last Week in AI
WordPress大学
WordPress大学
aimingoo的专栏
aimingoo的专栏
小众软件
小众软件
L
LangChain Blog
Vercel News
Vercel News
阮一峰的网络日志
阮一峰的网络日志
IT之家
IT之家
P
Proofpoint News Feed
博客园_首页
D
DataBreaches.Net
T
The Blog of Author Tim Ferriss
The GitHub Blog
The GitHub Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
C
Check Point Blog
Engineering at Meta
Engineering at Meta
Microsoft Azure Blog
Microsoft Azure Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Team Conflict in the Open
Lavkesh Dwivedi · 2026-06-20 · via DEV Community

Originally published on lavkesh.com


As a team leader, you can't avoid conflicts forever. They'll arise eventually, whether it's about a project, approach, or personalities. Ignoring them only makes things worse, causing people to take sides and the conflict to spread.

The moment you notice tension, address it directly, but not aggressively or publicly. Acknowledge the issue and express your desire to help resolve it. People respect directness more than avoidance.

Before intervening, understand the root cause of the conflict. Is it about work style differences, unclear expectations, or past resentments? Talk to each person separately, letting them vent and actually listen. Ask questions to clarify their concerns and what they're really upset about.

I've seen this play out many times, for example, when two team members at a previous company, John and Mike, couldn't agree on the architecture for a new feature. They both had valid points, but their communication was breaking down. I stepped in, spoke with each of them separately, and then facilitated a joint conversation. It turned out the issue was not the technical details, but rather the fact that they had different priorities, with John focusing on scalability and Mike on maintainability. Once they understood each other's priorities, they were able to find a compromise that met both needs.

People often don't surface the real issue until they feel heard. They might say they're mad about a code review but mean they feel disrespected or untrusted. Your goal is to understand both sides, not to judge.

Facilitate a real conversation by setting ground rules, such as no interrupting or personal attacks. Let each person share their perspective, and you stay calm and neutral. If someone's trying to win an argument, pull them back. This can be challenging, especially when the conflict involves strong personalities or high stakes. I recall a situation where two team leads, Rachel and Chris, were at odds over a project timeline. The tension was palpable, and it took some effort to get them to listen to each other. But once they did, they were able to find a solution that worked for both of them.

In my experience, tools like Slack or Microsoft Teams can be both a blessing and a curse when it comes to conflict resolution. On the one hand, they provide a record of conversations and can help to clarify misunderstandings. On the other hand, they can also facilitate the spread of misinformation and rumors. It's essential to be mindful of these dynamics and to use these tools judiciously.

The breakthrough usually happens when each person hears the other's perspective and realizes it's not what they thought. There was just a miscommunication that spiraled. Look for common ground, like shared goals and values.

I've found that using techniques like active listening and open-ended questions can help to facilitate this breakthrough. For example, asking questions like 'What do you think is the root cause of this issue?' or 'How do you think we can work together to resolve this?' can help to get people thinking about the problem in a more collaborative way. Additionally, using tools like shared documents or collaborative note-taking apps can help to ensure that everyone is on the same page.

Call out the things you notice they agree on, reminding them they're on the same team. This foundation helps them work together professionally, even when disagreeing. It's also important to recognize that conflicts can be an opportunity for growth and learning. By working through difficult issues, teams can develop stronger relationships and a deeper understanding of each other's strengths and weaknesses.

Collaborate on a solution by asking them to come up with one together. 'What would make this better?' or 'How do we prevent this in the future?' Get them problem-solving together. This can be a challenging process, but it's essential for building trust and ensuring that the solution is sustainable. I've seen teams use techniques like design thinking or agile methodologies to facilitate this process, with great success.

The solution matters less than the fact that they came up with it together. They're more likely to follow through on something they agreed to. This is because they have a sense of ownership and investment in the solution, which can help to drive motivation and engagement.

Clarify expectations going forward, making it explicit who's responsible for what and how disagreements should be handled. This is also when you clarify team values, such as how to handle disagreements and earn trust. It's essential to document these expectations and values, so that everyone is on the same page and can refer back to them as needed.

Know when to get help if the conflict is rooted in something systemic, like discrimination. Involve HR or get professional help. Don't try to be the therapist. It's also important to recognize that conflicts can be a symptom of deeper issues, such as a lack of diversity or inclusion. By addressing these underlying issues, teams can create a more positive and supportive work environment.

Follow up genuinely a week later, checking in on how things are going. Celebrate their achievement if they worked through something hard and came out respecting each other more.