To answer “tell me about a time you implemented a new idea,” spend a sentence or two on the idea and most of the answer on making it real: the case you made, the small test you ran, how you got people and resources behind it, the rollout and the result. Interviewers care less about how clever the idea was than about whether you can carry one from a suggestion to something people actually use. Close with a number and what happened to the idea after you.
How this question differs from its cousins
| Question | What it focuses on | Where to spend your time |
|---|---|---|
| “Tell me about a time you were creative” | Where the idea came from | The insight and the original thinking |
| “Tell me about a time you showed initiative” | Acting without being asked | Spotting the gap and starting |
| “Tell me about a time you challenged the status quo” | Questioning an accepted way | The evidence, the tact and the pushback |
| “Tell me about a time you implemented a new idea” | Delivery | The pilot, buy-in, rollout, adoption and result |
| “Tell me about a time your idea was rejected” | Handling a no | The reasons, and what you did next |
The same events can answer several of these; what changes is where you spend the time. For this one, about two-thirds of the answer belongs to implementation.
What interviewers are checking
- Practical judgment: the idea was worth the effort and the risk.
- A case: you explained the benefit in terms the decision-maker cared about.
- Testing: you tried it small before rolling it out.
- Bringing people along: training, answering objections, adjusting the idea.
- Measurement and follow-through: you checked it worked and kept it working.
Several frameworks describe this. The UK Civil Service Success Profiles behaviour “Changing and improving” asks candidates to seek out opportunities to create effective change and suggest innovative ideas for improvement; Amazon's “Invent and Simplify” principle says leaders look for new ideas from everywhere and are not limited by “not invented here”; and the NSW framework's “Manage reform and change” capability is about supporting and championing change and helping others engage with it (all checked November 2026). So an idea you borrowed from another team or company is fine, as long as you say so. Our guide to all 16 Amazon Leadership Principles maps other stories to principles.
Choosing an idea that actually shipped
- It was implemented, at least as a pilot. A proposal that went nowhere belongs in a different answer.
- You were central to implementing it, even if the idea started with someone else; say whose it was.
- It changed what colleagues or customers did.
- There is a result: time, errors, sales, retention, satisfaction or safety.
Avoid ideas you put in place without permission when permission was needed, big company initiatives where your part was small, and technical ideas you can't explain in plain words. If your idea was mainly a fix to an existing workflow, the process-improvement question may suit it better.
A structure: spark, case, pilot, rollout, result
| Stage | What to say | Time |
|---|---|---|
| Spark | The problem and the idea, in one or two sentences | 15 seconds |
| Case | Who you had to convince and what you told them | 20 seconds |
| Pilot | The small test and what it showed | 25 seconds |
| Rollout | How you scaled it: training, changes, objections | 25 seconds |
| Result | The number, adoption and what happened next | 15 seconds |
It is the STAR method with the Action split into case, pilot and rollout. Keep the spark short; candidates who love their idea spend a minute explaining it and run out of time before the part being assessed.
Five ideas taken from suggestion to rollout
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 retail: a customer request log
“I worked weekends at an independent bookshop, and customers often asked for titles we didn't stock. We'd apologize and they'd leave. My idea was a request log at the till, with the customer's details if they wanted a call when the book arrived. The owner worried it would mean extra ordering work, so I offered to run it myself for a month and review it with her at the end. I made a one-page form, showed the other weekend staff how to use it and went through it every Monday against the supplier list. In the first month we logged 46 requests; the owner ordered 30 of them and 24 customers came back to collect. She kept the log, added it to weekday shifts and began using the request patterns to decide what to stock in two sections.”
Customer-facing: first-30-days calls at a gym
“As a membership advisor at a gym, I noticed most cancellations came from people in their first two months, many of whom had visited only two or three times. My idea was a first-30-days plan: a call at day 7 and day 21 to ask how it was going and book a free session with a trainer. My manager liked it but worried about staff time, so we piloted it with half of one month's new members, split by sign-up date, and kept the other half as a comparison. I wrote a short call guide so the calls felt helpful rather than salesy. After three months, the pilot group had visited more often and about a third fewer had cancelled. The manager rolled it out to every new member, and the trainers liked it because some of those free sessions became regular clients.”
Trades: a photo record before walls are closed
“I'm a lead carpenter at a small remodeling company. We sometimes had to open finished walls to find a pipe or wire, or settle a disagreement with a homeowner about what was behind the drywall. My idea was a photo record: before any wall or ceiling was closed, we'd photograph every bay with a tape measure in shot, upload it to the job folder and give the homeowner a copy at handover. The owner thought it would slow us down, so I tried it on my own two jobs and timed it at about 15 minutes a room. On one of those jobs the photos had already saved us opening a ceiling to find a junction box, and I showed him. He made it standard, I trained the other two crews, and requests to locate hidden pipes and wiring after handover have almost stopped.”
Office or tech: an automated pricing check
“As a junior data analyst at a regional grocery chain, I noticed that pricing errors, like a promotion that didn't load at some stores, were usually found days later in the weekly sales report. My idea was an automated check each morning comparing every store's sales of promoted items with the chain average and flagging outliers. My manager agreed I could spend Friday afternoons on it. I built a first version in SQL with a short email summary and ran it alongside the weekly report for a month: it caught four real pricing errors, each at least three days earlier than before, and two false alarms, which I fixed by adjusting the threshold. I then walked the pricing team through it, and they asked me to add a stock-out check. It is now part of their daily routine.”
Manager: Saturday mortgage clinics at a credit union
“As a branch manager at a credit union, I kept hearing from members that they couldn't get mortgage advice without taking time off work, and our branch's mortgage applications lagged the others. My idea was a monthly Saturday morning mortgage clinic, by appointment. It needed approval from the regional manager, staff willing to work Saturdays and an adviser from head office. I built a short case from member comments and our application numbers and proposed a three-month trial with time off in lieu. Two of my team volunteered and the adviser agreed to come once a month. Every slot was booked in the first month, applications from our branch rose by about a third over the trial, and the regional manager extended the clinics to two more branches using the setup guide I wrote.”
Follow-up questions to expect
- “Whose idea was it originally?” Be exact. Implementing someone else's idea well is still a strong story.
- “Who objected, and what did you change because of it?” Show you adjusted the idea, not just pushed it through.
- “How did you measure whether it worked?” The comparison, the period and the number.
- “What would you have done if the pilot had failed?” Stopped it, learned why, and said so to the people who backed it.
- “Is it still in use?” If it faded, say why. That honesty usually lands well.
Mistakes to avoid, and a practice routine
- A minute on the idea and ten seconds on the implementation.
- No test: “we rolled it out to everyone” sounds risky, not decisive.
- Claiming the whole team's work as yours.
- An idea with no measurable effect.
- Skipping the people who had to change their habits.
Time the spark: if it takes more than 20 seconds out loud, cut it. Then rehearse the full answer with an AI mock interview, which builds questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10. Have “who objected?” ready as well. You can draft it first in the free STAR builder.
Where CoPilot Interview fits
CoPilot Interview is an AI interview assistant whose free AI mock interview turns your résumé and the job description into questions, reads them aloud and scores each spoken answer out of 10, so you can check that the implementation, not the idea, carries your answer. The browser demo at /try has 145 questions in 10 tracks, free and without signup. 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.
For any live use in a real interview, follow your employer's rules. 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 implementing a new idea at work?
An idea you turned into something people use: you made the case, tested it small, adjusted it, rolled it out with training and measured the result, such as a request log, a check-in call or an automated report.
Does the idea have to be mine?
No. Implementing a colleague's or another company's idea counts if you led the work of making it happen; just say where it came from.
What if my idea was only piloted?
A pilot with a clear result is a good answer. Say what the pilot showed and what was decided afterwards.
How is this different from “tell me about a time you were creative”?
A creativity answer focuses on the thinking behind the idea. This one focuses on delivery: buy-in, testing, rollout and adoption.
How long should my answer be?
About 100 seconds, with no more than 20 seconds on the idea itself.
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