A senior candidate is asked to describe a time they led change. They pick their biggest project: a new system, a restructure, a merger of two teams. They spend four minutes on the timeline, the budget and the go-live date. The panel nods, then asks one follow-up: “Who pushed back, and what did you do about it?” The answer is thin, because that part of the story was never prepared.
This is the pattern I see most often in senior interview preparation. The candidate has led real change. They simply tell it as a project update, when the panel is listening for something else entirely.
This guide sets out what a director or executive panel is really testing with this question, how to choose the right story, a structure that holds up under probing, and the follow-up questions to prepare for.
Why the question changes at senior level
At mid-level, “tell me about a time you led change” checks whether you can deliver a change someone else decided on. You implemented the new process, kept the team on track and hit the deadline.
At director level and above, the panel assumes you can deliver. They want to know whether you can decide what needs to change, build the case for it, and bring people with you who don’t report to you and don’t have to agree. Most senior roles are created or filled because something needs to change, so this question is often the closest the panel gets to asking: “What would you actually do here?”
| Mid-level answer | Senior-level answer | |
|---|---|---|
| Starting point | “I was asked to roll out…” | “I saw that… and made the case to change it” |
| Focus | Tasks, timeline, delivery | Judgement, trade-offs, people |
| Who you influenced | Your own team | Peers, senior stakeholders, other functions |
| Resistance | Mentioned briefly, if at all | Central to the story |
| Result | Delivered on time | Measurable outcome that lasted after you stepped back |
What the panel is really assessing
The question sounds like one thing. In practice, a senior panel is listening for five.
- Diagnosis. Did you see the need for change yourself, and can you explain why it mattered to the organisation, not only to your team? Panels notice when a candidate can’t say what would have happened if nothing changed.
- Judgement and trade-offs. What options did you consider, and what did you choose not to do? A change with no visible trade-offs sounds either small or unexamined.
- Influence without authority. Who did you need on side that you couldn’t instruct? Peers, a sceptical finance director, a union, a regional team in another country. This is often the deciding factor between two strong candidates.
- Handling resistance with respect. How did you respond to people who disagreed? Panels listen closely to how you describe them. Contempt for the people who resisted is a red flag, however good the result.
- Lasting results. What changed, in numbers, and did it hold after the project ended? Change that slipped back once you moved on tells the panel you managed a project, not a shift in how people work.
In my view, the fourth point is the one most candidates underestimate. Senior roles involve leading people through change they didn’t choose. How you talk about the people who pushed back tells the panel how you will treat their teams.
Choosing the right story
The biggest change you’ve led is not always the best one to tell. I’d go further: the best change stories are often mid-sized, because you can explain your own role clearly. In a large programme, your contribution gets lost among steering groups and consultants, and the panel can’t tell what you decided.
A strong story usually has these features:
- You initiated it, or shaped it significantly. You weren’t only handed a plan to deliver.
- There was real resistance. Someone with influence disagreed, and you had to work through it.
- You made a decision that could have gone the other way. A trade-off, a risk, or something you chose to stop doing.
- It’s recent. Within the last three to five years, so it reflects the leader you are now.
- The result can be measured. Retention, cost, cycle time, customer scores, engagement, revenue.
- It relates to the role. If the job is about integrating teams after an acquisition, a story about integration beats a story about a new reporting tool.
Prepare at least two change stories. Panels often ask a second version of the question, and repeating the same example looks thin. One story about changing how people work and one about changing structure or strategy gives you good range.
A structure that holds up at senior level
STAR (situation, task, action, result) is a reasonable starting point, but at senior level it puts too much weight on the situation and too little on your thinking. This six-part structure keeps the focus where the panel wants it. Aim for two and a half to three minutes in total. If you want to see how the standard STAR format can be rebalanced, read The STAR Method for Senior Interviews: How to Adapt It at Director Level.
- The headline (one sentence). Lead with the change and the result: “I moved our regional teams from three separate operating models to one, which cut onboarding time by 40% over 18 months.” The panel now knows where the story is going and can listen for how you got there.
- Why it needed to change (20–30 seconds). The problem, its cost to the organisation, and what would have happened if nothing changed. Keep the background short.
- The choice you made (30 seconds). The options you considered and why you chose this one. Name one thing you decided not to do, and why.
- Bringing people with you (60 seconds). This is the heart of the answer. Who resisted, what their concern was, and what you did to understand it and work through it. Show that you took their objection seriously, and say if it changed your plan.
- The result (20–30 seconds). Two or three numbers, and evidence that it lasted: still in place a year later, adopted elsewhere, or owned by the team without you.
- What you’d do differently (15 seconds). One honest, specific reflection. This signals maturity, and it often prompts a good follow-up conversation.
Notice the balance. Steps 3 and 4 take more than half the answer. Most candidates spend that time on step 2.
Illustrative outline (not a real client): A head of operations sees that three regional teams use different processes for the same work. She makes the case to the COO using error rates and onboarding time. She chooses to standardise around the best of the three existing processes rather than buy a new system, and accepts a slower start in exchange for lower cost and less disruption. The strongest resistance comes from a respected regional lead who built one of the old processes. She asks him to co-lead the design, and two of his steps end up in the final version. Onboarding time falls by 40% and errors by a third. Two years on, the model is still in place. Her reflection: she would have brought finance in earlier, because the budget conversation cost her two months.
The follow-up questions to prepare for
At senior level, the first answer only opens the conversation. Panels probe to check the story is yours and that it holds together. Prepare for these:
| Follow-up question | What it’s testing | What a strong answer includes |
|---|---|---|
| “What was your specific role?” | Whether you led it or were part of it | The decisions you personally made, using “I” for those and “we” for the team’s work |
| “Who was the hardest person to bring on side?” | Influence and respect | Their view in fair terms, what you learned from it, how you moved them |
| “What would you have done if they hadn’t agreed?” | Judgement under pressure | A realistic fallback, including when you’d escalate or adjust the plan |
| “What went wrong?” | Honesty and self-awareness | A real setback, what it cost, and how you recovered |
| “How did you keep your own team going during it?” | Leading people through uncertainty | How you communicated, what you protected them from, how you checked in |
| “How do you know it worked?” | Evidence, not assertion | Before-and-after numbers, and how long the change has held |
| “How would you approach change here?” | Whether you can transfer the lesson | Listening and diagnosis first, rather than repeating your last playbook |
The last question deserves care. Candidates who say “I’d do exactly what I did before” suggest they haven’t thought about how different organisations work. Start with what you would want to understand first.
Common mistakes
- Telling it as a project update. Milestones, budgets and go-live dates prove you can manage a project. They say little about how you lead people through change.
- Casting yourself as the lone hero. Senior panels are wary of candidates who changed everything single-handedly. Name the people who made it work. Giving credit is a leadership signal, and it makes your own role more believable.
- Making the resisters the villains. “The old guard just didn’t get it” tells the panel how you’d talk about their people. Describe the concern fairly, even if you disagreed with it.
- No numbers. “It went really well” is not a result. If you don’t have exact figures, give honest estimates and say so.
- A change with no cost. Every real change has a trade-off. If yours doesn’t, the panel will wonder what you left out.
- Too much background. If you’re still explaining the situation after a minute, you’ve lost the panel.
- An old story. A change from ten years ago suggests you haven’t led one since.
Other ways the question is asked
The same assessment often comes in different words. Your change stories should cover all of these:
- “Describe a significant change you initiated.”
- “Tell me about a time you had to win support for an unpopular decision.”
- “Give an example of transforming a team or function.”
- “Tell me about a time you challenged the way things were done.”
- “How have you led a team through uncertainty or restructuring?”
- “Describe a change that didn’t go to plan.”
Competency-based panels often use the last one, and it catches out candidates who have only prepared success stories. For the wider set of questions director panels use, see Director-Level Interview Questions: What the Panel Is Really Assessing.
Not sure whether your experience is ready for a senior role? The free Leadership Readiness Assessment takes about ten minutes and shows where your strengths and gaps sit.
Prepare your change stories
Work through each story with these prompts before you rehearse it out loud. If you can’t fill a row, the panel will find the gap.
| Prompt | Story 1 | Story 2 |
|---|---|---|
| Headline: the change and its result, in one sentence | ||
| Why it needed to change, and the cost of doing nothing | ||
| Options you considered, and what you chose not to do | ||
| Who resisted, and what their concern was | ||
| What you did to bring them on side | ||
| Results, with numbers | ||
| Evidence it lasted | ||
| What you’d do differently | ||
| Which variations of the question it answers |
Then rehearse each story with someone who will interrupt you. Check that your first sentence carries the point, and that you can answer every follow-up in the table above without inventing details on the spot.
Preparing for a senior interview?
I work one-to-one, online, with senior professionals preparing for director, head-of and executive interviews. Wherever you’re based, sessions are scheduled around your time zone.
The Interview Preparation Programme covers role-specific strategy, answer development, mock panel interviews with realistic follow-up questions, and coaching on communication and presence. We build and test your change stories until they hold up under any version of the question.
If you have an interview coming up, book a discovery call and we’ll look at what the panel will be testing for.

