📋 Contents
- Why "no numbers" doesn’t mean "no impact"
- The before → after statement
- Way 1: problems you prevented
- Way 2: processes and systems you built
- Way 3: time you saved for others
- Way 4: quality and reliability
- Way 5: people you enabled
- Way 6: scope, volume and trust
- Way 7: decisions your work shaped
- Tie it to goals your manager already tracks
- Make the impact visible while it happens
- Collecting this evidence as you go
- Putting it together in a review
PART 1
Why "no numbers" doesn’t mean "no impact"
Advice about accomplishments often says "quantify everything." That works for sales and growth roles. For many others, the honest number does not exist, or is owned by someone else, or would take more effort to measure than the work itself.
Inventing numbers is worse than having none; a reviewer who asks "where did 30% come from?" and gets a vague answer will discount everything else you wrote. Instead, use evidence that is specific and checkable: a clear change in how things work, a named group of people affected, a problem that did not happen.
PART 2
The before → after statement
The most useful tool for unmeasured work is a simple before → after description. You state how things were, what you did, and how they are now. The reader can picture the change without any metric.
✍️ Before → after statements
Before, every new hire had to ask around to get system access, often waiting several days. I built a single access request form routed to the right owners; new hires now have access on day one.
Before, the monthly report was assembled by hand from four spreadsheets. I set up one shared source; the report now updates itself and nobody spends the last day of the month copying data.
Before, customer complaints about delivery went to whichever person happened to see them. I created one queue with an owner per region; every complaint now has a named person responsible.
💡 Rough numbers are fine if honest
If you know something took "about two days" before and "same day" after, say so with "about" or "roughly." Approximate, honest figures are credible. Precise-sounding invented ones are not.
PART 3
Way 1: problems you prevented
Prevented problems are invisible by nature: the outage that did not happen, the contract clause you caught, the deadline that was not missed. Make them visible by naming the risk and what would likely have happened.
- Caught a pricing error in the partner contract before signature that would have locked us into below-cost rates for the full term.
- Spotted that the launch date clashed with the payment provider’s maintenance window and moved it by two days, avoiding a launch with checkout down.
- Added a backup step to the weekly data export after noticing it had no recovery option; the backup was used once already when the main export failed.
Use the pattern risk spotted + action taken + what was avoided. Be careful to describe the likely consequence honestly, not the worst imaginable one.
PART 4
Way 2: processes and systems you built
A process or document that others keep using is lasting impact. The evidence is adoption: who uses it, how often, and what it replaced.
- Wrote the release checklist that all three product teams now use for every release.
- Designed the intake form for marketing requests, which replaced ad-hoc chat messages and gave the team a weekly view of incoming work.
- Created the onboarding guide for the support team; the last four hires used it as their main reference in their first month.
PART 5
Way 3: time you saved for others
Saving your own time is nice. Saving other people’s time is impact, especially if those people are expensive, overloaded, or customer-facing. Name who benefits and what they can now do instead.
| Weak | Stronger |
|---|---|
| Made a template for reports | Made a reporting template that lets account managers prepare client reviews in an hour instead of an afternoon |
| Automated some tasks | Automated the weekly invoice reminders, so the finance team no longer sends them by hand every Monday |
| Answered lots of questions | Wrote an FAQ for the top questions about the new policy; questions to HR on the topic dropped to a trickle |
Time estimates in examples are illustrative; use your own honest approximations.
PART 6
Way 4: quality and reliability
Quality work is often noticed only when it slips. Show it through consistency and the absence of repeat problems.
- Every payroll run I owned this year went out on time with no corrections needed.
- Reworked the test data setup so the same bug class has not reappeared since the fix in spring.
- Reviewed every customer-facing email template for tone and accuracy before the rebrand; none needed post-launch fixes.
PART 7
Way 5: people you enabled
Mentoring, unblocking and teaching create impact through others. The evidence is what those people can now do.
- Coached two junior analysts through their first stakeholder presentations; both now present monthly results without support.
- Unblocked the mobile team during the API change by setting up a shared test environment within a day of their request.
- Ran three internal sessions on the new CRM; the sales team switched over fully a month earlier than planned.
⚠️ Don’t take credit for their work
Describe your contribution precisely: "coached," "unblocked," "reviewed." Overclaiming other people’s results damages trust fast, especially if those people read their own reviews.
PART 8
Way 6: scope, volume and trust
When you cannot measure the output, measure the input honestly: how much you handled, how complex it was, and how much you were trusted with. Scope tells a reader the level you are working at. (Figures below are examples.)
- Supported a 60-person sales org as its only operations analyst.
- Handled every vendor contract renewal for the department, roughly two dozen a year, with no lapses.
- Was the person leadership asked to run the incident review after the October outage.
- Became the approver for all changes to the customer data schema.
Being chosen for something is evidence too. "Asked to," "selected to" and "became the go-to person for" all signal trust that a number would not capture.
PART 9
Way 7: decisions your work shaped
Research, analysis, legal review, design exploration: a lot of valuable work ends in a decision rather than a deliverable. Name the decision and your part in it.
- My competitor analysis was the basis for leadership’s decision to drop the entry-level plan.
- The user interviews I ran led the team to cancel a feature before engineering started on it.
- My risk memo moved the launch from Q4 to Q1, when support staffing was in place.
A "no" can be impact. Stopping the wrong project early often saves more than shipping a small right one, and it is the kind of contribution that disappears from memory unless you write it down.
PART 10
Tie it to goals your manager already tracks
Even unmeasured work usually supports a metric somebody owns. If your company uses OKRs or team goals, find the one your work moves and say so explicitly. "Fewer escalations to engineering" might be the support lead’s key result; your refund FAQ contributed to it, even if you cannot claim a share of the number.
✍️ Linking unmeasured work to a team goal
Team goal: Reduce time-to-first-value for new customers.
My contribution: Rewrote the setup guide and recorded three short walkthrough videos; onboarding calls now skip the basics and go straight to configuration.
PART 11
Make the impact visible while it happens
Impact nobody hears about tends to vanish by review season, especially on remote teams where your manager does not see you working. Visibility is not bragging if it is useful to others.
- Post a short note in the team channel when something ships, with one line on what it changes for readers.
- Put "what changed" in your weekly update, not only "what I did."
- Offer a 10-minute demo of a tool or process you built at a team meeting.
- When someone thanks you in a DM, ask if they would mind saying it in the channel, or save it for your records.
- Bring one impact story to each 1:1, so your manager hears it before they write your review.
PART 12
Collecting this evidence as you go
The hardest part of unmeasured impact is remembering it. Prevented problems leave no trace; nobody sends a report about the outage that did not happen. Write one line the day it happens: what you noticed, what you did, what was avoided or changed. When review season comes, you will have a list of before → after statements instead of a blank page.
☐ Did I prevent a problem this week? Note the risk and the action.
☐ Did I create or improve something others use? Note who uses it.
☐ Did I save someone time? Note who and roughly how much.
☐ Did someone thank me? Save the message.
These lines slot straight into the "beyond my goals" part of a self-evaluation.
PART 13
Putting it together in a review
When you write your review, lead with the impact category that best matches your role. A support engineer might lead with reliability and people enabled; an operations coordinator with processes built and problems prevented. Then pick two or three strong examples per category and write each as a before → after statement.
✍️ Full paragraph example
This year my main contribution was making our operations more reliable. Before, supplier delays were discovered when stock ran out; I set up a weekly check with each supplier, and we now hear about delays two to three weeks ahead. I also documented the returns process, which had lived in one person’s head; three colleagues have since handled returns on their own using it.
Frequently asked questions
Q. How do you quantify accomplishments without numbers?
Quantify what you can honestly count: scope (how many people, accounts or requests you supported), frequency, or rough before → after times. Where nothing can be counted, describe the change, who benefited, and what was avoided.
Q. How do I talk about my impact in a performance review?
Lead with the two or three changes that mattered most, each as a before → after statement tied to a team goal, and back them with a colleague’s quote or a sign of adoption.
Q. Should I try to estimate numbers anyway?
Only if you can explain how you got them. A rough, honest estimate with "about" is fine. If the number would be a guess, use a before → after description instead.
Q. What if my manager only values metrics?
Ask which outcomes matter most to them, then connect your work to those outcomes. Even unmeasured work usually supports a metric someone owns, such as fewer escalations or faster delivery.
Q. How do I show impact in a support or admin role?
Focus on reliability (things done right and on time), time saved for others, and problems prevented. These are often the core value of the role.
Q. Can I use feedback from colleagues as evidence?
Yes. Specific quotes such as "your checklist saved us during the release" are strong evidence, especially for work without metrics. Save them with dates and names.
Q. How do I talk about preventing something that never happened?
Describe the risk you spotted, what you did, and the likely consequence if you had not. Keep the consequence realistic.
Q. Is team impact okay to include?
Yes, as long as you state your part clearly. "I led the testing for the team’s launch" is better than "we launched."
This article is general guidance. Review formats, rating scales and expectations vary by company — check your own company’s guidelines alongside it.
PLAN2FOLIO
Evidence for reviews, raises and job moves — starting with one line today
Write what you did today in one line. PLAN2FOLIO sorts it into the outcomes of your role, drafts your weekly report on Fridays and gathers evidence by outcome at review time. Free to start.
Start free →