My org is large enough to have a dedicated 24/7 front line team that look after dozens (hundereda) of things. The churn in that team is high that you can’t rea

My org is large enough to have a dedicated 24/7 front line team that look after dozens (hundereda) of things. The churn in that team is high that you can’t really give them any significant training on every system. Even a 20 minute video would take weeks to onboard for a system they’ll likely never touch. As far as I’m concerned a run book is there to stop me from being needlessly escalated to at 3am. If there’s a genuine problem then sure, I or another SME need to be contacted. Most of the time there’s a problem it is a reduction in resilience (so no need for out of hours contact), or something out of our control (loss of power in a location, failure of a circuit, in which case the 24 hour team can raise with the appropriate people. I can count on one hand the number of problems worthy of a call out, and that’s in the last 7 years. As such the first entry in my run book is “judging importance”.