Super proud to be an early partner for @TrustVanta's Connectors API, making it easier than ever for Kintaba users to automatically keep their IR compliance records up-to-date! #compliance#incidentresponse#soc2
https://t.co/i6B01Ueqbp
Our automation engine makes it easy to set your IR team up for success after the incident with postmortem defaults based on tags, severity levels, and even responders!
๐ฅ Incidents are critical moments when all the red tape falls away and people (esp. ๐ on-calls) come together to save the day.
Kintaba's people-focused ๐ reporting helps teams recognize those who keep your company strong during crisis.
Try it ๐ https://t.co/MvfbOq16BJ
Fear of declaring an incident too early is a common barrier to effective IR. To combat this internally we use a special "Pre-SEV" level that lets early investigation happen in a structured/recorded way without triggering any notifications or automations until it's escalated.
ICYMI: Great writeup on the importance of automating IR practices at AirBNB: โNo matter how an incident is detected, having a single intake funnel for all incidents is crucial for effective incident detection.โ https://t.co/5K5954qn0u
There's nothing scarier than a manager who declares that "on their team, there are no incidents." The best teams work hard to encourage incident response as an open and positive part of operations. https://t.co/4PvQIjZYsE
Positive culture is at the core of a successful incident response practice. So many great talks on this topic from earlier this year at #irconf worth checking out if you couldn't attend๐ https://t.co/8gfatO46zT.
If you're interested in #CustomerSuccess - this is the podcast for you. I sat down w/ @mraaronwoods - Sr. Manager of #CustomerSuccess at @LaunchDarkly ๐
Later joined by @john3gan to discuss the importance of the customer voice in incident response.
https://t.co/GNWjeFE1Tb
We think a lot about #CustomerSuccess when we think about #IncidentResponse because it turns out that more often than not those teams identify emerging critical events long before the technical indicators catch up.
Are you empowering your CS teams with IR
best practices?
This is starting to touch the world of philosophy and the discussions around whether we even have free will. Regardless, thinking about the historical & systemic context will always be more fruitful than playing the blame game ๐ฏ cc @norootcause
https://t.co/Zqrpy21LiO
We werenโt able to make it to #KubeCon EU so weโre grateful for people like @jkriggins documenting what happened on the ground. Great stuff from @smourapina
https://t.co/UOLg25Ys6g
Have you gotten a chance to see @themortalemily 's talk on the fallacy of 'repeat' incidents? Grab your popcorn -- it's 5 minutes, full of energy, and may involve dinosaurs ๐ฆ
https://t.co/rFTr2a2God
We've said it from the beginning: Incident Management needs to be a company-wide practice. Incidents and failures don't just happen within technical systems and within #SRE teams.
The more your people and teams participate, the more resilient you will become as an organization.
We're excited to be named a digital innovator by @Intellyx for broadening incident response beyond #SRE to more pieces of the organization! ๐ฅณ
https://t.co/0YTVABxeYJ
Our friend @itielshwartz from @Komodor_com talking about how embracing a positive incident culture helps developers feel confident and move fast! #IRConf