Defending a Decision Others Opposed: What Was the Outcome?

How to answer "describe a time you defended a decision others opposed": what it tests, a sample answer with notes, two follow-ups and common mistakes.

The full question runs: describe a time when you had to defend a decision you made even though others were opposed to it. What was the situation, what did you do, and what was the outcome? The interviewer is checking two things that pull against each other. Did you hold a position under pressure, for reasons you can explain? And did you actually listen to the people who disagreed, and test your view against theirs? Pick a decision that was genuinely yours, describe the opposition fairly, and save real time for the outcome: what happened to the work, what happened with the people who opposed you, and what you would do differently.

What the question tests

Published hiring frameworks put the two halves side by side.

• Amazon has a principle for each half. "Have Backbone; Disagree and Commit" says leaders "have conviction and are tenacious" and "do not compromise for the sake of social cohesion". "Are Right, A Lot" says they "seek diverse perspectives and work to disconfirm their beliefs". A strong answer shows both: you stood firm, and you went looking for the reasons you might be wrong.
• The UK Civil Service Success Profiles list, under Leadership at Grade 6 and 7, "stand by, promote or defend your own and your team's actions and decisions where needed". The same list also includes "welcome and respond to views and challenges from others, despite any conflicting pressures to ignore or give in to them".

Jeff Bezos's 2016 letter to shareholders adds an angle for the person holding the decision: with conviction but no consensus, ask the others whether they will "gamble with me on it". The goal is commitment, not agreement. Your story does not need everyone to end up agreeing with you. It needs them to have been heard, and then to have backed the decision anyway.

How the bar rises with seniority

The Civil Service framework shows how the same behaviour is expected at increasing difficulty. Under Making Effective Decisions:

• Grade — What the indicator asks for
• HEO and SEO — "display confidence when making difficult decisions, even if they prove to be unpopular"
• Grade 6 and 7 — "make decisions confidently even when details are unclear or if they prove to be unpopular"
• Director and Director General — "when required, be able to make unpopular decisions and defend them at the highest level"

The US Office of Personnel Management's structured interview guide uses a similar logic in its general rating scale: higher levels apply a competency in more difficult situations, from "the simplest situations" at level 1 to "exceptionally difficult situations" at level 5.

So match the story to the job. For an entry-level role, a decision about a group project, a shift rota or a customer is fine. For a manager, the opposition should include peers or your own manager, and the evidence should have been incomplete when you decided. For a senior role, expect to need stakes beyond your team. A well-told story that is too small for the level can still score low.

Picking the story

Check four things before you commit to an example.

1. The decision was yours. You owned it or were asked to make the call. Agreeing with your boss while others pushed back is a different story.
2. The opposition had a point. If the people against you were simply wrong or difficult, the interviewer learns nothing about how you weigh a real objection. You should be able to state their case in one fair sentence.
3. You can say why you held firm. Evidence, a constraint the others could not see, or a risk you judged bigger than theirs. "I just knew" is not a reason.
4. You know how it turned out. If the outcome is still unclear, pick another story.

Avoid stories where you won by pulling rank, or where the "decision" was really following a rule or law (that is an integrity question).

A sample answer, with notes

This is an illustrative answer for a recruiting lead, not a real person's story. Use your own facts; a borrowed story falls apart under follow-up questions.

Situation. I ran recruiting for a customer support team that needed twelve new agents before the holiday peak. Our process included a written exercise: candidates replied to three real, anonymised customer emails. Two hiring managers wanted to drop it. Candidates were falling out of the process, and they were worried about empty seats in November.

What I did. The process was mine to set, so the decision was mine. Before deciding, I looked at where candidates were actually dropping out. Most of the loss was in the days between the phone screen and the exercise, not in the exercise itself. The year before, we had hired a seasonal group without it, and the team leads had spent weeks rewriting those agents' replies. So I kept the exercise, but I cut it from three emails to two and let candidates do it straight after the phone screen instead of booking a separate slot.

I met both managers, explained the decision and the drop-off data, and told them what would make me reverse it: if we were still behind the hiring plan by mid-October, we would drop the exercise for the remaining roles. One manager still disagreed. I asked him to run with it until that checkpoint, and he agreed.

Outcome. We did not need the checkpoint. Ten seats were filled by the deadline and the last two in the first week of the peak, so we were slightly late. The team leads said the new group needed far less help with written replies than the previous year's. The manager who had pushed back hardest asked to use the same exercise for his next round. What I would do differently: I showed the managers the drop-off data after I had decided, and the first meeting felt to them like a done deal. Sharing it before deciding would have cost me nothing and saved some goodwill.

Why this works:

