Hi [[ session.user.profile.firstName ]]

Blameless Post-Mortems

Following up an incident, outage, or even a successful deployment with a post-mortem isn’t a new concept. It’s easy to understand the benefits of sharing, analyzing, and understanding what went well and what didn’t. In many cases, individuals blame others, or worse, themselves for actions that may have led to an outage. By understanding the human-side of complex systems and communicating that in post-mortems, we can remove blame towards individuals and seek out the true cause (or set of causes) of incidents.
Recorded Feb 6 2015 51 mins
Your place is confirmed,
we'll send you email reminders
Presented by
Jason Hand, DevOps Evangelist, VictorOps
Presentation preview: Blameless Post-Mortems

Network with like-minded attendees

  • [[ session.user.profile.displayName ]]
    Add a photo
    • [[ session.user.profile.displayName ]]
    • [[ session.user.profile.jobTitle ]]
    • [[ session.user.profile.companyName ]]
    • [[ userProfileTemplateHelper.getLocation(session.user.profile) ]]
  • [[ card.displayName ]]
    • [[ card.displayName ]]
    • [[ card.jobTitle ]]
    • [[ card.companyName ]]
    • [[ userProfileTemplateHelper.getLocation(card) ]]
  • Channel
  • Channel profile
  • VictorOps & Raygun: A Stunning Integration Recorded: Mar 22 2016 18 mins
    Garrett Dawson
    Join Raygun and VictorOps as we dive into how our integration can make you better at your job. Whether it’s finding that bug before your customers or being able to ACK from your mobile phone, the combined features of our products ensure that you can collaborate remotely and get the context necessary to make quick decisions during a firefight.
  • The State of On-call 2015: Is it getting better? Recorded: Dec 16 2015 46 mins
    Todd Vernon, CEO, VictorOps
    What's happening with on-call? We asked over 500 people to tell us what tools they're using and how they're dealing with the on-call process. And boy did they respond!

    In this webinar, we'll talk about what changes we've seen in the survey data since last year, what challenges still remain and what topics are emerging as trending for 2016. Join us to see how you stack up against others!
  • The State of On-call 2015: Is it getting better? Recorded: Dec 9 2015 46 mins
    Todd Vernon, CEO, VictorOps
    What's happening with on-call? We asked over 500 people to tell us what tools they're using and how they're dealing with the on-call process. And boy did they respond!

    In this webinar, we'll talk about what changes we've seen in the survey data since last year, what challenges still remain and what topics are emerging as trending for 2016. Join us to see how you stack up against others!
  • ChatOps: The New Interface of DevOps Recorded: Nov 9 2015 52 mins
    Jason Hand, DevOps Evangelist at VictorOps
    The teams and organizations that are leading the DevOps movement have turned to their chat client to provide a new interface. By moving tools and command line functionality into chat, it's possible to create greater situational awareness and increase tribal knowledge. In this presentation, the audience will learn about the basics of ChatOps, its origins, and how teams who have fully adopted DevOps best practices are using it to deliver high-quality software quickly, deploy infrastructure safely, and manage incidents more efficiently than ever before.
  • Tips & Tricks to Reduce TTR for the Next Incident Recorded: Oct 27 2015 31 mins
    Jason Hand, DevOps Evangelist, VictorOps
    Resolving an incident can be a complex process that takes a lot of time and many people. According to the 2014 State of On-Call Report, most teams report that it takes 10-30 minutes to resolve an incident and on average, 5 people are needed to help with resolution.

    But it doesn’t have to be that way. In this webinar, Jason Hand will present best practices and tips for surviving every stage of the firefight - from when an alert comes in to pulling reports after it’s over. Join us to see how we do it at VictorOps.
  • DevOps Culture Shift: Expanding On-Call Responsibilities Recorded: Sep 16 2015 54 mins
    Todd Vernon, VictorOps Founder & CEO
    “I just write the code and throw it over the wall. It’s up to Ops to make it work” -- when Devs care only about coding, Ops and customers suffer.

    “It’s not my job to test code. If there’s a problem, talk to QA.” -- when Ops care only about stability, innovation and customers suffer.

    DevOps represents cultural change. Whether it’s the change of resistant engineers that don’t want to be on-call or the change of Operations teams to have more empathy towards their counterparts writing code, to the willingness of executives to embrace a culture of automation, measurement and sharing. Organizations must overcome the culture war to be able to approach the agility and productivity that organizations following a DevOps model gain. The faster they can get there, the faster these organizations can take the competitive edge away from traditional enterprises.

    In this webinar, featuring guest Forrester Research principal analyst Kurt Bittner, we will look at:
    - The current state of organizations - a separation of Devs and Ops
    - The how of DevOps - DevOps is a culture, not a product
    - The benefits of DevOps - happier customers

    As part of our panel discussion, we will answer the following questions to help you get started building a DevOps culture within your organization:
    - Why change the status quo?
    - How do I align two disparate groups?
    - How do I remove the obstacles that separate Dev and Ops teams?
    - Will customers see a difference if devs are on call?
    - Can IT start to think differently?
  • How post-mortems can close the loop on IT metrics Recorded: Aug 19 2015 35 mins
    Jason Hand, DevOps evangelist at VictorOps
    In today’s modern infrastructure, it’s imperative to have situational knowledge about what’s going on...the good, the bad, everything. The DevOps movement has taught us that monitoring is a key component of adopting the best practices of highly efficient software delivery teams. These metrics are not only useful as context during incident management but also to analyze once an outage has been resolved.
  • Real World ChatOps Recorded: Jun 25 2015 34 mins
    Jason Hand, DevOps Evangelist, VictorOps and Michael Ansel, Box
    Join Jason and Michael Ansel, from Box, as they explain what ChatOps is and how it can help different teams in your organization. You'll learn tips to get started, tools needed and emerging best practices around the topic.
  • DevOps Culture Shift: Expanding On-Call Responsibilities Recorded: May 27 2015 54 mins
    Todd Vernon, VictorOps Founder & CEO
    “I just write the code and throw it over the wall. It’s up to Ops to make it work” -- when Devs care only about coding, Ops and customers suffer.

    “It’s not my job to test code. If there’s a problem, talk to QA.” -- when Ops care only about stability, innovation and customers suffer.

    DevOps represents cultural change. Whether it’s the change of resistant engineers that don’t want to be on-call or the change of Operations teams to have more empathy towards their counterparts writing code, to the willingness of executives to embrace a culture of automation, measurement and sharing. Organizations must overcome the culture war to be able to approach the agility and productivity that organizations following a DevOps model gain. The faster they can get there, the faster these organizations can take the competitive edge away from traditional enterprises.

    In this webinar, featuring guest Forrester Research principal analyst Kurt Bittner, we will look at:
    - The current state of organizations - a separation of Devs and Ops
    - The how of DevOps - DevOps is a culture, not a product
    - The benefits of DevOps - happier customers

    As part of our panel discussion, we will answer the following questions to help you get started building a DevOps culture within your organization:
    - Why change the status quo?
    - How do I align two disparate groups?
    - How do I remove the obstacles that separate Dev and Ops teams?
    - Will customers see a difference if devs are on call?
    - Can IT start to think differently?
  • How a Control Call can Improve Incident Management Recorded: May 13 2015 20 mins
    Joni Klippert, VP Product, VictorOps
    Join our VP of Product, Joni Klippert and our Operations Support Specialist, Nate Grieb as they explain why the new VictorOps feature, the Control Call, is a game changer for on-call.

    In this launch webinar, you will hear why we built this feature, understand how exactly this feature addresses some of the common challenges of being on-call, see a comprehensive demo of the feature and learn about best practices surrounding a Control Call.
  • DevOps Culture Shift: Expanding On-Call Responsibilities Recorded: Apr 30 2015 54 mins
    Todd Vernon, VictorOps Founder & CEO
    “I just write the code and throw it over the wall. It’s up to Ops to make it work” -- when Devs care only about coding, Ops and customers suffer.

    “It’s not my job to test code. If there’s a problem, talk to QA.” -- when Ops care only about stability, innovation and customers suffer.

    DevOps represents cultural change. Whether it’s the change of resistant engineers that don’t want to be on-call or the change of Operations teams to have more empathy towards their counterparts writing code, to the willingness of executives to embrace a culture of automation, measurement and sharing. Organizations must overcome the culture war to be able to approach the agility and productivity that organizations following a DevOps model gain. The faster they can get there, the faster these organizations can take the competitive edge away from traditional enterprises.

    In this webinar, featuring guest Forrester Research principal analyst Kurt Bittner, we will look at:
    - The current state of organizations - a separation of Devs and Ops
    - The how of DevOps - DevOps is a culture, not a product
    - The benefits of DevOps - happier customers

    As part of our panel discussion, we will answer the following questions to help you get started building a DevOps culture within your organization:
    - Why change the status quo?
    - How do I align two disparate groups?
    - How do I remove the obstacles that separate Dev and Ops teams?
    - Will customers see a difference if devs are on call?
    - Can IT start to think differently?
  • Tips & Tricks to Reduce TTR for the Next Incident Recorded: Mar 24 2015 31 mins
    Jason Hand, DevOps Evangelist, VictorOps
    Resolving an incident can be a complex process that takes a lot of time and many people. According to the 2014 State of On-Call Report, most teams report that it takes 10-30 minutes to resolve an incident and on average, 5 people are needed to help with resolution.

    But it doesn’t have to be that way. In this webinar, Jason Hand will present best practices and tips for surviving every stage of the firefight - from when an alert comes in to pulling reports after it’s over. Join us to see how we do it at VictorOps.
  • Annotating Alerts: How the VictorOps Transmogrifier Reduces TTR Recorded: Feb 11 2015 22 mins
    Joni Klippert, VP Product, VictorOps
    With the Transmogrifier, you can easily maintain continuous documentation, quiet alert noise and make sure you alert the right person, every time. In this webinar, we'll explain why we built the feature, hear the CTO of 911 Labs explain how he uses the feature and get an in-depth demo of how the transmogrifier works.
  • ChatOps Unplugged - A Beginner's Guide Recorded: Feb 9 2015 43 mins
    Jason Hand, DevOps Evangelist, VictorOps
    Join us for a discussion on ChatOps and the movement to deploy, measure, and mitigate from a chat client. With more and more teams implementing methods to trigger commands from within their favorite chat clients, the time it takes to perform specific and repetitive tasks has been dramatically reduced. In providing a real-time command history to others, we can share knowledge and learn from each other faster than ever before.
  • Blameless Post-Mortems Recorded: Feb 6 2015 51 mins
    Jason Hand, DevOps Evangelist, VictorOps
    Following up an incident, outage, or even a successful deployment with a post-mortem isn’t a new concept. It’s easy to understand the benefits of sharing, analyzing, and understanding what went well and what didn’t. In many cases, individuals blame others, or worse, themselves for actions that may have led to an outage. By understanding the human-side of complex systems and communicating that in post-mortems, we can remove blame towards individuals and seek out the true cause (or set of causes) of incidents.
  • Beware of Network False Alarms: How to Reduce Alert Fatigue Recorded: Feb 6 2015 30 mins
    Jason Hand, DevOps Evangelist & Mike Merideth, Senior Director of IT at VictorOps
    If you and your on-call team feel overwhelmed or exhausted by the volume of alerts, this is for you. In it, we explore methods to not only identify and deal with alert fatigue but reduce it over time by fine-tuning your monitoring and alerting services. We'll also discuss the iterative process of identifying which data sets really represent actionable issues, which ones are redundant or overlap, and which ones are valuable only for information, and are never actionable. Join us to hear how you can make on-call suck less.
We make being on-call suck less.
Our incident timeline gives you a real-time view of the health of your infrastructure, while allowing you to collaborate with your team in the midst of a firefight. We make it easy to pull reports after the fact, reroute alerts to the right person and escalate to different teams.

All of this, along with our Transmogrifier (a new feature we created that gives you the ability to append alerts with helpful documentation), means that your team can reduce TTR and solve IT problems faster.

Embed in website or blog

Successfully added emails: 0
Remove all
  • Title: Blameless Post-Mortems
  • Live at: Feb 6 2015 10:50 pm
  • Presented by: Jason Hand, DevOps Evangelist, VictorOps
  • From:
Your email has been sent.
or close