> glitch:_symptom_or_cause?
Glitch: Symptom or Cause?
A root-cause sorting game where players separate symptoms, triggers, causes, and distractions.

Active Scenario
Glitch: Symptom or Cause?
BLAST RADIUS0%
COST INCURRED0k
CLARITY50%
CONFIDENCE50%

INITIALIZING SCENARIO...
A root-cause sorting game where players separate symptoms, triggers, causes, and distractions.
Lead Anchor
Glitch
Environment
Postmortem Room
This is an interactive scenario for TinyCTO.tv titled "Glitch: Symptom or Cause?". In this scenario, players take on the role of Glitch in the Postmortem Roomto explore the technical trade-offs involving root cause analysis, postmortem, production failure, debugging. The overarching lesson of this scenario is: Glitch: Symptom or Cause? is a TinyCTO.tv interactive technical parable about the first visible failure is rarely the design failure.