82,903
edits
Runbook: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 3: | Line 3: | ||
So: a cheat sheet for steering complex but stupid machines. As such, the [[runbook]] has a natural attraction for a [[chief operating officer]], who looks upon employees in exactly those terms. so expect to see [[runbook]]s applied to the [[operations]] department, especially when it is going through a period of stress or significant change. In the wild world of negotiation, they are called “[[playbook]]s,” which makes them sound fun. | So: a cheat sheet for steering complex but stupid machines. As such, the [[runbook]] has a natural attraction for a [[chief operating officer]], who looks upon employees in exactly those terms. so expect to see [[runbook]]s applied to the [[operations]] department, especially when it is going through a period of stress or significant change. In the wild world of negotiation, they are called “[[playbook]]s,” which makes them sound fun. | ||
Judge for yourself how machine-age dogma has infected operations management orthodoxy, by this paragraph from Wikipedia: | Judge for yourself how machine-age {{t|dogma}} has infected operations management orthodoxy, by this paragraph from Wikipedia: | ||
:“''Operational [[runbook]]s may be tied to IT Infrastructure Library (ITIL)<ref>No idea, sorry.</ref> incidents to allow repeatable processes<ref>AKA drudgery.</ref> supporting specific aspects of the [[service catalog]]. The [[runbook]] is typically divided into routine automated processes and routine manual processes. The [[runbook catalog]] begins with an index of processes covered and may be broken down in outline form to align the processes to the major elements they support in the [[service catalog]].''” | :“''Operational [[runbook]]s may be tied to IT Infrastructure Library (ITIL)<ref>No idea, sorry.</ref> incidents to allow repeatable processes<ref>AKA drudgery.</ref> supporting specific aspects of the [[service catalog]]. The [[runbook]] is typically divided into routine automated processes and routine manual processes. The [[runbook catalog]] begins with an index of processes covered and may be broken down in outline form to align the processes to the major elements they support in the [[service catalog]].''” | ||