How to write strong resume bullets when you have no metrics

You do not need a percentage in every resume bullet. You need a reader to understand what you did, why it mattered, and which part was yours. If you cannot verify a number, leave it out. A precise description is more useful than an impressive figure you cannot explain in an interview.

Start with an evidence worksheet

For one project, write down five things: the problem, the people affected, your personal action, the artifact you produced, and what changed afterward. Use records you are allowed to access: a release note, a ticket, your own project notes, or a manager's feedback. Do not take confidential material from an employer to build your resume.

Question	Example answer
What was the problem?	Support staff checked three tools to investigate a failed payment.
What did I own?	I built the internal search interface and connected the event data.
What did I deliver?	A searchable payment-event timeline.
What changed?	Staff could see the event sequence in one place.
What can I verify?	The interface shipped and support used it; I did not measure time saved.

This is an illustrative example. It supports a useful bullet without claiming a measured productivity gain.

Replace duties with a concrete contribution

Before: “Responsible for improving support tools.”

After: “Built a searchable payment-event timeline that brought investigation details from three internal tools into one support view.”

The second version names an artifact, a workflow and a scope. It does not claim that response times fell by 30%. If “three” is not a count you know, write “multiple internal tools” instead.

For an operations role, “Helped with onboarding” might become “Created a new-hire checklist covering account access, equipment and first-week training; maintained it with the people team.” For a junior designer, “Worked on the website” might become “Designed the mobile checkout error states and documented recovery messages for engineering.” Keep only details that match your own work.

Use different kinds of evidence

Volume is one option: locations supported, documents reviewed or services maintained. Complexity is another: a migration across two systems, a workflow with several approval steps, or a tool used by people with different permissions. Completion also matters: a process adopted, a launch delivered, or an audit finding resolved.

Be careful with implied causation. “Built the onboarding guide during a quarter when support tickets fell” does not prove the guide caused that fall. Unless you can defend the relationship, describe your contribution and the observed outcome separately.

Prepare the follow-up before you publish the bullet

Ask yourself: Why was this needed? What did I personally decide? What was difficult? How do I know it worked? What would I change? If your only answer is “the team did it,” change the verb so your ownership is accurate. “Contributed the API integration” is often stronger than an unsupported “led.”

Keep a private evidence note for each major claim. This does not belong on the resume; it helps you prepare a grounded answer. If you later recover a reliable metric, add its baseline, endpoint and measurement window to that note before putting the number on the page.

A final editing pass

Choose one main contribution per bullet. Remove introductory phrases such as “responsible for.” Read the result aloud. A recruiter should be able to ask a specific question about it, and you should be able to answer from memory without inventing missing steps.

For broader guidance, see Harvard's resume guidance. To connect a bullet to its interview follow-up, read our STAR answer guide, or check your own resume. Resbetter's free preview includes analysis, three resume-linked questions and a partial rewrite. Review AI suggestions against your evidence before using them.