Issue #13 · The Ops & Transformation Briefing · October 2026

When operations works, nobody notices.

A practical guide to getting invisible work into your year-end review, and into your team’s.

Issue #13 6 min read Review template Free preview
This issue in one line

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.

Subscriber issue

Get the year-end evidence template

Subscribers get the full guide: more rewrites, where to find your evidence, how to write your team’s reviews, the template and an AI prompt that will not invent numbers.

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.

Three reasons good operations work goes unseen

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.

An iceberg with a small trophy on the visible tip and a much larger hidden mass of checklists, gears, folders, a calendar and a shield below the water

“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.

Turn activity into impact in four lines

For each win, answer four questions. Then squeeze the answers into one or two sentences.

  1. What I did. The action, in plain words.
  2. What changed, or stayed reliable. Compared with before, or a standard you held under pressure.
  3. How I know. A number, a date or a document someone else could check.
  4. Why it mattered. To customers, cost, risk or the team.

Before and after

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.”

Use your real numbers. No number? Use a date, a document or a named outcome. Never estimate a figure you cannot back up.

The rest of this issue is for subscribers

The full issue adds three more rewrites, where to find your evidence, the six kinds of work that get missed, how to write your team’s reviews, the evidence template and an AI prompt. It is free, every other Friday.

Already subscribed? Use the full-issue link in your newsletter email. Unsubscribe from any issue. Privacy Policy.

Two courses for review season

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.

Reviews · Feedback
Managing Employee Performance — University of Minnesota
Coursera · Self-paced
Covers the performance review process and how to give feedback. Useful if you are writing reviews for your team this year.
View on Coursera →
Goals · Documentation
Performance Reviews and Management — SkillUp
Coursera · Four modules, around 3 hours · Intermediate · Self-paced
Setting clear, measurable goals, giving balanced feedback and documenting reviews. A good fit for the manager section of this issue. It is written around US workplace standards, so check how it maps to your own organisation’s process.
View on Coursera →