HomeResourcesHow to Write a Self-Evaluation Without Metrics (+ Examples)

How to Write a Self-Evaluation Without Metrics (+ Examples)

How to show impact in your self-review when your role doesn't come with revenue or dashboard numbers, with before-and-after examples.

5 min read

Most self-evaluation advice tells you to "quantify your impact with numbers—like increasing revenue by 35%." That works if you're in sales or growth. It doesn't help much if you work in operations, project management, support, HR, or internal tooling, where your best work just makes things run quietly.

When you don't have a dashboard full of percentages, the worst thing you can do is invent them. Managers can spot a guessed "improved team efficiency by 40%" immediately. Instead, you can write a strong, specific self-review by describing what changed in the real world because of your work.

Below are the four ways to show impact without revenue metrics, before-and-after rewrites you can adapt, and a template you can copy.

Four ways to show impact when you don't have metrics

If your role doesn't produce revenue or conversion numbers, look for one of these four kinds of proof:

  1. Before and after state. How did the workflow look in January, and how does it look now? Moving from three scattered spreadsheets to one shared intake form is a concrete result even without a percentage.
  2. Problems that stopped happening. Prevention work is invisible until you name what used to break. Late closes, recurring support tickets, missed handoffs, and last-minute fire drills all count when they go down or disappear.
  3. Who uses what you built. Did another team copy your template? Do new hires use your onboarding checklist? Did leadership adopt your weekly update format? Adoption by others is strong proof of value.
  4. Scope and constraints. Shipping on the planned date after a late legal change, or covering a teammate's queue during a two-month vacancy, shows reliability under real constraints.

Before and after examples (no fake percentages)

Notice how none of the strong examples below use a made-up percentage. Each one swaps a vague claim for a checkable operational fact.

Weak (vague activity)Strong (concrete before and after)
I improved a lot of processes this year.Vendor invoices now go through one intake sheet instead of three email inboxes, so finance no longer chases sign-offs by hand.
I helped keep things running smoothly.Built a month-end close checklist; we went from three late closes last year to none this year.
I worked closely with many teams.Ran a weekly sync between finance, procurement and legal that cleared the backlog of stuck contract requests before Q4.
I supported new hires on the team.Wrote our first-week onboarding guide and paired with two new teammates; the team now uses the guide for every new hire.
I handled project risks well.Flagged a compliance gap during ERP planning and worked with legal to resolve it before it delayed our launch date.
I answered customer questions quickly.Noticed the same setup question coming up every week, wrote a help article with screenshots, and shared it with the support team so we could answer in one reply.

Examples by work type

Swap the details below with your own work, and only include a number if you can point to where it came from.

Process and operations work

  • "Moved equipment requests from ad-hoc Slack messages into a single form with automatic manager approval, ending the weekly back-and-forth with IT."
  • "Documented the quarterly access review steps so a backup owner could run the Q3 audit while I was out, with zero findings from security."
  • "Consolidated four regional vendor lists into one master tracker with renewal dates and owners, so we stopped missing cancellation windows."

Cross-functional coordination

  • "Set up a shared launch checklist across product, marketing and support so every release this half went out with help docs and a sales note on day one."
  • "Wrote a one-page summary of the two migration options with engineering and finance, which let leadership make a call in a single meeting after weeks of debate."
  • "Acted as the main point of contact between our team and the external agency during the website rebuild, keeping feedback in one thread instead of five."

Reliability and "keeping the lights on"

  • "Took over the weekly data import when a teammate left, fixed the two steps that used to fail on Mondays, and kept the report on time through the hiring gap."
  • "Reviewed every enterprise contract redline with legal this quarter so none of the quarter-end renewals slipped past their deadline."
  • "Created a pre-release test checklist after our March hotfix; we haven't had a repeat rollback on that workflow since."

Fill-in template for non-metric roles

Use these sentence starters when you're staring at a blank review form:

Before / After:
- Previously, [how the process or problem worked before]. I [what you built, changed or organized], so now [how it works today].

Prevention / Reliability:
- To prevent [problem that used to happen], I [action you took], which meant [what stopped breaking or slipping].

Adoption:
- I created [doc, checklist, template or workflow] for [original purpose], and it is now used by [who uses it and when].

Unblocking others:
- When [project or handoff] was stuck on [bottleneck], I [your specific part], allowing [team or project] to move forward on schedule.

Why you forget these details by November

Revenue numbers sit in a dashboard all year. Operational details—the stuck requests you cleared in April, the checklist you wrote in June, the launch risk you caught in August—live nowhere unless you write them down the week they happen.

That's why writing a self-review without metrics feels so hard: by review season, all you remember is "I kept things running," which sounds weak on paper.

A two-line note every Friday solves this. Write down what was broken, what you did, and what changed while it's still fresh. Look at our guide on writing a self-review when you can't remember what you did, or start from a simple weekly status update.

For role-specific lines, see our self-evaluation examples for Operations, Project Managers, Product Managers, and Customer Success.

If you want to turn a rough note into a structured story right now, paste it into the free STAR method generator. To log your work in a minute each week and get a ready-to-use brag sheet at review time—with nothing made up—start free on WinStash.

Free tool · No sign-up

Turn one work note into a STAR story

Paste a sentence or two about something you did. You get a STAR story and a resume bullet that only use what you wrote.

Try the STAR generator

Frequently asked questions

What if my manager asks me to quantify everything with numbers?

Use counts and timeframes you can actually verify: how many requests you cleared, how many days a process took before vs. after, or how many teams use the checklist you built. You don't need revenue or percentages to be specific.

How do I write about work that just kept things running?

Name the failure or friction that didn't happen. Going from three late month-end closes to zero, or running a migration with no customer escalations, turns invisible maintenance into a clear outcome.

Should I estimate a percentage if I don't have the exact number?

Avoid guessed percentages. If your manager asks where "improved efficiency by 35%" came from and you have no answer, it weakens the rest of your review. Use "about" with a real unit (like "from about six days to two") or describe the change in plain words.

What if my biggest project was a team effort?

Use "we" for the overall outcome and "I" for the specific part you owned: the bottleneck you spotted, the checklist you wrote, or the handoff you coordinated.

Write it down this week. Use it at review time.

WinStash keeps a short note from each week and turns your notes into a weekly update, a brag sheet and STAR stories, using only what you wrote.

Start free on WinStashFree plan · No credit card required

Keep reading

Self-evaluation examples by role: Operations Manager · Project Manager · Marketing Manager · Account Executive · Customer Success Manager · UX Designer