The whole weight of this answer rests on one word, and it is not "initiative". It is "nobody". Initiative means you did something nobody asked you to do, and nobody would have blamed you for not doing. The moment your story contains an instruction, a request, or a responsibility that was clearly yours, the initiative evaporates, because you were just doing what was expected.
Most candidates weaken their own answer without realising it, by describing something that was actually part of their job and calling it initiative. The interviewer hears a competent employee doing their role, which is fine but not what was asked. The strongest initiative answers are almost provocative in how clearly they establish that this was not your job and you did it anyway.
Make the "nobody asked" explicit
Because this word carries the answer, you should say it out loud in your story. Do not leave the interviewer to infer that nobody asked you. State it. "It was not part of my role, but..." or "Nobody had raised it, so..." This is one of the rare cases where being explicit about the setup strengthens rather than pads the answer, because it sharpens exactly the thing being tested.
Compare:
- Weak: "I improved the filing system in our office."
- Sharp: "Nobody had asked me to touch it, and it was not really my job, but the filing system was costing everyone ten minutes a day, so I rebuilt it."
Same action. The second version makes the initiative visible by naming its optional nature.
The two halves of a strong initiative story
A good answer has a noticing half and a doing half, and both need to be there.
The noticing. Initiative starts with seeing something others walked past: an inefficiency, a gap, a problem nobody owned, an opportunity being missed. The observation is genuinely the impressive part, because plenty of people would step over the same thing. Give it real weight in your answer.
The doing. Then you acted, without being told to, and ideally without waiting for permission (or you sought permission proportionately and then ran with it). The doing should show you followed through, not just suggested something and left it.
If your story has the doing but not the noticing (someone pointed the problem out, then you fixed it), it is more of a problem-solving answer. If it has the noticing but no real action, it is just having good ideas. Initiative needs both.
A worked example
"I had a summer job doing data entry for a small charity, and part of it was sending thank-you letters to donors, which we did completely manually, typing each one from scratch. It was slow, and worse, because it was slow, the letters were going out weeks late, sometimes a month after someone had donated, which for a charity is a real problem because it makes donors feel taken for granted.
Nobody had asked me to change anything, my job was just to type the letters. But it bothered me that people were giving money and hearing nothing back for weeks. So on my own initiative I built a simple mail-merge setup, a template with the personal bits pulled automatically from the donor spreadsheet we already had. It took me an afternoon to work out.
After that, thank-you letters went out within two days instead of two to four weeks, and they were still personalised. I checked with my manager before rolling it out properly, because it was changing a process, and she was genuinely pleased, she had known the delay was a problem but nobody had had time to fix it.
The reason I did it was honestly just that the delay felt disrespectful to the donors, and once I noticed it I could not really un-notice it. What it taught me was that a lot of 'that's just how we do it' problems are actually nobody's job to fix, which is exactly why they never get fixed unless someone decides to."
Why it works
The candidate says "nobody had asked me" explicitly, which is exactly right. The noticing is given real weight (the delay was disrespectful to donors) and it is a genuine observation, not everyone doing data entry would clock the donor-experience angle. The doing follows through to a concrete result (two days instead of two to four weeks). And the proportionate check with the manager before rolling it out shows judgement: initiative does not mean going rogue, it means acting on something and bringing people with you.
The closing insight is the sharpest part: "a lot of that's-just-how-we-do-it problems are nobody's job to fix, which is why they never get fixed unless someone decides to." That is a real understanding of how organisations work, and it signals to the interviewer that you will be the person who notices and fixes the quiet inefficiencies everyone else has stopped seeing.
What weakens the answer
It was actually your job. The most common failure. If fixing it was within your responsibilities, it is diligence, not initiative. Choose something genuinely outside your remit.
You were told to. "My manager asked me to improve it, so I did" is not initiative by definition. The request has to be absent.
No follow-through. "I suggested we could do X" is an idea, not initiative. Initiative means you did it, or at least drove it to happen.
Going rogue. The opposite failure: changing something significant with no regard for anyone else. Real initiative usually involves a sensible check-in, especially before changing a process others rely on. Show you acted boldly but not recklessly.
Finding yours
Look for a time you saw something that was not working and fixed or improved it without being asked: a process, a tool, a gap in how something was done, a problem nobody owned. Jobs, volunteering, and group projects are full of these. The problem-solving competency guide is a close relative if you want to sharpen the diagnosis part.
Before your interview, check your story passes one test: could you say "nobody asked me to do this" and have it be true. If you cannot, keep looking, because that phrase is the heart of the answer. You can practise it and get feedback on whether the initiative comes through as clearly as it needs to.