diagnose

Systematic debugging using evidence-based root-cause analysis involves a structured workflow that collects evidence, generates hypotheses, ranks them, and guides stepwise experimentation to identify the exact problem source reproducibly.

Investigating operations incidents across production environments requires structured evidence collection and hypothesis testing to converge on actionable solutions, ensuring reproducible incident response and accurate root-cause identification.

Structured hypothesis ranking for performance issue diagnosis works by gathering evidence and testing potential causes stepwise, allowing teams to efficiently narrow down root causes across development and production contexts.

Stepwise experimentation for root-cause analysis works by guiding teams through structured prompts to collect evidence and test ranked hypotheses, ensuring a reproducible path toward identifying the fundamental cause of an incident.

To start an incident response investigation workflow, you need to describe a problem scenario to initiate the process, which then prompts you to collect relevant evidence and form testable hypotheses for diagnosis.

You should avoid unstructured debugging and use a systematic diagnosis workflow when facing complex software, operations, or performance issues that require reproducible evidence collection and hypothesis ranking to converge on actionable solutions.