Template

Keep a hypothesis–test–result ledger

Without notes, troubleshooting quietly turns into reruns and folklore.

About 1 min read

Before you use it

Use when
  • A diagnosis spans many attempts, people or configuration changes.

Keep this limit in mind

  • The ledger is not a dumping ground for secrets, personal data or unverified blame.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

A template to use

[time] Hypothesis: [hypothesis]. Test/change: [action]. Observed: [result]. Interpretation: [what this weakens or supports]. Rollback/state note: [state].

Why it matters

Record each active hypothesis, the test used, the observed result and what changed because of it. Also record deliberate system changes and how to undo them. Keep entries factual enough that a new investigator can see which paths are closed, which remain open and whether the environment has drifted during the search.

An example

After increasing a timeout for one test, record both the latency result and the fact that the timeout must be restored.

Check your result

A second person can avoid repeating a completed test and can reconstruct material state changes.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingKeep a hypothesis–test–result ledger

Evidence and sources
Supports

Google SRE recommends recording hypotheses, tests and observed results so investigations do not repeat work or lose the path back to the pre-test state.

Do not place credentials, regulated data or unnecessary personal information in an incident notebook.

Effective Troubleshooting · Test and Treat; investigation notes

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details