# Executing Right Moves During Crises Fin's incident management protocols and customer impact mitigation strategies - **Source:** [The Intercom Blog](https://brifing.si/source/eb59ca39-d0f1-4477-b729-bb78be348a12) - **Published:** 2026-07-14 - **Topic:** [Software & Engineering](https://brifing.si/c/engineering) - **Original article:** - **On Brifing:** https://brifing.si/s/1e0b07a7-d333-49ef-a581-e87fa25f51f2 ## The Onset of Crisis At Fin, incidents typically originate from three sources: customer complaints, sudden metric drops, or live deployment monitoring by engineers. For instance, operators spotting patterns in conversations trigger GitHub issues, engaging engineering teams via incident.io within moments. ## Customer-Centric Protocol Fin's incident framework prioritizes customer impact through rapid detection, assembling cross-functional teams, implementing safe resolutions, and maintaining transparent communication. Every confirmed incident automatically becomes the team's top priority (P1). ## Rollback Mechanism Engineers actively monitor live deployments, enabling sub-two-minute rollbacks when anomalies appear. This rapid response often resolves issues before customer impact occurs. The team continuously refines this process, recognizing that every second counts during outages. ## Role Clarity Four defined roles ensure effective response: Engineering Lead handles technical triage, Incident Commander coordinates decisions, Business Lead manages customer communications, and Resolution Owner oversees post-mortems. This structure reduces cognitive load during high-pressure scenarios. ## STRIKE Team The out-of-hours STRIKE unit handles incidents during evenings, weekends, and holidays. As first responders when primary teams are offline, they prevent dangerous delays in ownership. Senior Principal Engineer Brian Scanlan detailed this system in his DASH conference presentation. ## Behavioral Metrics Beyond server uptime, Fin tracks core user workflows like query responses. Automated alerts trigger when these metrics dip, often identifying issues before manual detection. This proactive approach minimizes mean time to detection (MTTD). ## Communication Framework Real-time updates keep Support and Sales aligned while technical teams focus on resolution. Though tools like status pages provide structure, the true differentiator is Fin's culture of disciplined transparency during disruptions. ## The Time Factor Every unresolved minute compounds customer impact and erodes trust. Fin prioritizes radical actions—like interrupting meetings—to accelerate resolution. The engineering culture treats incident response as interrupt-driven work. ## Learning Culture Post-incident analyses feed systemic improvements. Fin's reliability philosophy extends beyond load management to mastering unexpected failures. Root cause insights become preventive measures in the product lifecycle. ## Autonomous Detection Fin's AI assistant and human operators often identify pain points before dashboards. These signals auto-populate incident.io, creating a human-machine partnership that accelerates response times beyond manual monitoring capabilities. ## Flat Hierarchy Response roles emphasize clear responsibilities over rigid hierarchy. While engineers diagnose technically, commanders assume decision-making burdens. This model optimizes coordination during high-stress scenarios. ## Conclusion Fin's incident management philosophy demonstrates how customer-obsessed processes and cultural discipline outperform tooling alone. From behavioral metrics to STRIKE team, every element serves the 'team's P1' principle. Effective crisis response blends technology with organizational values. ## Sources covering this story - https://www.intercom.com/blog/doing-the-right-thing-when-things-go-wrong/ — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._