Changing and Improving: Avoiding the Obvious Trap
What Changing and Improving actually asks for, with a weak and a strong worked example against the same prompt, so you can see the gap for yourself.
The moment “Changing and Improving” appears on a shortlist of behaviours, most candidates reach for the biggest change they were ever near. A system migration. A restructure. A departmental merger. It feels like the obvious choice, because it was big, it was memorable, and everyone in the office talked about it.
It is usually the wrong choice. Somebody else led that change. You attended the briefings, worked through the guidance, and adapted, which is a real skill, but it is not what this behaviour is testing. The framework asks what you changed or improved, however small, and what you did to make it stick.
This post sets out what Changing and Improving actually asks for at the grades most external applicants apply to, quotes the framework’s own wording so you can check it against your advert, and shows a weak and a strong answer against the same prompt so you can see exactly where the gap sits.
What Does “Changing and Improving” Actually Ask You to Prove?
It asks you to prove you spotted a better way of doing something and acted on it, not that you lived through a change somebody else designed. The official definition, in the Success Profiles Behaviours guidance, reads: “Seek out opportunities to create effective change and suggest innovative ideas for improvement. Review ways of working, including seeking and providing feedback.”
Every verb in that sentence puts you in charge of the action: seek out, suggest, review, provide feedback. None of it is written from the position of someone a change happened to.
Changing and Improving is one of nine named Behaviours, and Behaviours is only one of five Success Profiles elements a vacancy can use, alongside Ability, Strengths, Experience and Technical. The advert states which elements your campaign uses, and the recruiting manager only tests the behaviours that suit the role, so you might not meet this one at all.
Why Do Candidates Reach for the Wrong Example?
Because scale feels like proof. A system migration or a restructure has a name and a memorable launch date, so it feels easier to describe than a small thing you did quietly. The trouble is that describing the migration usually means describing what happened to your team, not what you did. The writer becomes a witness to an event rather than the person who caused one.
Ask a simple test of any draft: if you removed yourself from the story entirely, would the change still have happened? If the answer is yes, the example is not about you.
What Is the Difference Between Adapting to Change and Driving It?
Adapting is coping well with a plan someone else wrote. Driving it is proposing the plan in the first place, however small that plan is. Both are genuinely useful workplace qualities, but only one of them is what Changing and Improving is measuring.
The definition’s own verbs make the line clear: “seek out” and “suggest” describe someone going looking for a problem before being asked to fix it. A candidate who writes about attending training sessions, following new procedures, or staying positive through a reorganisation is describing resilience, not initiative. Resilience under someone else’s change is closer to Delivering at Pace or Working Together. It is not evidence for this behaviour, even when the underlying change was large and disruptive.
What Does the Framework Expect at Your Grade?
Less than most candidates assume, and it scales with responsibility rather than with the size of the change. At Administrative Assistant (AA) and Administrative Officer (AO) grade, the published examples of Changing and Improving are that you: “review ways of working and suggest improvements, including how to make full use of new digital technologies”, “learn new procedures and help colleagues to do the same”, “query any issues that arise from changes in a suitable way”, and “respond in an effective and appropriate manner when emergencies arise”.
At Executive Officer (EO) grade, one level up, the same guidance raises the expectation from your own work to your team’s: “regularly review own and team’s work and take the initiative to suggest ideas to make improvements”, “give feedback on changes in a constructive manner”, “take a positive, open approach to the possibility of change and encourage others to do the same”, “help others to understand changes and the reasons they are being put in place”, “identify and act on the effects changes are having on your role and that of the team”, “look for ways to use technology to achieve efficient and effective results”, and “consider accessibility needs of the diverse range of end users”.
Notice what stays constant across both grades: the person reviewing, suggesting and querying is you. What changes is scope, from your own tasks at AA and AO grade to your team’s work at EO grade.
PublicServicePathway is independent and is not affiliated with or endorsed by the UK Government or Civil Service. The quotes above are copied directly from the published framework so you can check them against your own advert rather than taking this post on trust.
How Small Can the Change Actually Be?
Smaller than the word “improving” makes it sound. A process you tidied up for two people is a legitimate answer if you can show you noticed the problem, proposed a fix, and made the fix outlast the moment you introduced it. A large transformation you stood next to, however impressive it looked from the outside, is a weaker answer than a small one you actually own, because ownership is what the descriptors above are asking for.
The Success Profiles Behaviours guidance itself suggests using the STAR method, setting the scene, showing what you did and how, and giving the outcome, and adds that “there is no expectation that you need to demonstrate every part of each example to be successful.” A tightly evidenced small example beats a vaguely evidenced big one under that structure.
What Separates a Weak Changing and Improving Answer From a Strong One?
The two answers below respond to the same illustrative prompt. Both were written for this article to show the difference in practice. Neither is a real candidate’s submission, and neither should be copied.
The prompt
Tell us about a time you identified a way to improve how something was done, and what you did to make sure it stuck.
A weak answer
“Our directorate moved from a paper-based case file system to a new digital case management platform. It was a huge change for the whole team, and at first everyone found it difficult. I attended the training sessions, worked through the guidance packs, and helped a couple of colleagues who were struggling with the new screens. Within a few weeks we were all using the new system as normal, and the team lead said the transition had gone smoothly. I think this shows I can adapt well to change and support colleagues through a difficult period.”
A strong answer
“Two of us in the team were manually retyping the same customer reference numbers from an intake spreadsheet into the case system, and I noticed we were making the same transcription error at least once a week, which then had to be corrected by a caseworker downstream. I drafted a one-page checklist that matched the order of the fields on both screens and tested it with my closest colleague for a fortnight, adjusting it twice after we found steps that still caused mistakes. I then raised it with my line manager, who agreed to add it to the induction pack for new starters. Six months on, it is still the version the team uses, and two colleagues who joined since have never seen the old process.”
Why the strong answer clears the bar and the weak one does not
The weak answer describes a platform somebody else built and a rollout somebody else managed. Every verb belongs to the organisation or to “everyone”: the directorate moved, the transition went smoothly. The writer’s own actions, attending training and helping colleagues, are real, but they sit inside the AA and AO descriptor for Working Together and Developing Self and Others, not for Changing and Improving. Nothing in it matches “seek out opportunities” or “suggest improvements”, because the writer never proposed anything. The change happened to the team, and the writer coped with it well.
The strong answer keeps a comparable, modest setting but changes what is on the page. It opens with the writer noticing a problem before anyone raised it, which is the “seek out opportunities” language from the definition itself. It shows a proposal (“I drafted a one-page checklist”), matching “suggest improvements” and “review ways of working” from the AA and AO descriptor. It shows testing and iteration, matching “query any issues that arise from changes” and the EO line “take the initiative to suggest ideas to make improvements”. It closes with the change outliving the writer’s involvement, six months on, new colleagues never seeing the old process, which answers the part of the framework that talks about a change being embedded rather than announced. The scale is smaller than a platform migration. The evidence is stronger, because every sentence is something the writer did.
FAQ
Can I use a small process fix as my Changing and Improving example, even if nobody else noticed it? Yes. The AA and AO descriptor is written around your own ways of working, not around organisation-wide projects. A change only you noticed and fixed is still valid evidence, provided you can show what you did and what changed as a result.
What if the biggest change I have been part of was led by someone else and I only adapted to it? Look for a smaller moment inside that same period instead. Somewhere in most large rollouts there is a smaller local problem, a workaround, a piece of guidance that needed clarifying, that you personally identified and acted on, even while the wider change was someone else’s to run.
Does the example have to involve new technology? No. The EO descriptor mentions using technology as one of several routes to improvement, alongside giving feedback on change and helping others understand it. A non-technical process fix is just as valid if it is something you reviewed and changed yourself.
How is Changing and Improving different from Making Effective Decisions? Changing and Improving is about spotting and acting on an opportunity to do something better. Making Effective Decisions is about how you weigh evidence and options once a decision is already in front of you. The same event can sometimes support either behaviour, but the example needs to be written for the one the advert has actually asked for.
Does my example need a dramatic or measurable result? No. The framework does not ask for a percentage or a saving. What it asks for, at both AA and AO and EO grade, is evidence that the change was reviewed, suggested, and followed through, and that it held once you stepped back.
Check Your Example Against the Grade Named in Your Advert
Every line quoted in this post came from the published framework, not from a prep site’s rewording of it, so read the AA and AO or EO descriptor that actually applies to your vacancy before you draft. If Working Together is also on your list and your current draft still leans on the stock line about being a team player, a companion piece on this site works through getting past it.