'Tell Me About a Time You Made an Unpopular Decision' Interview Answer: Examples

An unpopular-decision story works when it has four parts: the decision and why it had to be made, who disagreed and what you genuinely listened to, how you explained it, and what happened afterwards, including whether you were right. It is a close relative of a time you made a difficult decision, the explaining part is the skill in delivering bad news, and the way you tell it should match your answer to what is your leadership style. This page explains what the interviewer is really asking, gives a structure that works, three sample answers of forty to eighty words to adapt, the mistakes that sink the answer, and a ten-minute practice routine.

What the interviewer is asking

Whether you can make a call that costs you approval, whether you listen to disagreement without being governed by it, whether you can explain a decision in a way that keeps people with you even when they dislike it, and whether you are honest about outcomes. Interviewers for management roles ask it because popular decisions do not need a manager. They also listen for the opposite failure: a candidate who enjoys being unpopular, or who tells a story where everyone was wrong except them. The strong answer shows reluctance, listening, clarity and an honest result.

A structure that works

1. The decision and the reason: what had to change and what would have happened otherwise.
2. The disagreement: who, why, and what you took from it, even if it did not change the decision.
3. How you explained it: in person, with the reasoning, and what you offered to soften the cost.
4. What happened: the result, how people felt later, and what you would do differently.

Three sample answers

Manager

I cancelled a team's long-standing Friday remote day for six weeks during a system migration, because the issues were being found in the office and fixed on Monday. Nobody liked it, and two people told me so directly. I listened, and I took one thing from it: I set the end date in writing on day one so it did not become permanent by drift. I explained the reason in a team meeting rather than by email, and I came in every one of those Fridays myself. The migration finished on time, the remote day came back as promised, and the team told me afterwards that the end date was what made it bearable.

Project

I pulled a feature the sales team had promised to a customer from a release, because it had failed testing twice and shipping it would have broken two other customers. Sales were furious and the account manager escalated to my director. I did not relitigate the testing; I showed the results, I offered a date for the feature in the next release, and I offered to join the call with the customer, which I did. The customer was annoyed for a week and the release went out clean. If I had shipped it, we would have had three unhappy customers instead of one.

Frontline lead

As a shift lead I changed the break rotation so that the two most experienced people were never on break at the same time, which meant some people lost the break slot they had had for years. Several told me it was unfair. I listened and I adjusted the rotation so everyone got their preferred slot at least twice a week, which I had not thought of, but I kept the rule. The reason was a bad incident during a double break, and I said that plainly. Within a month nobody mentioned it, and the incidents stopped.

Mistakes that sink the answer

• A story where you ignored all disagreement and were vindicated; it reads as stubbornness.
• No reason the decision had to be made.
• Explaining the decision by email or not at all.
• A decision that turned out badly, told without learning.
• Enjoying the unpopularity.

A ten-minute practice routine

1. Pick one decision that was genuinely necessary and genuinely unpopular, and write the reason in one sentence.
2. Write what the disagreement taught you, even if it did not change the decision.
3. Add how you explained it and what you offered, and the honest result.
4. Say it aloud in under ninety seconds, without edge.
5. Answer it in the browser demo or a mock interview and compare with the structured answer.

Where CoPilot Interview fits

CoPilot Interview is an AI interview assistant whose browser demo at /try lets you answer this question aloud and compare your answer with a structured one, free and with no signup, and whose free AI mock interview asks it in the context of your résumé and the job description and scores your spoken answer out of ten. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Practice is the use nobody objects to; if you consider live help in a real interview, follow your employer's rules.

Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.

Frequently asked questions

How do you answer 'tell me about a time you made an unpopular decision'?

The decision and why it was necessary, who disagreed and what you took from them, how you explained it in person and what you offered to soften the cost, and the honest result.

Should the decision have turned out well?

Ideally, yes, but an honest story with a mixed result and a clear lesson is stronger than a flawless one that sounds invented.

What if I have never made an unpopular decision?

Most people have made a small one: a schedule, a rule, a cancelled plan. Small is fine if it was real and you can show the four parts.

How long should the answer be?

Sixty to ninety seconds.