Last company, yes. Stored in the wiki but eventually some teams left a link in the wiki and moved the runbook to the repo (multiple services, each with their ow

Last company, yes. Stored in the wiki but eventually some teams left a link in the wiki and moved the runbook to the repo (multiple services, each with their own repo). Started when someone who didn't write a thing could be paged for a thing. We also strove to have all alerts related to our team's services routed to our team and we rotated on call weekly. Standard process was, as on call engineer, to update runbooks as needed. Each runbook had key debugging info, a list of alerts with workarounds or suggestions for digging deeper, links to dashboards, stuff like that. Super useful. A runbook missing info would come up in stand up or retro. We really relied on good runbooks for things we had yet to automate into self-healing systems. New place, we have some basic runbooks in the wiki but we have room to grow in this area. Coincidentally, the new company is about the same size as the old one was when we started to invest in runbooks.