How to Answer “How Do You Handle Conflict in a Team?”: Six Myths Tested Against the Evidence

Published · by JOBB GROUP FZE

“How do you handle conflict in a team?” is one of the most common behavioural questions, and it attracts a lot of recycled advice. Some of that advice makes answers worse. Below are six widely repeated beliefs about the question, each checked against research and guidance from employment and organisational sources, followed by a structure and two illustrative answers.

This guide is about conflict within a group: two colleagues who clash, a team split over an approach, or friction you had to help resolve as a member or lead. A personal clash between you and one coworker is a slightly different question and calls for a more personal story.

Myth 1: “Say your teams never really have conflict”

Fact: conflict is normal, and interviewers know it.

Acas, the UK’s workplace conciliation service, commissioned a survey of workers in Great Britain in 2025. It found that 44% of people had experienced conflict at work in the previous 12 months, and that the conflict was most commonly with a colleague in the same organisation. Acas described the 44% figure as the highest level of individual conflict at work ever reported in a survey of workers in Great Britain.

The data is from one country, but the point travels: an answer claiming your teams never disagree is not credible. It also suggests either low self-awareness or a habit of avoiding difficult topics. Start from the assumption that conflict happens and show how you deal with it.

Myth 2: “Disagreement about the work is always healthy; only personal conflict hurts”

Fact: the evidence is less comfortable than that.

A widely cited meta-analysis by De Dreu and Weingart, published in the Journal of Applied Psychology in 2003, combined studies on task conflict (disagreement about the work) and relationship conflict (personal friction). Contrary to the prediction that task conflict would help, both types were negatively associated with team performance, at roughly similar strength. Relationship conflict was more strongly linked with lower team member satisfaction.

The study found one important nuance: task conflict was less harmful to performance when it was only weakly connected to relationship conflict. In other words, disagreement about the work does less damage when it stays about the work.

For your answer, this means “I believe healthy conflict drives innovation” is a weak line on its own. A stronger point is how you keep a debate about methods, priorities or quality from turning personal: separating the issue from the people, agreeing criteria for a decision, and closing the debate once a decision is made.

Myth 3: “Keeping quiet keeps the peace”

Fact: unaddressed conflict tends to linger and cost people.

In the same Acas survey, around a fifth of people took no action over the conflict they experienced. Among managers whose conflict involved a direct report, 35% did nothing. Only half of respondents said their conflict had been largely or fully resolved, and the most commonly reported impact was stress, anxiety or depression (57%).

Acas’s training for people managers lists recognising “the importance of early intervention” as a learning outcome. Interviewers are looking for the same instinct. An answer in which you noticed tension and acted early, even with something as simple as a private conversation, is stronger than one in which you waited until it exploded.

Myth 4: “A good team member sorts everything out alone and never escalates”

Fact: knowing when to involve a manager is part of handling conflict well.

Acas found that the most common way people resolved conflict was through discussion with their own line manager (45%), while fewer than 10% used internal formal processes. Informal routes, including managers, do most of the work.

Competency frameworks reflect the same balance. The UK Civil Service’s Success Profiles, under the “Leadership” behaviour, expect staff at Higher and Senior Executive Officer grades to “effectively manage conflict, misconduct and non-inclusive behaviour, raising with senior managers where appropriate”. A balanced answer shows you tried to resolve the issue directly first, and that you would escalate if it involved conduct, safety, discrimination or a deadlock you could not break.

Myth 5: “A harmonious team is one where people do not disagree”

Fact: the healthier sign is that people feel safe to disagree.

Amy Edmondson’s 1999 study of 51 work teams in a manufacturing company, published in Administrative Science Quarterly, introduced the idea of team psychological safety: a shared belief that the team is safe for interpersonal risk-taking. Psychological safety was associated with learning behaviour, such as asking questions and discussing errors, and learning behaviour in turn helped explain team performance.

