Writing recaps

I write a lot of recaps.

Recaps for teams to run a project forward based on my vision.
Recaps for stakeholders to see how far we’ve come.
Recaps for partnerships to see what’s on the horizon.

AI’s good at recaps. But when I use AI to help with recaps, doing recaps on my own becomes slower. I don’t subconsiously hold onto the same details I otherwise would. I don’t feel the shape of the work in my mind. I don’t remember the things that happened. Because if a machine is doing it for me, the brain says, “why bother, then?”

The problem worsens. Now, I don’t see the details. I don’t guide the work well because I don’t see the shape anymore. I forget things.

Ick.

This is why I continue to write my own recaps.

Not because the machine can’t.
Because I can’t, when it can.

I’d prefer to know the shape of my work and guide it to great places, and have to write things up periodically, than save a few minutes at the expense of my best work.