The 5 things I log every week
(so review season doesn't blindside me)

The diagnosis (the 5 signs)

You solved something and told no one. You can't quite remember what you did last month. Someone else presented your work at the last team meeting. You're "just helping" way more than your title suggests. And if someone asked you right now to describe your last six months in an interview, you'd probably blank.

None of that means you're not doing the work. It means the work isn't being written down anywhere, including in your own head.

Why it disappears

Review season doesn't sneak up because you didn't do enough. It sneaks up because memory is a terrible record-keeping system. By the time anyone asks "what did you actually do this quarter," the details are already gone not the big shipped features, those are easy. The stuff that disappears is the coordination, the decision made in a five-minute Slack thread, the thing you prevented that never became a problem in the first place.

The 5 things I log every week

Once a week, I write one line for each of these, not a report, just enough to remember later:

1. Decisions I made: A priority I defended, a feature I killed, a trade-off I owned. The "why" matters more than the "what."
Example: Killed the CRM integration request, usage data showed under 2% would use it. Redirected the team to fix onboarding drop-off instead.

2. Alignment I created: A moment where two people or teams disagreed, and I got them to a shared decision. Often the most invisible work of the week and the easiest to forget by Friday.
Example: Sales wanted a rushed feature for Friday, engineering flagged it as risky. Got both sides to agree on a scoped-down version in one 30-minute call.

3. Problems that never happened: The bug caught before it reached a client. The rework avoided because a mismatch got caught early. Success looks like nothing happening, which is exactly why it's easy to lose.
Example: Caught a permissions bug in QA before the client rollout would have exposed other clients' data.

4. A number, even a rough one: Time saved, percentage moved, anything I can attach to a decision. "Improved the flow" is forgettable. A number isn't.
Example: Simplified checkout flow, projected to recover ~4% of drop-off based on funnel data.

5. Who I unblocked: Time spent getting someone else moving again a broken environment, a stuck conversation, a missing piece of context. No output of my own to point to, but without it, someone else's work stalls.
Example: Spent 2 hours helping QA fix their environment nothing shipped, but they couldn't have tested anything without it.

That's it. Five lines, once a week, dated. Not a spreadsheet, not a formatted doc, just enough that six months from now, I'm not staring at a blank page trying to remember what I did.

Saying it without sounding like you're chasing credit

Writing it down is half the work. The other half is saying it out loud without it sounding like self-promotion.
The trick is timing: mentioned the same day, in the normal flow of work, it reads as ordinary visibility. Mentioned a week later, especially after someone else got the spotlight, it reads as chasing credit, same fact, different timing.

A short Slack message in the team channel, the day it happens, works better than any formal update: "Unblocked the DSP2 flow this morning, there was a mismatch between our implementation and [team]'s that no one had caught." Nobody reads that as bragging.

Everybody reads it as information.

If you're in the middle of this right now doing the work that holds everything together while someone else gets the spotlight, it's a hard place to sit, and it doesn't mean you're doing anything wrong. Making your work visible matters at every stage of a career, not just when you're chasing a promotion. It's worth the effort even when no one's asking you to make it.

I'm turning this into a simple tool, log a win in 30 seconds, get a ready-to-use summary whenever you need it. It's not built yet. Before I do, I want to know if this is actually useful to more than just me.

Get early access

Your email is only used to send you this checklist.
No spam, unsubscribe anytime.

Before you go

I'm a product manager sharing what I use to spot and fix broken user journeys.
This is a free resource, no strings attached.
Questions? pmworkflowlab@proton.me