Discover and read the best of Twitter Threads about #Operability
Most recents (2)
We are LIVE tweeting the panel discussion with @doctorsumitseth @RVlahutin @sharads @aurora_ravi @Hiroakitanikkei and @erinwatsonlynn
Stay tuned for updates!
Join us using this link:
#Raisina2022 #RaisinaDialogue
Stay tuned for updates!
Join us using this link:
#Raisina2022 #RaisinaDialogue
.@doctorsumitseth: e–KYC, e-signatures are an outcome of #digital transformation, where the last man standing has also benefited. This is the silent revolution that has transcended in India; from the #MissedCall economy to #4G penetration
#Raisina2022
#Raisina2022
.@sharads: #Internet committed the original sin: It became an advertising-supported web. It created an ecosystem where the big three companies have information about us on the internet.
#Raisina2022
#Raisina2022
How should you decide if an incident merits a post-incident review?
The answer isn't "if it's a P1 or P2, forget P3s". In fact, it's the wrong question to be asking... #Operability 1/n
The answer isn't "if it's a P1 or P2, forget P3s". In fact, it's the wrong question to be asking... #Operability 1/n
Many orgs I work with have a policy of "do a review if the incident was a P1 or a P2". Lower priority incidents don't get a review.
This might be due to a high volume of P3s from untuned alerts, friction in the incident review process, lack of emphasis on improvement, etc. 2/n
This might be due to a high volume of P3s from untuned alerts, friction in the incident review process, lack of emphasis on improvement, etc. 2/n
At best, the incident review process involves team members working together to uncover a shared timeline and improvement actions.
I'd call this a "shallow analysis" that pre-dates an understanding of resilience engineering, operability, the work of @AdaptiveCLabs etc. 3/n
I'd call this a "shallow analysis" that pre-dates an understanding of resilience engineering, operability, the work of @AdaptiveCLabs etc. 3/n
