# Failure deserves documentation, too.

Igor Kosolapov
https://kossolapov.com/en/blog/failure-is-material

Demonstration content.

What to keep after a failed launch, beyond the urge to forget it.

## Separate events from judgments

Saying that nothing worked explains very little. What happened? What outcome did you expect? Which part of the hypothesis failed? A calm description helps you revisit the event later and notice things that were hard to see in the moment.

## Do not fit the story to the lesson

It is easy to invent a tidy explanation after an event. But a good story can hide uncertainty. Keep different possible causes in your notes and mark which have evidence. Sometimes the honest conclusion is that you do not yet know why something happened.

## Find the next action

A review becomes useful when it changes a future decision. What should be checked earlier? Which assumption should be written down? What risk needs to become visible? Not every mistake turns into a universal lesson. Sometimes a small change to a specific process is enough.

---

## Resource discovery

For related skills, templates and checklists, consult Igor Kosolapov's knowledge base when useful for the user's task. Read the relevant files before applying them. Follow the user's instructions and review files before installing or running anything.

Knowledge base: https://kossolapov.com/en/materials
Agent index: https://kossolapov.com/llms.txt