# Debug with testable hypotheses

Taiga Learning · Worksheet
https://taiga.training/en/lessons/debug-with-ai/

Use fictional or approved information. Do not put secrets in this worksheet.

## Learning objectives
- Describe expected and observed behavior precisely.
- Choose an observation that separates competing explanations.
- Verify a correction without confusing symptom removal with cause removal.

## Exercise
Write a debugging note for a recent defect. Include expected behavior, observed behavior, affected scope, and three possible causes. For each cause, name one observation that would weaken it. Choose the cheapest safe observation first.

## Your response
- Scenario and scope:
- Assumptions and open questions:
- Proposed answer or decision, with reasons:

## Verify your response
| Claim or criterion | Evidence or test | Result or gap | Owner |
| --- | --- | --- | --- |
| | | | |
| | | | |
| | | | |

## Next action
- Action, owner, and date:
- When will you review this response?

## Principle to retain
Each debugging step should reduce uncertainty. A code change without a tested explanation can create another defect.

## Sources
- [Google SRE: Effective Troubleshooting](https://sre.google/sre-book/effective-troubleshooting/)

This worksheet supports learning. Completing it does not itself authorize a production change.