Record the evidence before changing the system
A useful incident note starts with what you observed: the request that failed, the time, the visible symptom and the relevant log entry. Keep real customer data and secrets out of learning notes.
Separate evidence from explanation
Write your leading hypothesis, then identify an observation that would support or weaken it. Change one thing at a time in an isolated lab so you can explain which action affected the result.
Share a reproducible account
Record your recovery action and the check that confirmed service returned. Include a cleanup step and one question for the next review. Ask a peer to explain your reasoning back to you.
This original Primus Learning exercise was drafted by a dedicated contributor and reviewed by the publication owner during the live product pilot.
Before sharing evidence, redact passwords, access tokens and other secrets from screenshots and log excerpts.