Easy incident response for your entire company. On #slack and www. We đź’™ Customer Reliability

New York, NY
Joined December 2019
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 vanta.com/blog/introducing-v…
5
2
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 👉 kintaba.com
1
1
1
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.” medium.com/airbnb-engineerin…
1
2
1
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👉 irconf.io/.
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. anchor.fm/10kmedia/episodes/…
3
8
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 surfingcomplexity.blog/2022/…
2
Kintaba retweeted
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 🦖 youtube-nocookie.com/embed/Z…
8
3
20
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.
1
We're excited to be named a digital innovator by @Intellyx for broadening incident response beyond #SRE to more pieces of the organization! 🥳 intellyx.com/2022/05/18/kint…
Silvia Pina talking about the focus on Whyhappen rather than Whodunnit at #KubeCon "Focus on helping people cope with complexity under pressure"
1
3
6
Our friend @itielshwartz from @Komodor_com talking about how embracing a positive incident culture helps developers feel confident and move fast! #IRConf
Check out @permit_io :)
Raise your hand if a failure around two-factor auth systems has prevented you from working an incident.
1
2
Interesting article in terms of ultimately improving customer experience -- thanks John Egan from @kintaba! buff.ly/3LMvG7Q
1
2