No neat metric? Show what changed without making up a number

“I improved the process” asks the interviewer to take your conclusion on trust. Give them something they can picture instead. What was difficult before? What decision or action was yours? What was different when the work was complete?

The change might be a decision that previously stalled, a handoff with a named owner, a new way to check quality, or a customer question the team can now answer consistently. These are not substitutes for a missing metric. They are different kinds of evidence. Name the one your real experience supports.

If the only evidence is that you felt the work went well, the result is still too vague. If a document, an agreed decision, a completed test, or later team behaviour shows what changed, you have a more useful starting point. Say how you know, not just what you believe.

Consider this fictional support-team example. Open customer cases were passed between shifts, but the next owner and action were sometimes unclear. A candidate proposed a short handover note, tried it with the team, and reviewed the notes after the trial.

An answer that overreaches would be:

“I transformed our handovers and made customer support much more efficient.”

The story contains no reliable measure of efficiency. A more defensible answer would be:

“I noticed that some open cases reached the next shift without a named owner or next action. I proposed a handover note that captured both, and we tried it with the team. In the cases we reviewed after the trial, the next shift could see who owned the follow-up and what had to happen next. The team kept using the note. We did not measure resolution time, so I would describe the result as a clearer handoff, not a proven speed gain.”

This version gives the listener an identifiable contribution, an observed process change, and an honest limit. It does not turn a fictional example into a Loopiva customer result or claim that one person caused every later outcome.

Different forms of evidence can support different statements. A decision record can show that a choice was made and why. A revised checklist can show that the process changed. A colleague's comment can show how someone experienced the change. None of these alone proves that revenue rose, customers became happier, or work became faster.

Keep the wording as narrow as the evidence:

• If a team adopted a new handover, say that it adopted the handover. Do not call adoption a productivity gain without more evidence.
• If a stakeholder said the explanation was easier to follow, describe that feedback. Do not turn one person's view into a universal customer outcome.
• If no error appeared after a change, say what you monitored and for how long. Do not claim you prevented errors that may never have occurred.

This is not an argument against numbers. Use a trustworthy measure when you have one and understand what it represents. The problem is borrowing the appearance of precision when the underlying observation does not support it.

You may have initiated a change without being the only reason it worked. In the fictional example, the candidate proposed the note; colleagues tested and continued using it. The observed handoff became clearer within the reviewed cases. That is already a meaningful account without claiming that the candidate single-handedly improved the whole service.

Ask yourself which verb belongs to you: noticed, proposed, tested, documented, persuaded, or checked. Then name what others did. Finally, state the observed result and any plausible limit. A careful boundary makes your reasoning easier to examine when the interviewer asks, “How do you know?”

Choose one completed project for which you do not have a dependable outcome metric. Before writing a polished answer, make three short notes:

1. What changed? Describe one observable difference, not an adjective such as “better.”

2. How do I know? Name the record, decision, behaviour, or feedback you actually saw.

3. What can I not claim? Mark an unmeasured effect, a shared contribution, or another possible cause.

Now say the answer aloud. Start with the problem and your own action, then give the change and its evidence. Finish with the limit only where it matters; honesty does not require a long apology.

Try two follow-ups: “What makes you say it worked?” and “What else could explain the change?” If your first answer cannot survive either question, narrow the claim or look for better evidence. Do not invent a number to close the gap.

Loopiva offers spoken interview practice with follow-up questions, completed-session feedback, and focused coaching. You can use a real example to practise explaining the observed change and to hear where your evidence or personal role is still unclear. Then work on that part and try the answer again. This is an application of the practice process, not a claim that Loopiva verifies your project data or predicts an employer's decision.

The next interview does not require a neat percentage for every story. It requires an answer you can stand behind when someone asks what changed—and how you know.