Incident Management for Operations by Rob Schnepp & Ron Vidal & Chris Hawley
Author:Rob Schnepp & Ron Vidal & Chris Hawley [Schnepp, Rob]
Language: eng
Format: azw3, pdf
Publisher: O'Reilly Media
Published: 2017-06-20T04:00:00+00:00
Incident Commander Tactics:
If it appears that the Grenade Thrower has lobbed a distraction, refocus the discussion with a CAN report and stick to the verifiable facts. Facts are kryptonite to the Grenade Thrower.
Grenade Throwers often cite the possibility of an extreme positive or negative outcome as justification for actions. The IC should acknowledge all possibilities, but keep the group focused on probabilities. Possible outcomes can be initially measured by yes or no.
Ask questions focused on probabilities of occurrence right now and within numerical ranges. For example, is it possible that an asteroid will crash in to the earth and cause massive damage? The answer is yes, of course, because it’s wrong to say it’s impossible. It has happened before and even though it’s been millennia since the event, it did happen and is therefore possible, although the probabilities are minimal. Ask the question this way, “On a scale of 0 to 100%, what’s the probability that an asteroid will crash to the earth today and cause massive damage?” Be careful to cut off any answer that goes down a rabbit hole of technical definitions, like if the Grenade Thrower replies “well, what’s massive damage?”
If the answer is no to a possibility question, then the issue is solved right there. For example, is it possible to walk across the ocean? The answer is no, which makes any further discussion of the event irrelevant and nothing more than an interesting thought experiment at best. In this context, the word “probable” may be interchanged with the word “likely,” indicating a strong sense that the event or consequence may occur.
An event may be possible but unlikely, which is where the Grenade Thrower may base an opinion, argument, or justification. If needed, an IC can help defeat the Grenade Thrower by distinguishing between possible and likely/probable when sorting through options or dissension on a course of action. An IC may poll the incident response group and ask if a particular outcome to an action is possible or likely/probable. Anything possible becomes some degree of likely. The groups can then rank the likely events on a 1 to 10 scale with 1 being least likely and 10 being most likely.
Download
Incident Management for Operations by Rob Schnepp & Ron Vidal & Chris Hawley.pdf
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.
Deep Learning with Python by François Chollet(12419)
Hello! Python by Anthony Briggs(9768)
OCA Java SE 8 Programmer I Certification Guide by Mala Gupta(9658)
The Mikado Method by Ola Ellnestam Daniel Brolund(9652)
Dependency Injection in .NET by Mark Seemann(9184)
Algorithms of the Intelligent Web by Haralambos Marmanis;Dmitry Babenko(8161)
Test-Driven iOS Development with Swift 4 by Dominik Hauser(7666)
Grails in Action by Glen Smith Peter Ledbrook(7576)
The Well-Grounded Java Developer by Benjamin J. Evans Martijn Verburg(7411)
Becoming a Dynamics 365 Finance and Supply Chain Solution Architect by Brent Dawson(6467)
Secrets of the JavaScript Ninja by John Resig Bear Bibeault(6288)
Microservices with Go by Alexander Shuiskov(6218)
Practical Design Patterns for Java Developers by Miroslav Wengner(6137)
Test Automation Engineering Handbook by Manikandan Sambamurthy(6098)
Angular Projects - Third Edition by Aristeidis Bampakos(5449)
The Art of Crafting User Stories by The Art of Crafting User Stories(5026)
NetSuite for Consultants - Second Edition by Peter Ries(4978)
Kotlin in Action by Dmitry Jemerov(4926)
Demystifying Cryptography with OpenSSL 3.0 by Alexei Khlebnikov(4781)
