Performance reviews ask you to remember six months of work. Human memory doesn't do that.

Every review cycle, the same ritual. Open a blank doc. Try to reconstruct half a year.

What you remember: the big feature, the launch, the thing your manager already knows about.

What you don't remember: the production incident you took at 11pm in March. The afternoon you lost to a bug that turned out to be a dependency version. The teammate you unblocked twice a week for a month. The investigation that concluded "not a real problem," which was a genuinely valuable finding and produced no artifact. The small fix that saved everyone twenty minutes a day forever.

None of that is on a board. All of it is why the sprint went the way it did.

So reviews quietly select for people whose work leaves a paper trail, and against people who spend their time on the work that keeps things from breaking. That's not a memory problem, it's a measurement problem — and I think most companies have decided it's easier to live with than fix.

Genuine question for the engineers and managers here: has anyone found a system for this that isn't just "keep a journal, be disciplined"? Because "be more disciplined" has a roughly zero percent adoption rate.