When an unplanned downtime occurs - What are the key information items that need to be relayed to everyone to create a better incident response process in your company? On the other hand, what are the sensitive data points that need to be secured? How do you balance these two?


Outline/Structure of the Talk

Everyone understands how Organisational Transparency sets the tone for a great culture. What they don't talk about is how great it is to leverage this transparency to understand and create an efficient incident response process.

The talk can be broken down into -

  1. How to build a culture of transparency with your incident response process?
  2. What are the different levels of transparency?
  3. Understanding what key information items is needed by different teams involved in the incident resolution process
  4. How to decide what data is sensitive to improve communication?
  5. Best practices & Case studies - How to make incident resolution more streamlined with Transparency? How do others do it today?

Learning Outcome

At the end of this we will see *why* certain best practices make sense, practices that aren't common but should be and other common practices which are probably not very helpful in certain use-cases.

This will also give clarity on how to set-up a good incident response process to ensure balancing feature velocity while maintaining system reliability.

Target Audience

Anyone who is interested to create an efficient incident response process and leveraging Transparency.


schedule Submitted 1 year ago

Public Feedback

    • Biju Chacko
      Biju Chacko
      VP, Engineering
      schedule 1 year ago
      Sold Out!
      45 Mins

      There are a ton of best practices in the operations world. But what really makes sense for your team? The reality is that one size *doesn't* fit all. Lean is a framework for designing and optimising processes. Let's apply it to a typical incident management process and see what comes of it.