Write a post-mortem without blame

Good software teams write a blameless post-mortem after an outage: what happened, when, why, and what will change, without hunting for someone to punish. The idea is that blame makes people hide information, while curiosity finds the real causes.

Do the same for your own setbacks, a few days or weeks after, when you are calmer. Write five short sections: what I aimed for, what happened, the causes (in my control and not), what I would do differently, and what I will keep doing. Write "the plan had no buffer" rather than "I am lazy".