To answer “tell me about a time you challenged the status quo,” describe one accepted way of working that you questioned, the evidence that made you question it, how you raised it with the people who owned it, how you tested the alternative and what changed. Interviewers are checking judgment as much as courage: they want someone who challenges with evidence and tact, learns why the old way exists, and commits once a decision is made. The strongest answers end with a measured result and a fair word about the original approach.
What the interviewer is checking
Interviewers want courage without the opposite risk, someone who argues with everything. A good answer shows:
- Curiosity. You noticed a habit everyone else had stopped seeing.
- Evidence. You questioned it with numbers, observation or a reliable source, not a hunch.
- Respect. You challenged the practice, not the people who built it, and asked why it existed before proposing a change.
- Commitment. You went through the right channel and would have accepted a no.
- A result. Something measurably changed, and it lasted.
Amazon's Leadership Principles include “Have Backbone; Disagree and Commit,” which says leaders are obligated to respectfully challenge decisions they disagree with and to commit wholly once a decision is made (as published on Amazon's jobs site, checked November 2026). The NSW Public Sector Capability Framework (Version 3, 2026) lists “Display resilience and courage,” described as being open and honest and prepared to express your views, and the UK Civil Service Success Profiles include “Changing and improving.” Those panels often ask this exact question; see how competency-based interviews are scored.
Who asks it, and how it is phrased
| Interview type | How it is often phrased | What a good story usually challenges |
|---|---|---|
| Consulting, strategy, operations | “Tell me about a time you questioned how things were done.” | A report, approval step or assumption that cost time or money |
| Product, engineering, IT | “Describe a time you pushed back on an established practice.” | A tool, policy or default that no longer fit |
| Healthcare and public sector | “Give an example of when you challenged a long-standing practice.” | A routine that suited staff more than patients or the public |
| Retail, hospitality, contact centres | “Tell me about a time you suggested a better way to serve customers.” | A script, rule or target that was hurting the customer experience |
If you are interviewing at Amazon, expect the disagreement version; our Leadership Principles examples show how one story can serve several principles.
Choosing a challenge worth telling
The best story is a practice people defended, that you questioned with evidence, through a proper channel, with a result you can count. Good sources:
- A report, meeting or sign-off that everyone kept doing because it had always been done.
- A rule or script that was creating complaints or rework.
- A schedule or routine that suited the organization more than the customer, patient or user.
- An unwritten team rule you inherited as a new lead.
Avoid these:
- Rules you simply ignored. “I stopped doing the check because it was pointless” is misconduct, not courage. Challenges go through whoever owns the rule.
- Stories where everyone else looks foolish. If the old way had no sensible reason in your telling, the interviewer will doubt the telling.
- Challenges that went nowhere, unless you tell them as a learning story; our guide to the time your idea was rejected covers that shape.
An argument with one person fits the disagreed-with-your-manager answer; a before-and-after workflow change fits the process-improvement question; winning one person over fits tell me about a time you persuaded someone.
A five-beat structure, with timings
| Beat | What to say | Spoken time |
|---|---|---|
| 1. The practice | What everyone did, and the reason it existed | About 15 seconds |
| 2. The evidence | What made you question it: numbers, feedback, a source | About 20 seconds |
| 3. The challenge | Who you raised it with, how you framed it, and the pushback | About 25 seconds |
| 4. The test | A pilot, trial or side-by-side comparison rather than a big switch | About 20 seconds |
| 5. The result | The number, what is still in place, and a fair word about the old way | About 20 seconds |
That is the STAR method with the Action split into the challenge and the test, because those are the two places interviewers probe. Aim for about 100 seconds. Frame your first move as a question (“could we test…?”), not a verdict (“this is wrong”).
Five sample answers to “tell me about a time you challenged the status quo”
We wrote these to show the shape in different jobs; they are not real candidates' stories. Use your own situation, your own numbers and your own words.
Entry-level: a printed newsletter at a small charity
“During a summer internship at a small environmental charity, I helped with donor mailings. Every quarter we printed and posted a newsletter to all 4,000 donors, which took the team two full days, and nobody had checked who responded to it. I pulled two years of gift records and found that most donors under 50 gave online and had never used the reply slip. I took it to the development director as a question, not a proposal: could we test an email edition for online givers? She was worried about losing the personal touch, so we agreed a split for two quarters: print for anyone who had given by post in the last two years, email for everyone else. Gifts from the email group held steady, printing and postage fell by about half, and the print edition stayed for the donors who valued it. I learned to challenge with a test rather than a verdict.”
Customer-facing: an upgrade script on complaint calls
“At a broadband provider's contact centre, every call had to end with a scripted upgrade offer, including complaint calls, and our quality checks scored us on it. Survey comments kept saying things like ‘they tried to sell to me while my internet was down.’ I sorted three months of my own results on complaint calls, and the most common negative comment was the sales pitch itself. I took the numbers to my team leader and asked whether the offer could be optional when the fault wasn't fixed on the call. The sales manager pushed back, because complaint calls produced some upgrades. We agreed a one-month trial on our team, tracking both survey scores and upgrades. Complaint-call scores rose and upgrades barely moved. The script changed for the whole centre the next quarter.”
Healthcare: 4 a.m. blood draws on a medical ward
“On our medical ward, routine blood tests were drawn at around 4 a.m. so results would be back before the morning ward round. Patients often told us it was the worst part of their stay. When I raised it at a team meeting, I was told the doctors needed results early, so I asked the doctor who led the round when she actually reviewed bloods for stable patients: after 9 a.m. With our nurse unit manager and the phlebotomy lead, I set up a six-week pilot: patients the medical team flagged as stable had routine bloods at 6:30 instead, and unwell patients were unchanged. Results were ready for nearly every round. Comments about being woken overnight fell in our patient feedback, and the ward kept the new window. I framed it throughout as a patient-experience change, not a criticism of the night staff.”
Office or tech: a forced password change
“As an IT support analyst at a 600-person firm, I noticed that password resets were about a third of our tickets, mostly in the week after our forced 60-day password change. The security manager saw the rule as essential for audits. I didn't argue from opinion. I pulled six months of ticket data and read NIST's digital identity guidelines, which advise against forcing periodic password changes unless there is evidence of compromise. I wrote a two-page proposal: longer passphrases, multi-factor sign-in for everyone and checks against known breached passwords, in exchange for ending the 60-day expiry. He asked whether our auditor would accept it, so I drafted the control description and he took it to them. The auditor agreed, and six months later reset tickets had fallen by more than half.”
Manager: the late-night month-end close
“When I became team lead for a six-person accounts team, month-end close always ran into late nights, and there was an unspoken rule that nobody left until every reconciliation was done. I tracked two closes and found that nearly two-thirds of the corrections the controller sent back were on work done after 9 p.m. I shared that with the team and the controller and said the late nights were a sign our calendar was wrong, not proof of dedication. Some senior staff were skeptical. We moved three reconciliations to the week before close and set a 7 p.m. stop with a morning catch-up slot. The next three closes finished on the same day as before, the controller's corrections roughly halved, and I had to model it myself by leaving at seven when it felt wrong.”
Follow-up questions to expect
- “Why do you think it was done that way in the first place?” Give the old way a fair reason. It shows you listened.
- “Who disagreed, and what did you do?” Name the role, their concern and how you addressed it.
- “What would you have done if the answer was no?” Say you would have committed to the decision and kept gathering evidence.
- “Tell me about a challenge that didn't work.” Have a second story ready; a risk that didn't land works well here.
- “How do you decide what is worth challenging?” Impact, evidence and the cost of a small test.
Mistakes to avoid, and how to rehearse
- Calling the old way stupid. Its authors may be on the team you are joining.
- Opinion without evidence. “I felt it was outdated” is a preference, not a challenge.
- The lone hero. Name the people who helped the change land.
- No ending. Say what changed and whether it stuck.
Write the old practice and its original reason in one sentence each, then say the whole answer aloud and time it. An AI mock interview reads questions aloud and scores each spoken answer out of 10, which shows whether your evidence comes through in the first 30 seconds. Draft the beats in the free STAR builder or type a first version into the free practice demo.
Where CoPilot Interview fits
CoPilot Interview is an AI interview assistant. For a question like this one its main job is rehearsal: the AI mock interview builds questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10, so you can hear whether your evidence and your fairness to the old way both come through. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Paid plans are Standard at $24.99 a month and Pro at $39.99 a month. It runs as a desktop app for Windows 10 and 11 and macOS 12 or later, a free iPhone and iPad companion on the App Store (iOS 16 or later) and an Android companion in beta.
If you consider AI help during a real interview, follow your employer's rules first. AI can help you structure and tighten a story, but it must not invent one: every event, number and name in your answer has to be true and yours.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
What is a good example of challenging the status quo at work?
A practice you questioned with evidence, raised with its owner, tested small and changed, with a measurable result, such as a script that hurt customer scores.
How do I answer if I have little work experience?
Use school, volunteering or a part-time job: a club rule, a team routine or the way a shift was run. The structure is the same.
Is challenging the status quo the same as disagreeing with my manager?
Not quite. A disagreement story is about one decision and one relationship; a status-quo story is about a practice many people took for granted. The same events can sometimes answer both.
What if my challenge failed?
You can still use it if you show what you learned and how you handled the no. Many interviewers trust an honest partial result more than a story where everything went perfectly.
How long should the answer be?
About 90 seconds to two minutes when spoken, with most of the time on the evidence, the conversation and the test.
Rehearse it out loud before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview