investigate

Root-cause debugging systematically identifies the actual source of software failures rather than patching surface symptoms. It enforces a strict investigation process that collects evidence and forms testable hypotheses to ensure lasting fixes.

To debug using a root-cause hypothesis, work through four phases: investigate, analyze, hypothesize, and implement. You gather symptoms, read code paths, check recent changes, reproduce the issue, and form a testable hypothesis for verification.

The best way to structure a debugging workflow is to follow defined phases that lock scope when needed. This disciplined approach guides you through collecting symptoms, reading code, checking recent changes, and recording evidence and telemetry for verification.

To reproduce an issue and collect evidence during an investigation, systematically gather symptoms and check recent changes. The workflow enforces recording evidence and telemetry throughout the process to verify your root-cause hypothesis.

You should lock scope during a root-cause investigation when the debugging task expands beyond its initial boundaries. Enforcing a strict root-cause approach with locked scope prevents drift and ensures you implement a fix for the actual failure.