Skip to content

How to explain results without exact metrics

You do not need to invent a number to describe useful work. When exact metrics are unavailable, explain what changed, what evidence you have and how far that evidence supports your conclusion.

By Moriya Works, the maker of ResumeDrill. Updated .

Inventory the evidence you actually have

Look for an adopted process, a completed handover, a resolved defect, stakeholder feedback or a decision informed by your work. These are different kinds of evidence, so name them accurately. A colleague saying a tool feels faster is feedback, not a benchmark. An approved proposal is evidence of a decision, not proof of a later business result.

Replace precision with specificity

Describe the before-and-after workflow in concrete terms. Perhaps people previously searched several documents and now used one checklist; perhaps an error stopped reproducing under the test conditions. State those conditions. Avoid words such as eliminated, transformed or guaranteed when you observed only a limited case.

Handle requests for a number directly

If asked for the percentage, say that you do not have a reliable figure and explain what you can support. If you remember a rough estimate, label it as an estimate and explain its basis. Only retrieve additional evidence through sources you are allowed to access. You can also explain what you would measure next time without pretending you measured it then.

A worked example

This is a fictional teaching example, not a customer’s resume or a script to copy. Use the structure with facts from your own experience.

Created a shared checklist for monthly reporting.

What impact did your checklist have?

Too vague

“It probably saved around half the team’s time.”

More specific

“Previously, the reporting steps were spread across chat messages and individual notes. I consolidated them into one checklist with owners and links to the inputs. The team used it for the next reporting cycle, and the manager asked us to keep it as the standard reference. We did not track time saved.”

Be ready for the follow-up

How would you measure the impact next time?

I would agree a baseline for preparation time and count missing-input follow-ups across comparable cycles. I would also record changes in workload so we did not attribute every difference to the checklist.

Adoption is an observable result. The proposed measurement plan shows learning while keeping it separate from what actually happened.

Try a short resume drill

Read the question aloud and pause to form your own answer. Then advance the sample to explore the follow-up and feedback.

From your resume to a real answer
A line on your resume

“Created a shared checklist for monthly reporting.”

Explain the work

What impact did your checklist have?

Example answer“Previously, the reporting steps were spread across chat messages and individual notes. I consolidated them into one checklist with owners and links to the inputs. The team used it for the next reporting cycle, and the manager asked us to keep it as the standard reference. We did not track time saved.”

Check your answer

  • Identify an observable change.
  • Name the evidence source without exposing confidential material.
  • Distinguish feedback, estimates and measurements.
  • State the measurement limit plainly.

Pick the least clear part and practise it again. Keep a few factual prompts rather than memorising the example word for word.

Now try it with your experience.

ResumeDrill turns the work on your resume into practice topics, questions and follow-ups.

Practise with your resume

Keep practising

Browse the full practice library