A practical guide to getting invisible work into your year-end review, and into your team’s.
In operations, good work is invisible. Nothing broke, so nothing gets mentioned.
Here is how to turn a year of steady, preventive work into evidence, for your own review and for your team’s.
The month-end closed on time. The backlog never built up. The audit came back clean.
Then review season arrives, and a year of that work gets summed up as “business as usual”. You have probably seen it happen to someone good. Maybe to yourself.
In my experience, the problem is rarely the work. It is how the work gets written down.
Success looks like nothing happening. Prevention leaves no trace. A problem you stopped is a problem nobody saw.
The rescue gets the credit. The person who saves a late month-end is remembered. The person whose month-end was never late is not.
We describe activity, not outcomes. “Managed the reconciliations” describes a job. It does not show what changed because you did it well.
“Nothing went wrong” is an outcome. Write it down as one.
On its own, though, it does not show your part. Say what you did to keep it that way, the period it covers, and the evidence.
For each win, answer four questions. Then squeeze the answers into one or two sentences.
These are illustrative examples, not wording upgrades. Use only actions and outcomes that match what you actually did.
Routine work done well
Before: “Managed the daily reconciliation process.”
After: “Ran daily reconciliations across [number] accounts with no breaks carried past month-end, so finance closed on time every month this year.”
An improvement
Before: “Helped reduce the backlog.”
After: “Redesigned the triage rules for incoming cases, cutting the backlog from [x] to [y] in [z] weeks without extra headcount.”
Prevention
Before: “Maintained data quality.”
After: “Traced a recurring data error to its upstream source and had it fixed there. It has not come back since [month], saving around [x] hours of manual correction a week.”
A project
Before: “Supported the system migration.”
After: “Wrote and tested the cutover checklist for the [system] migration. Go-live had no unplanned downtime, and the team was back at normal volumes within [x] days.”
Developing people
Before: “Trained new joiners.”
After: “Built a two-week onboarding plan for [number] new joiners. They were working the queue on their own within [x] weeks, compared with [y] before.”
Use your real numbers. No number? Use a date, a document or a named outcome. Never estimate a figure you cannot back up.
It is easy to forget work you finished earlier in the year. Start with these six places.
Your team has the same problem, and you are often the only person who can fix it for them.
If you do not write down your team’s invisible work, nobody else will.
Copy this into a document or spreadsheet. Add rows until you have ten wins, then keep the best five. Fill in the evidence column first: a win with no evidence is just a claim.
| Win | What changed | Evidence | Why it mattered |
|---|---|---|---|
| Triage redesign | Backlog down from [x] to [y] in [z] weeks | Case system report, [month] | Customers waited less, no extra headcount |
Use an AI assistant approved by your organisation, and remove confidential details before pasting your notes. Then add:
Here are my notes on what I worked on this year. Turn each one into a one- or two-sentence impact statement using this structure: what I did, what changed, how I know, and why it mattered.
Use only the facts and numbers in my notes. Do not invent or estimate any figure. Where a statement needs a number I have not given, write [NUMBER NEEDED].
Do not invent actions, outcomes or causal links. Separate what I did from what the team achieved, and flag any statement that lacks evidence.
AI drafts the narrative. The numbers come from you. Check every statement against your evidence before it goes anywhere near your review.
One for writing reviews well, one for setting next year’s goals so this is easier twelve months from now. Coursera generally offers a free first-module preview, rather than free access to a whole course. Availability, paid access and certificate options vary; check the course page before enrolling.
If this was useful, forward it to a colleague who is writing their review this year. That is how this briefing grows.
And if the formula helps you get a win recognised, email [email protected] and tell me. Please leave out anything that identifies your employer or colleagues.
Keep Sharing... Keep Learning...
This guide draws on my own experience in operations rather than research, so treat it as a practical starting point.
Sandeep
Founder, OperationsCareers · Operations Management group on LinkedIn since 2008
If someone forwarded this to you, the Operations Briefing lands free every other Friday — one idea worth knowing, what to do about it, and a practical tool each issue.
Subscribe to receive the Operations Briefing by email every other Friday. Unsubscribe from any issue. Privacy Policy.
Optional Google Analytics helps us understand how this website is used. It stays off unless you allow it. See our Cookie Policy and Privacy Policy.
