When an urgent issue arises in a tech organization, the natural instinct is often to drop everything and rush to fix it. But this “firefighting” mentality can be more harmful than helpful, leading to wasted resources, burned-out teams, and missed opportunities for real solutions. In a recent podcast episode, Kate Megaw and Ryan Smith shared their experiences and insights on how organizations can better handle urgent issues without derailing their teams’ productivity.
The True Cost of Rushed Solutions
Ryan Smith opened the discussion with a telling story: his team once lost four to five members for two and a half days trying to fix what seemed like a critical checkout issue affecting customers in another country. After investigating, it turned out the problem wasn’t with their system at all – it was caused by a popular antivirus software’s update. This incident highlights a common problem in tech organizations: the tendency to assume responsibility and rush to fix issues before properly understanding their scope and source.
The financial impact of such reactions can be substantial. As Kate Megaw points out, when multiple developers spend days on an issue that isn’t actually theirs to fix, organizations waste hundreds of thousands of dollars in resources. Beyond the immediate cost, this reactive approach disrupts planned work, delays important projects, and contributes to team burnout.
Breaking the Firefighting Cycle
The speakers identified several key strategies for organizations to break free from the firefighting cycle:
- Implement a Triage System
- Establish daily triage meetings to evaluate incoming issues
- Ask critical questions about impact, scope, and ownership
- Create a clear prioritization process for handling problems
- Empower Teams to Ask Questions
- How many users are affected?
- Is this truly our system’s issue?
- What evidence supports the problem source?
- What are the implications of immediate intervention?
- Establish Clear Ownership and Processes
- Define who owns which parts of the system
- Create clear escalation paths
- Set boundaries on when to engage development teams
- Structure Teams for Success Some effective approaches shared include:
- Creating dedicated SWAT teams for maintenance and support
- Rotating support responsibilities among team members
- Allocating specific capacity for maintenance work (e.g., 40% of team capacity)
The People-Pleasing Paradox
One interesting insight from the discussion was how organizations’ desire to please customers can actually lead to worse outcomes. As Ryan Smith noted, teams often feel pressured to accept blame and fix issues immediately, even when the problem lies elsewhere. This “people-pleasing” mentality can result in:
- Taking ownership of problems that belong to other vendors
- Creating technical debt through rushed solutions
- Setting unrealistic expectations for future issue resolution
Building a Better Response Culture
The speakers emphasized the importance of organizational culture in addressing these challenges. Key elements include:
- Leadership Support
- Leaders must support teams in questioning issue origins
- Encourage thorough investigation over quick fixes
- Recognize and reward thoughtful problem-solving
- Clear Communication Channels
- Establish proper channels for reporting issues
- Document and share triage decisions
- Maintain transparency about prioritization choices
- Root Cause Analysis
- Take time to understand recurring problems
- Invest in permanent solutions rather than quick fixes
- Document lessons learned from each incident
- Team Empowerment
- Give teams authority to question incoming issues
- Support decisions to decline non-critical fixes
- Encourage product ownership and accountability
Looking Forward
The key to breaking free from a firefighting culture lies in building organizational processes that encourage thoughtful analysis over reactive problem-solving. As Kate Megaw suggests, it’s about finding the balance between being responsive to customer needs and maintaining sustainable development practices.
Organizations need to recognize that while the desire to help customers is admirable, rushing to fix every reported issue without proper investigation can lead to wasted resources and burned-out teams. By implementing proper triage processes, empowering teams to ask questions, and supporting thorough problem analysis, organizations can create a more sustainable and effective approach to handling urgent issues.
Remember the analogy shared in the podcast: don’t be the team pushing a square-wheeled wheelbarrow, too busy to stop and implement the round wheels that would make everything easier. Sometimes, taking a pause to ask the right questions and implement proper solutions is the fastest way forward.