Test disabling is a major pain point for sheriffs at the moment. Ideally, we want to make it possible to disable tests with just one click in the UI, but this is a big task, so we will do this in a series of steps. This is what I imagine our approach being: 

1. Scope out the work required by finding all of the different test types sheriffs have to deal with and recording how they currently disable those tests. (Existing documentation for reference: https://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium/handling-a-failing-test )
2. Using our findings from step 1, write up a playbook for test disabling with entries organized by type of test that sheriffs can easily follow in the iterim. 
3. Link tests in sheriff-o-matic to entries in this playbook. 
4. Go through the list of test types and implement automated methods to disable each of the test types in order of impact/effort ratio. 
5. As we implement a 1-click method of disabling each test type, replace the playbook links with "Disable Test" links. 

Along the way, if we notice that different test disabling methods might make more sense to unify closer to the source rather than building automation on top of, it might make sense to discuss this with relevant teams.