When an interviewer asks you to describe a time you improved a process or system, they are looking for evidence that you notice inefficiency, understand the real cause of a problem and can turn an idea into a measurable improvement.
The strongest answers do not stop at “I suggested a better way”. They show the problem, the evidence, what you changed, how you brought people with you and what improved afterwards.
What a strong answer should contain
- A real problem or inefficiency with enough context to understand why it mattered.
- Evidence that you investigated the cause rather than jumping to a solution.
- Your specific action, not only what “we” did as a team.
- How you handled stakeholders, resistance, risk or implementation.
- A measurable result: time saved, cost reduced, quality improved, errors reduced, customer outcome improved or capacity released.
- What you learned or what you did to make the improvement sustainable.
Use STAR – but spend most of your answer on the action
STAR works well for this question. Keep the Situation and Task short. The interesting part is the Action: how you discovered the issue, evaluated options, designed the change and implemented it. Finish with a Result that proves the improvement was worthwhile.
Example 1: improving a manual reporting process
“In my previous role, our weekly performance report took two analysts most of a day to produce because data was copied manually from several spreadsheets. The process was slow, introduced occasional errors and meant the report could not be produced when either analyst was absent.”
“I mapped the process and found that most of the manual work was repetitive transformation rather than judgement. I agreed the required outputs with the report users, standardised the source files and built an automated Power Query workflow. I ran the old and new processes in parallel for three reporting cycles, documented the checks and trained both analysts so the solution was not dependent on me.”
“Production time fell from around 12 staff-hours to under two, and the number of correction requests dropped significantly. The saved capacity was used for analysis rather than copying data, and the approach was later reused for two other reports.”
Example 2: reducing customer-service delays
“A customer-service team had a growing backlog because every case entered the same queue regardless of urgency or complexity. I reviewed four weeks of data and found that simple requests were waiting behind a smaller number of complex cases.”
“I worked with the team to define three triage categories and introduced a short daily review of urgent or blocked cases. We piloted the change with one team, tracked waiting time and rework, and adjusted the definitions where staff were interpreting categories differently.”
“Within six weeks the average waiting time for straightforward cases fell by 35%, the oldest-case backlog reduced by more than half and customer complaints about response time dropped. We then rolled the approach across the wider service.”
Example 3: improving software testing
“Our regression testing repeatedly started late because test data was requested only after development completed. I reviewed delays across three releases and found that the same core data sets were needed each time.”
“I worked with developers and environment support to create reusable baseline data, documented ownership and moved data preparation into refinement and sprint planning. I also added a quick readiness check before regression started.”
“The average delay waiting for data fell from roughly two days to a few hours. Regression started on time in the next three releases and we reduced last-minute overtime without cutting test scope.”
Example 4: improving an approval process
“A purchase-approval process required every request to pass through four managers even when the value and risk were very low. Staff were waiting several days for routine approvals and managers were spending time on decisions they almost always approved.”
“I analysed six months of requests, grouped them by value and exception type and proposed a tiered approval model. I involved finance and compliance early because simply removing approvals would have created control concerns. We agreed thresholds, an audit sample and clear escalation triggers.”
“After implementation, low-risk requests were normally approved the same day, manager approval volume reduced by around 40% and audit sampling found no deterioration in compliance.”
A shorter answer
“Our team was spending several hours each week manually reconciling two systems. I mapped the causes of the mismatches and found that most came from inconsistent data-entry rules. I agreed a single validation standard with both teams and introduced an automated exception report so staff only reviewed records that genuinely needed attention. Weekly reconciliation time fell by about 60% and the error backlog stopped growing.”
What the interviewer is looking for
This question can test several capabilities at once: initiative, analysis, problem solving, stakeholder management, delivery and continuous improvement. Senior roles will usually require more than spotting a small efficiency. They want to understand how you judged priorities, influenced others and made sure the change delivered value.
How to make your example stronger
- Use a before-and-after measure whenever possible.
- Explain why the old process existed; do not imply everyone before you was incompetent.
- Show how you tested the change before rolling it out widely.
- Mention controls, risk or unintended consequences where relevant.
- If people resisted the change, explain how you understood and addressed the concern.
- Describe how you made the improvement stick: documentation, ownership, automation, training or monitoring.
Common weak answers
“I created a spreadsheet” is not automatically a process-improvement example. The spreadsheet matters only if you can explain the problem it solved and the result.
“I told my manager we should change it” also stops too early. Unless the role is extremely junior, the interviewer will want to know what you did to develop, influence or implement the idea.
Avoid examples where the result is purely subjective. “Everyone liked the new process” is weaker than evidence about time, quality, cost, customer outcomes, errors or throughput.
Questions similar to “Tell me about a time you improved a process”
- Tell me about a time you streamlined a process.
- Describe a change you introduced that improved efficiency.
- Give an example of a system or process you improved.
- Tell me about a time you challenged the usual way of doing something.
- How have you used data to improve a process?
- Tell me about a continuous-improvement idea you implemented.
More process improvement examples
Automating a complaints process
“I was asked to review and document a customer-complaints process that relied heavily on staff manually checking folders, opening several systems and copying information into a complaint file. I shadowed colleagues for a week so I could understand the work before suggesting changes.
I identified two practical opportunities: automatically notifying the team when a new complaint arrived and using existing data feeds to bring the information staff needed together without opening each system separately. I mapped the proposed process and passed the recommendations to the programme manager, who used them to create an improvement project.
Once implemented, the changes reduced the time required to complete a complaint file by around 50%. I also identified a further automation opportunity but deliberately did not recommend it at that stage because the available resources did not make it viable.”
Improving customer onboarding
“In a Business Analyst role, I reviewed a manual customer-onboarding process that was creating delays and avoidable errors. I mapped the bottlenecks, identified repetitive tasks that could be automated and worked with the relevant teams to select and implement onboarding software that centralised data and provided real-time updates.
After implementation, onboarding time fell by around 30% and the error rate reduced by roughly 20%. The change also released staff time for higher-value work. The key lesson was that successful process improvement depends on understanding the existing process first, then choosing automation only where it genuinely removes waste.”
Final answer structure
Example 5: automating repetitive invoice data entry
“In an accounts role, contractors around the country regularly emailed expense reports and invoices that had to be manually entered into our accounting system. The work took around 20 hours each week and was repetitive, so I researched whether the data-entry process could be automated before taking an idea to management.”
“Once I had identified a workable approach, I presented the expected time saving and controls to my managers. They approved the change and an IT contractor automated the data transfer. I retained a quality-check step rather than removing control completely.”
“The weekly effort fell from roughly 20 hours to around one hour of quality checking, releasing about 19 hours for higher-value work. The useful part of the improvement was not simply automation; it was researching the option, getting approval and retaining an appropriate control.”
Keep the setup short, spend most of the answer explaining what you personally did, and finish with a measurable result. If the interviewer remembers only one thing, you want it to be that you found the real problem and delivered an improvement that can be proven.