I'm finding that the best way for me to document is to realize that I'm going to go slower at everything but I'm going to document along the way. I'm in Events

I'm finding that the best way for me to document is to realize that I'm going to go slower at everything but I'm going to document along the way. I'm in Events, and typically in an event it's been low payoff to try and do anything _after_ the event. Each event is a burnout because you're always pushing yourself. I assume the same is in software too. I can't find the original article, but I often find that keeping a running note or checklist or even a pseudo-script (written like a script but not executable) are really helpful. I see what you're saying though, my run book right now is just a collection of articles that I've written and occasionally refactored to make more sense as a whole.