sysadmin at a 200 person company. single IT person for way too long, now have one junior. we inherited the classic "everything lives in my head" situation and I've been trying to get our environment properly documented for 6 months.

the technical part is straightforward. network diagrams, server inventory, backup procedures, vendor contacts. I know what needs documenting. the hard part is finding time to actually write it all down when I'm also the person keeping the lights on.

what I've been doing that actually works: when I fix something or set something up, I narrate the process out loud right then. I use Willow Voice which is an AI voice dictation tool and just talk through what I did while it's fresh. "ok so the exchange hybrid migration required updating the autodiscover DNS record to point to the O365 endpoint, then running the hybrid configuration wizard, the TLS certificate needed to be the wildcard cert not the single domain one because..." you get the idea.

I talk for 2-3 minutes and get a page of documentation that I clean up later and drop into our wiki. takes way less time than sitting down at the end of the week trying to remember what I did on tuesday.

the junior is doing the same thing now. his documentation has actually been better than mine because he's explaining things at a level that someone unfamiliar would understand, which is exactly what you want in runbooks.

our wiki went from 12 pages to about 80 in 4 months. not all polished, but it exists. if I get hit by a bus tomorrow the junior can at least find the passwords and know which server does what.

other solo sysadmins, what's your documentation setup? trying to figure out if bookstack or confluence is worth the migration from our current wiki.