84
The Scream Test
(eviltoast.org)
I work for a company that works for a company that works for a company.
We have clients that are clients of clients, and may be direct clients in some other aspect.
We host services for these entities.
That is all fine until they don't pay us.
When they don't pay us, there are multiple rounds of contacting someone who will contact someone who will contact someone. Someday.
Sometimes, someday does not arrive.
At that point, we conduct the Scream Test.
The essence of the Scream Test is:
- This thing is theoretically not needed.
- Let's turn it off.
- And see who screams?
We shut down some stuff today. Waiting on the cacophony...
Is the official name for this "the scream test"?
I do this in lots of jobs; I tend to come in on cleanup jobs after gross incompetence, sometimes for many years. In addition to fixing problems, I have to help companies learn what should be happening and realign them to normal operating practices. Stopping pointless, worthless, outdated and redundant practices are something I do, and sometimes I apply the method above, though with many fewer degrees of separation than you have to those who may be affected. I find cutting pointless stuff to be one of the best ways to focus energy on things that do matter, get people to a better place and sometimes even save money doing it.
Ya man. Google it. I'm not that creative. Did not make it up.
Interesting, results seem to be focused in IT as a somewhat common approach but I'm not in IT, curious it has settled there in the vernacular.