Conflict Resolution in Teams

Conflict is inevitable in high-pressure startups. Your job as a leader is to move the team from "Me vs. You" to "Us vs. The Problem."

Task vs. Relationship Conflict

• Task Conflict: "I think we should use Postgres." vs. "I think we should use MongoDB." (Healthy)
• Relationship Conflict: "You always pick the wrong database because you don't know what you're doing." (Toxic)

De-escalation Phrases

If a meeting gets heated, use these "Cooling" phrases:

• "Let's pause for a second and make sure we're all talking about the same thing."
• "I hear your concerns about the timeline, and I also hear [Name]'s concerns about quality."
• "What's the middle ground here?"

The "I Statement"

Teach your team to use "I statements" to avoid sounding like they are attacking:

• Attack: "You didn't test your code!"
• I Statement: "I feel frustrated when the build breaks because it slows down the whole team."

Finding the "Win-Win"

• "If we go with your architecture, can we still hit the Friday deadline?"
• "How can we incorporate both of these ideas into the MVP?"

Alex's Tip: If two people are stuck in a loop, use the "Five Whys" technique. Ask "Why?" five times to get to the root of the disagreement. Often, it's not about the code; it's about a lack of clear requirements.

• The way you handled that client call showed real seniority.

Specific recognition is motivating because it shows you noticed the actual work, not just a vague good job.

Language for improvement

Be specific and forward-looking in criticism:

• In Q3, two tickets slipped without early warning. In the next period, I'd like us to flag risks earlier so the team can adjust. How can I support you with that?

This names the evidence, the expectation, and the support. It is firm but constructive.

The career conversation

After the review, discuss growth:

• Where do you want to be in 12 months?
• What skills do you want to build?
• What projects would stretch you?
• How can I support your growth?

These questions show you care about the person's career, not just their output. Career conversations are one of the strongest retention tools a manager has.

Common mistakes

1. Surprise criticism. Serious feedback must be given earlier, not first at the review.
2. Vague impressions. Cite specific examples with outcomes.
3. No future focus. A review that only looks backward misses the chance to motivate and develop.

Practice

Take one piece of feedback you would give a teammate. Rewrite it as evidence-based:

1. Situation/example: _
2. Impact: _
3. Forward-looking ask: _

Example: In the last sprint, the API docs were not updated with the release (example), which caused two support tickets from the mobile team (impact). Next release, could we update the docs as part of the definition of done? (ask)

In the next lesson, you will learn the English of hiring and interviewing candidates.