Too Long; Didn't Read
<a href="http://Troubleshootingtroubleshooting" target="_blank">Troubleshooting</a> on an <a href="https://hackernoon.com/tagged/engineering" target="_blank">engineering</a> team is an art, not a science. More importantly, troubleshooting is a team effort. As companies begin scaling from a five-person engineering team to 50, or from twelve customers to 1,200, troubleshooting becomes exponentially more complex. Larger engineering teams, dispersed operations, service dependencies and more customers <a href="https://smallbiztrends.com/2018/04/slack-downtime.html" target="_blank">make maintaining reliability of service more difficult</a>. The troubleshooting process starts out simple: fixing problems by getting your team into a room together — but, it gets much more complex as you grow, ballooning to require solving multiple, concurrent problems involving broad product surface areas, and several services and external dependencies across a large, dispersed team.