Unfortunately I can't share any of ours because they're all proprietary client work, but I think my teams have done a really masterful job. They're among some o

Unfortunately I can't share any of ours because they're all proprietary client work, but I think my teams have done a really masterful job. They're among some of the best I've read anywhere. For me the standout traits of a good postmortem are: * Honesty about the reality of the situation; no sugarcoating, no spin * Blameless, factual tone that avoids the passive voice * Describes technical details at a level helpful for practitioners * Makes use of other resources as needed (e.g. references corporate wiki, external ideas, blog posts) * Good writing that's easy to read and is free of grammatical ambiguities and spelling errors