Describe Your Impact When You Don’t Have Exact Numbers

A missing percentage does not make an accomplishment unusable. Begin with what you can support: the problem, your action, and an observable outcome. Then decide whether a number adds information you can verify.

Precision can come from the description of the work. Naming a decision you informed or a process someone adopted can tell a reader more than an impressive figure with no reliable source.

Compare the claim with the evidence

Consider Maya, the fictional onboarding specialist used throughout this series. In this synthetic example, she mapped handoff ownership across product, engineering, and onboarding and wrote a checklist. The team adopted it for customer launches. No launch-time measurement is available.

This proposed bullet reaches beyond those facts:

Reduced onboarding time by 30% by leading a cross-functional process transformation.

The percentage has no source. The leadership and scale claims are also unsupported. Removing the number alone would leave those problems in place.

A supported version is:

Mapped handoff ownership across product, engineering, and onboarding, creating a checklist the team adopted for customer launches.

It names the action, the scope, the artifact, and adoption. It leaves open whether the process changed launch speed.

Look for four kinds of useful evidence

Observable outcomes. What was delivered, approved, adopted, resolved, or made available? Describe what you can observe and how you know it. Delivering something does not establish every downstream benefit.

Scope. Which teams, processes, locations, or kinds of work were involved? Maya can name the three functions in her handoff map. A larger scope is not automatically better; an accurate scope helps the reader understand the work.

Adoption. Who used the result? A guide used by new colleagues or a checklist adopted by a launch team establishes use. It does not by itself establish higher productivity or fewer errors.

Decisions. Did your analysis inform a choice? Explain what you supplied, who made the decision, and what was decided. Preserve that distinction if you advised the decision-maker.

These are ways to describe evidence, not substitutes for investigating a result you could reasonably recover.

Handle partial numbers carefully

Before including a metric, check the baseline, time period, population, and your contribution. A figure from one project should not silently become an organization-wide claim.

If you only remember an estimate, mark it as an estimate in your private notes and try to verify it. Do not turn an uncertain recollection into an exact public number. If it cannot be supported, describe the outcome in terms you can explain.

Qualitative evidence deserves the same care. “Improved collaboration” may be too broad if all you know is that the team started using a shared checklist. Say what happened, then explain its significance when you have the context to support that interpretation.

Try it: strengthen one achievement

Take a bullet with a vague outcome or an uncertain metric and answer:

1. What problem or need was I addressing?
2. What did I personally do?
3. What changed that I can observe or verify?
4. Who used the work or made a decision from it?
5. What is the source, and what remains unknown?

Write one sentence using those answers. Remove claims that depend on the unknown details. Read the result aloud and answer a follow-up about your contribution.

For Maya, the useful change from “helped improve handoffs” is the supported description of ownership mapping and adoption. A fictional percentage would make that story harder to defend.

Bring the improvement back to your career record

Keep the confirmed accomplishment, the supporting source, and any remaining questions together. Reuse the same facts when you tailor a resume, write your LinkedIn profile, or prepare an interview answer.

You have completed the Master your story reading path. Return to your career inventory and add one accomplishment you can now explain more clearly.

Request free beta access to clarify achievements and build from your career evidence in ResWiz. Private beta access is free for approved participants.