Skip to content
Brian Scanlan: Improving Oncall Support with Meaningful Alarms episode artwork

Mar 29, 2021 53 min

Brian Scanlan: Improving Oncall Support with Meaningful Alarms

from Maintainable Hosted by Brian Scanlan, Robby Russell

In this episode of Maintainable, Robby is joined by Brian Scanlan, Principal Systems Engineer at Intercom. Brian shares insights into how Intercom has successfully implemented a volunteer-led on-call support system, emphasizing the importance of meaningful alarms and a consistent software environment. Summary of Topics [00:05:32] Introduction to the Guest's Background: Brian Scanlan discusses his role at Intercom and his experience with on-call practices. [00:15:10] Developing a Volunteer-Led On-Call System: Brian explains how Intercom transitioned to a volunteer-led on-call system, ensuring that alarms are meaningful and actionable. [00:20:00] The Role of Consistent Software Architecture: The impact of Intercom’s monolithic Ruby on Rails architecture on simplifying on-call duties. [00:29:46] Managing Technical Debt as Velocity Risks: Brian describes how Intercom manages technical debt through a velocity risk framework. [00:38:45] Improving Deployment Processes: The evolution of Intercom’s deployment processes, reducing the time from merge to production. [00:43:32] Treating Internal Tools as a Product: The importance of treating internal tools with the same care as external products, focusing on usability and impact. [00:50:56] Encouraging Small Wins in Productivity: How Intercom encourages engineers to address small productivity issues to prevent larger problems. [00:51:39] Balancing Innovation with Stability: Intercom’s conservative approach to engineering and how it helps maintain a stable product. Key Takeaways Meaningful Alarms: Ensure that all alarms are actionable and represent real or inevitable customer pain. Consistent Architecture: A consistent software environment, like Intercom's Ruby on Rails monolith, simplifies on-call duties and allows for greater flexibility across teams. Velocity Risk Framework: Managing technical debt by quantifying its impact on velocity helps prioritize the most impactful work. Continuous Improvement: Regular reviews and continuous improvement are essential for maintaining a sustainable on-call system. Product-Focused Engineering: At Intercom, the emphasis is on building products, not just writing code, ensuring that engineers are focused on delivering value. Helpful Links Intercom's Engineering Site Brian's Twitter Brian's LinkedIn [Book Recommendation] Choice Theory: A New Psychology of Personal Freedom, William Glasser Every episode leaves good material on the cutting room floor. The Maintainable newsletter is where it goes, along with past episodes worth another listen. Join here: maintainable.fm/newsletter

Episode details come from the podcast's RSS feed.

Embed this episode

Discover how Brian Scanlan of Intercom revolutionized on-call support by implementing meaningful, actionable alarms, and explore the benefits of a consistent software environment in scaling on-call practices.

Ready to play

Brian Scanlan: Improving Oncall Support with Meaningful Alarms

0:00 53:25

No transcript yet.

Requests help us decide what to transcribe next.

Frequently asked questions

How long is this episode of Maintainable?

This episode is 53 minutes long.

When was this Maintainable episode published?

This episode was published on March 29, 2021.

Can I download this Maintainable episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.