How does your team actually handle runbook documentation? Ours doesn't.
Honest question — we have a strong infra team, great uptime, fast incident resolution. But every single runbook is either 2 years out of date or just doesn't exist.
The engineers who fix things are the same ones who "never have time" to document what they did. And honestly I get it — after a 2am incident nobody wants to write docs.
The knowledge just lives in Slack threads that are impossible to search, or worse, in one person's head.
Curious how other teams actually deal with this. Have you found anything that works, or is this just a universal DevOps tax everyone quietly accepts?