For an interview, this reframes the question. Handling conflict is not only about stopping arguments. It is also about making sure quieter team members can raise concerns, so problems surface early instead of festering. If you have ever invited dissent in a meeting, set ground rules for a debate or followed up privately with someone who disagreed but said nothing, that is worth mentioning.

Myth 6: “Only managers can give a good answer”

Fact: team members resolve a lot of conflict, and interviewers ask this question at every level.

You do not need formal authority to show conflict skills. Useful examples for individual contributors include: proposing a way to compare two competing approaches objectively; summarising both sides fairly in a meeting so they could be weighed; offering to pair with a colleague on the part of the work where the friction was; or suggesting a short trial to settle a disagreement with evidence rather than opinion.

The Civil Service framework’s description of working together at one senior grade includes the ability to “challenge assumptions while being willing to compromise if beneficial to progress.” Both halves of that phrase apply to team members as much as to managers.

A four-part structure that reflects the evidence

Use a real example in roughly the STAR order (situation, task, action, result), and make sure the action covers these four points:

  1. Diagnose. Was the conflict about the work, about roles, or about personalities? Show you worked this out before acting.
  2. Act early and privately first. Speak to the people involved before the issue becomes a team-wide problem.
  3. Move the debate onto shared criteria. Agree what a good outcome looks like, then compare options against it, so the discussion stays about the work.
  4. Close and follow up. Confirm the decision, check the relationship afterwards, and escalate if it did not hold.

End with a result someone could verify, such as a deadline met or a process agreed, and one thing you would do differently.

Illustrative answers

These are illustrative examples written for this guide, not real candidates’ answers.

As a team member

“On a website rebuild, our two senior developers disagreed about whether to refactor the old checkout or replace it. Meetings kept ending without a decision and the rest of us were blocked. I wasn’t leading the project, but I suggested we list what the business needed from checkout, such as launch date, risk and maintenance, and score both options against that list. I also spoke to each developer separately beforehand, because I could see the debate had started to feel personal. Once the criteria were agreed, the replacement option clearly won on maintenance and the developer who had argued for refactoring took ownership of the migration plan. We launched on schedule. I’ve since used the same approach whenever a technical debate stalls.”

As a team lead

“In my last role, two coordinators on my team were clashing over handovers. Each felt the other left work unfinished at shift change. I met each of them privately first to hear their side, then brought them together with the handover records. It turned out the template didn’t cover two common job types, so both were partly right. We redesigned the template together, and I checked in with both after two weeks. The complaints stopped. The lesson for me was to look for the process issue behind a personal conflict before assuming it’s about personalities. If it hadn’t settled, I’d have involved HR, but it didn’t need to go that far.”

Showing it on paper as well

Conflict-handling skills are easier to believe when your CV backs them up with outcomes: a cross-functional project delivered, a process redesigned, a team retention improvement. The resume examples library shows how to phrase collaboration achievements as results, and the project manager resume builder is set up for roles where stakeholder and team conflict are part of the job. Once the CV is drafted, an ATS resume score check can confirm that teamwork keywords from the job advert are present.

Frequently asked questions

Should I use an example where the conflict was not fully resolved?

It can work if you show what you did, what you learned and what you would do differently. Acas’s 2025 survey found only half of people said their conflict was largely or fully resolved, so an honest partial outcome is realistic. Avoid examples where you simply walked away.

Is it acceptable to mention involving HR?

Yes, particularly for conduct issues, harassment or discrimination, where escalation is the right response. Show that you tried an informal route first for ordinary disagreements, and that you knew when it was no longer appropriate.

What if I have never worked in a team?

Use group projects from study, volunteering or sport. The National Careers Service notes that examples can come from work, home or volunteering. Focus on what you did, not what the group did.

How long should the answer be?

About ninety seconds to two minutes for a behavioural question. Keep the situation short and give most of the time to your actions.

Sources

Ready to build your resume?

Start with a sample or a blank page. No sign-up needed. Free to edit; US$1.00 only if you download a PDF.

Build My ATS ResumeExplore Resume Templates