What result can you claim in the interview?
A fictional panel asks about a time you improved a service process.
The question
At a public information desk, you wrote two routing rules and trained the desk team. The end-of-month view counts the opening requests that remain in the original queue.
| Requests | |
|---|---|
| Opening requests | 120 |
| Opening requests still in the original queue at month end | 72 |
The end-of-month view does not classify why requests left the queue.
“Explain your own work and the result the team can support.”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: How do you answer the competency?
What would you do here? Open the move you’d make.
Describe the team’s actions without identifying your part
Tempting, but it misses something. The panel needs to understand which work you did.
Name your action and the result the team measured
The strong move. This gives the panel a specific example tied to the competency.
Claim the results came solely from your training
Tempting, but it misses something. The opening record does not identify what caused the change.
See how a strong candidate says it
“I would explain the opening queue, then describe the two routing rules I wrote and the training I provided. I would give the result for the team and explain how we measured it.”
Why it works: The question asks about your contribution to a service change and what followed.
Step 2: What can you say from this view?
What would you do here? Open the move you’d make.
Report 48 completions because 120 fell to 72
Tempting, but it misses something. The view does not show whether each request was completed.
Describe a 60% drop because 72 of 120 remain
Tempting, but it misses something. Sixty percent is the share that remains in the original queue.
Report a 40% queue decline and verify the statuses
The strong move. This reports exactly what the two counts support.
See how a strong candidate says it
“The original queue fell by 48 requests, or 40%. I would check the status of the 48 before I describe them as complete.”
Why it works: The view measures how many opening requests remain in one queue. It has no disposition for those that left.
Step 3: What changes after the status check?
A reviewed status report shows 30 completions and 18 transfers out of the original queue. All 18 transferred requests are still open.
What would you do here? Open the move you’d make.
Report 30 completed and keep the 18 transferred requests open
The strong move. The status records distinguish the two groups of requests that left the first queue.
Keep 48 as completions because the first queue still fell by 48
Tempting, but it misses something. The updated report shows 18 are open after transfer.
Report 72 total open because that is the original queue count
Tempting, but it misses something. The 18 transferred requests are open in the second queue.
See how a strong candidate says it
“The team completed 30 of 120, or 25%. Another 18 transferred and are still open. Across both queues, 90 of the original requests remain open. The original queue count still fell by 40%.”
Why it works: A transfer reduces the first queue count. It leaves the request open in the receiving queue.
Step 4: How do you give the final answer?
What would you do here? Open the move you’d make.
Give only the 40% change to keep the answer short
Tempting, but it misses something. The panel could hear that as a completion figure without the status explanation.
Give your two actions, the team result and the measurement lesson
The strong move. This answers the competency and keeps both the ownership and result clear.
Say you personally completed all 30 requests
Tempting, but it misses something. The result belongs to the team. Your role was the routing rules and training.
See how a strong candidate says it
“We started with 120 open requests. I wrote two routing rules and trained the desk team. The team completed 30 that month and transferred another 18. Next time I would track completions and transfers separately from the start.”
Why it works: A useful answer identifies the action, measured result and what you would improve.
The answer, in short
- Decision
- Describe the routing work and the 30 completed requests. Keep the 18 transfers separate.
- Because
- The current status records establish which requests were completed and which remain open.
- What would change it
- A later verified change in the status of a transferred request would affect the open count.
Common traps
- Name the action you owned.
- Check that the result measures what you say it measures.
Check your answer
- I gave a specific action.
- I described the initial queue measure accurately.
- I revised the outcome with the status evidence.
- I gave a clear answer with a measurement lesson.
Last reviewed Nov 11, 2026