Skip to content
Tutorials Center
My learning

Topics

Lesson 38 of 41 ยท Leadership and Stakeholders

Team Building and Conflict Resolution

Build a high-performing project team: Tuckman stages, team agreements, meeting health checks and the five conflict-resolution modes, with runnable Python examples.

A project team is a temporary group that must perform quickly, often with people who have never worked together and who report to different managers. Good team building shortens the time to productivity; good conflict handling keeps friction from turning into damage. Neither happens by accident.

Tuckman's stages of team development

In 1965 Bruce Tuckman described four stages (a fifth was added in 1977). Teams move through them, and they can fall back to an earlier stage when membership or goals change.

Five stages of a team

Forming Polite, unsure, depends on the leader.
Storming Disagreements about roles and methods.
Norming Agreed rules and trust.
Performing Efficient and autonomous.

Adjourning: the team disbands, celebrate and reflect.

1 / 2

Storming is not a failure. It is the team figuring out how to work together. Leaders who fear it and suppress it often get a fragile team that explodes later. Leaders who help the team talk through it reach performing faster.

Building the team

Practical team-building activities that work:

  1. Kick-off meeting. Share the goal, why it matters, scope, who does what, and how to communicate. Have everyone say something in the first ten minutes.
  2. Team charter (team agreement): values, decision rules, meeting rules, communication norms, how to handle disagreement. The team writes it, not the manager.
  3. Co-location or regular face-to-face time, even for remote teams: one in-person kickoff changes the relationship for months.
  4. Clear roles (a RACI) and shared goals.
  5. Recognition and rewards: specific, timely and meaningful to the individual.
  6. Training and mentoring, which also close skill gaps.
  7. Fun and social time, but not mandatory and not at the expense of caregivers.

Psychological safety

Google's research on team effectiveness (Project Aristotle) found that the strongest factor was psychological safety: team members believe they will not be punished for asking questions, admitting mistakes or disagreeing. You build it by admitting your own mistakes first, thanking people who bring bad news, and responding to errors with curiosity ("what did we learn?") instead of blame.

Team size and structure

Small teams (five to nine) communicate better: remember that channels grow as n(n-1)/2 (see communication management). Cross-functional teams, with all the skills needed to deliver, wait less on others. Agile teams are self-organizing; traditional teams may have a clear hierarchy with the manager assigning tasks. Both can perform when roles are clear.

Python Team health check survey

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Review the weakest items with the team in a retrospective, choose one improvement and re-run the survey in a month.

Conflict in projects

Conflict is normal and can be productive: disagreements about approach surface risks and better ideas. It becomes harmful when it is personal, hidden, or never resolved. Common sources of project conflict, roughly in order of frequency: schedules and priorities, resources, technical opinions, procedures and roles, cost, and personalities.

Conflict about tasks (what to do) helps; conflict about relationships (who someone is) hurts. A leader's job is to keep disagreements about the first kind.

The five conflict resolution modes

The Thomas-Kilmann model describes five modes, depending on how much you care about your own goals and the other person's.

Mode Also called When it fits
Collaborate Problem solve, confront Important issue, enough time; seeks win-win
Compromise Reconcile Moderate importance; both give something
Accommodate Smooth The issue matters more to the other; preserve the relationship
Compete Force, direct Emergency, or a safety or ethics matter
Avoid Withdraw Trivial issue, or to let emotions cool

Collaborating usually produces the most durable result, but not every conflict deserves the time. Forcing is a legitimate tool in emergencies, but used habitually it destroys trust.

Python Pick a conflict mode

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

A practical resolution routine

  1. Cool down if people are angry; meet privately, not in public.
  2. Listen to each side separately and repeat what you heard.
  3. Separate people from the problem and positions from interests.
  4. Define the issue in one neutral sentence.
  5. Generate options together; evaluate against shared criteria (goal, cost, time).
  6. Agree on a specific action and a review date; write it down.
  7. Follow up. If it flares again, escalate to a manager or an impartial mediator.

Use "I" statements ("I need the estimate by Tuesday") instead of accusations ("you always delay"). Ask open questions ("what would a good outcome look like?"). Focus on behaviors you can observe.

Difficult situations

  • A low performer: give specific feedback early, clarify expectations, offer support, document, and involve the line manager if it continues.
  • A dominant person: use round-robin turns, written input first.
  • A silent person: ask directly, give time to prepare, try one-to-one.
  • A conflict between you and the sponsor: use data, bring options, ask what they are trying to protect.
  • Virtual team friction: assume good intent, move sensitive topics to a call, and clear up misunderstandings quickly.

Team issues often trace back to unmanaged expectations from stakeholders, or to a leader's habits (project leadership).

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which Tuckman stage involves disagreement about roles and methods?

    In storming, differences in opinions and working styles surface; coaching and mediation help.
  2. 2. Which conflict mode seeks a win-win solution by solving the underlying problem?

    Collaborating combines concern for both parties' goals and is usually the most durable.
  3. 3. What did research on effective teams find to be the most important factor?

    Psychological safety lets people speak up, ask questions and admit mistakes.
  4. 4. A production outage needs an immediate decision. Which mode is justified?

    In emergencies the leader decides quickly and explains afterwards.

Summary

  • Teams develop through forming, storming, norming, performing and adjourning; leaders adapt their style.
  • Build teams with kick-offs, charters, clear roles, recognition and psychological safety.
  • Conflict about tasks is useful; conflict about people is damaging.
  • Five modes: collaborate, compromise, accommodate, compete, avoid; choose by importance, urgency and relationship.
  • Use a routine: cool down, listen, define, generate options, agree, follow up.

Next: Project Closure and Lessons Learned