Changing and Improving interview questions test how you respond when the current way of working is no longer good enough.
The panel will usually want more than enthusiasm for change. They are looking for judgement: how you recognised the problem, what evidence you used, how you involved people and whether you adapted when the first idea met resistance.
If you are still writing the application, use the Changing and Improving 250-word statement guide.
What the panel is looking for
A strong answer makes the improvement understandable before it makes it impressive. The panel should be able to see the problem, the constraints and why your chosen change was sensible.
They may also test whether you can challenge constructively. At senior grades, that can mean pushing back on a preferred solution when the evidence points elsewhere; at junior grades, it may simply mean suggesting a practical improvement and helping colleagues use it.
Common Changing and Improving interview questions
| Theme | Example question |
|---|---|
| Practical improvement | Tell me about a time you improved a process or way of working. |
| Resistance to change | Describe a time somebody resisted a change you were introducing. |
| Innovation | Give an example of when you found a different way to solve a recurring problem. |
| Learning from feedback | Tell me about a time feedback caused you to change your original approach. |
| Technology | Describe a time you used technology to make work more effective. |
| Challenge | Tell me about a time you challenged an established way of working. |
| Unsuccessful first attempt | Give an example of a change that did not work first time and what you did next. |
A different script for every question usually makes preparation harder. Build a small bank of real examples and practise how each can answer more than one theme.
Use B-STAR to keep the answer focused
A brief Belief can establish your approach before the example. Keep the setup short, let Action carry the improvement evidence and finish with what actually became better.
I do not assume that new automatically means better. I start by understanding what is getting in the way, then test the simplest improvement that deals with the real cause.
Full worked interview answer
Question: Tell me about a time you improved a process when people had different views about what needed to change.
I do not assume that new automatically means better. I start by understanding what is getting in the way, then test the simplest improvement that deals with the real cause.
As an HEO, I inherited responsibility for a weekly performance pack that took analysts most of a day to assemble. Managers wanted a new reporting tool, while analysts argued that the real problem was inconsistent definitions across teams.
I needed to improve the process without spending money on technology that might simply automate bad data.
I reviewed how each measure was produced and found that several teams were using different cut-off points and status definitions. I brought the analysts and operational leads together to agree a common source and definition for each measure before discussing automation.
Once those rules were settled, I used our existing reporting platform to automate the repeatable parts. Two analysts were sceptical because unusual cases still needed judgement, so I asked them to design the exception route with me rather than forcing every case through the automated logic. We ran the old and new packs in parallel for two cycles and corrected one definition where the figures did not reconcile.
The team moved to the revised process without buying another tool. Routine re-keying was removed, analysts had more time to investigate the figures, and managers reported greater confidence because every team was now working from the same definitions.
Why this answer works
The candidate separates the proposed solution from the underlying problem. That stops the answer becoming a story about buying technology.
The analysts who disagree are not treated as blockers. Their concern turns out to be useful and shapes the exception route.
Running the approaches in parallel shows controlled implementation rather than a dramatic switch with no assurance.
The result demonstrates both efficiency and quality, and it follows directly from the problem described at the start.
Compare your answer with more worked examples
The grade-specific interview guides cover all nine behaviours with worked questions and answers, helping you test whether your example shows enough ownership, challenge and delivery for the grade you are applying for.
Expect follow-up questions
Expect the panel to test the change beneath the polished story. They might ask:
One likely question is: Why did you decide not to pursue the new tool?
They may also ask: How did you handle colleagues who preferred the existing process?
Another useful probe would be: What was the biggest risk in changing the reporting method?
You could also hear: What would you have done if the parallel run had exposed larger differences?
A final follow-up might be: What did the analysts contribute that you had not considered initially?
What changes by grade?
AA/AO
Notice better ways of working, learn new procedures, make sensible use of technology and raise problems with change constructively.
EO
Review how work is done, suggest practical improvements, respond positively to change and help colleagues understand and use new approaches.
HEO/SEO
Work with others to simplify processes, use technology intelligently, invite ideas from a wide range of people and explain the reasons for change.
G6/7
Create space for challenge and innovation, understand the full effect of change on people and users, use technology where it adds value and challenge senior proposals when needed.
Prepare one example where you changed your own mind
Panels often probe whether you are genuinely open to improvement. An example where feedback altered your first idea can be more convincing than one where every colleague immediately agrees with you.
Know the problem in one sentence
If it takes two minutes to explain why the old way was poor, the answer will drag. Practise describing the issue clearly, then spend the time on your decisions.
What if the first change did not work?
Panels sometimes ask about a failed improvement because it reveals whether you learn or defend. A strong answer can explain what the early evidence showed, what assumption turned out to be wrong and how you adjusted.
You do not need a disaster story. A pilot exposing an awkward exception or a piece of feedback changing the design is enough to show that improvement was iterative.
Handling technology questions
If technology features in your example, keep the behaviour about the problem and the improvement rather than the software. The panel does not need a product demo.
Explain why technology was appropriate, what alternative you considered and how you made sure the solution worked for the people using it, including accessibility where relevant.
Common interview mistakes
Innovation without a problem. A new tool or process is presented as the achievement even though the need for it is unclear.
Treating resistance as negativity. The strongest answers listen for useful concerns rather than dismissing people who disagree.
No testing. The candidate jumps from idea to full implementation without showing how risk was managed.
Claiming credit for somebody else’s change. Being part of a transformation is not enough if your own decisions are invisible.
No evidence of improvement. The process changed, but the answer never shows that it became better.
Prepare across all nine behaviours
The grade-specific interview guides cover all nine behaviours with worked questions and answers, helping you test whether your example shows enough ownership, challenge and delivery for the grade you are applying for.
Need the written application instead? Go to the Changing and Improving 250-word statement example.