• The opposition is stated fairly. The managers' worry (empty seats at peak) was real, and the answer says so.
• The candidate tested the objection before deciding. Checking where people dropped out is the "disconfirm your beliefs" half of the question.
• Holding firm did not mean changing nothing. The core decision stayed; the exercise got shorter and faster. That shows listening without giving in.
• A reversal condition was set in advance. Saying what would change your mind is the clearest sign that you were defending a judgement, not your ego.
• The outcome has three parts. The result for the work (including that it was slightly late), the result for the relationship, and an honest lesson.

Spoken aloud this runs about two minutes. If yours runs long, shorten the situation, not the outcome.

What was the outcome? Getting the last part right

The outcome is where many answers go soft. OPM's guide lists "What was the outcome?" as a standard probe, and the next probe on the same list is "Is there anything you would have said and/or done differently?" Oregon's Department of Consumer and Business Services notes on the STAR method that candidates often have to be prompted for their results, and advises including them without being asked.

A complete outcome covers:

• The result for the work, in concrete terms. Numbers help if you have them; a clear before-and-after works if you do not.
• What happened with the people who disagreed. Did they commit? Did the working relationship survive? This is the part most candidates leave out.
• A lesson that would change your behaviour next time, not a general statement about communication.

If the decision turned out to be wrong, you can still use the story. The same Oregon guidance notes that an example with a negative result can highlight your strengths in the face of adversity. Say what you saw, when you changed course, and what you now check before making a similar call. Told well, that can be more convincing than a story where you were proven right on every point.

Two follow-ups to prepare

"Is there anything you would have done differently?" Have a real answer, not "no", and make it about your own conduct: involving people earlier, setting a review date, or explaining the trade-off in writing. Do not blame the people who opposed you.

"What would have made you change your mind?" If you set a reversal condition, say so. If you did not, name the evidence that would have persuaded you. An answer of "nothing" tells the interviewer you were defending your position, not the outcome.

Common mistakes

• Making the opponents the villains. It suggests you will describe your new colleagues the same way.
• Treating winning as the outcome. "They eventually admitted I was right" is about you, not the work.
• Pulling rank. "I was the manager, so I made the call" skips the part being tested: how you persuaded people.
• Changing nothing. If no part of the objection affected your plan, it sounds as if you were not listening.
• Saying "we" throughout. Oregon's STAR guidance says to use "I", not "we". The decision was yours, so tell it that way.

Variations you may hear

The same story often answers "describe a situation where you were not in the majority", "tell me about an unpopular decision you made" and "describe a time you had to make a difficult decision". For the first, you may not have been the decision-maker. If you argued against a decision someone else made, the approach in how to answer the bad policy interview question fits better. For "a difficult decision", spend more time on the trade-off you weighed and less on the opposition.

Some written assessments test the same idea with a multiple-choice item: you are sure a pricing change is the right fix, others disagree, and you must pick the most emotionally intelligent way to say so. Replies that dismiss the others' view, or declare your fix the only answer, miss the point. A reply that presents your idea as one option you would like the group to explore keeps your conviction while inviting challenge, which is the same balance this interview question looks for.

If you are also preparing what frustrates you at work, check that the two answers do not contradict each other.

Practising it

Write the story in three parts (situation, what you did, outcome), with the outcome split into work, people and lesson. Say it aloud, time it, then ask someone to put the two follow-ups to you without warning. If you use Verve AI's Interview Copilot, you can save stories like this in STAR format in its Knowledge Base, and the copilot draws on the documents you have enabled when it suggests answers.

For more questions written the same way, browse the interview question bank.

Sources

• Amazon Leadership Principles ("Have Backbone; Disagree and Commit" and "Are Right, A Lot" wording): https://www.amazon.jobs/content/en/our-workplace/leadership-principles
• Jeff Bezos, 2016 letter to shareholders ("disagree and commit", "gamble with me on it"): https://www.aboutamazon.com/news/company-news/2016-letter-to-shareholders
• UK Civil Service Success Profiles behaviours (Leadership at Grade 6/7; Making Effective Decisions at HEO/SEO, Grade 6/7 and Director/DG): https://www.gov.uk/government/publications/success-profiles/success-profiles-civil-service-behaviours
• US OPM, Structured Interviews: A Practitioner's Guide, September 2008 (Table 1 rating scale; Table 4 outcome probes): https://www.opm.gov/policy-data-oversight/assessment-and-selection/structured-interviews/guide.pdf
• Oregon DCBS on the STAR method (results often need prompting; negative results; "I" not "we"): https://www.oregon.gov/DCBS/jobs/Pages/the-STAR-method.aspx
• Verve AI Knowledge Base (STAR-format entries, enabled documents): https://docs.vervecopilot.com/features/knowledge-base