[{"data":1,"prerenderedAt":136},["ShallowReactive",2],{"glossary-page-\u002Fglossary\u002Fblameless-postmortem":3},{"id":4,"title":5,"body":6,"description":123,"extension":124,"meta":125,"navigation":131,"path":132,"seo":133,"stem":134,"__hash__":135},"docs\u002Fglossary\u002Fblameless-postmortem.md","Blameless Postmortem",{"type":7,"value":8,"toc":115},"minimark",[9,15,20,28,32,35,63,67,70,87,90,94],[10,11,12],"glossary-title",{},[13,14,5],"p",{},[16,17,19],"h2",{"id":18},"what-is-a-blameless-postmortem","What Is a Blameless Postmortem?",[13,21,22,23,27],{},"A ",[24,25,26],"strong",{},"blameless postmortem"," is a structured review conducted after an incident, outage, or major failure. Its goal is to understand what happened, why it happened, and what should change, without treating the review as a search for someone to blame.",[16,29,31],{"id":30},"why-blameless-postmortems-matter","Why Blameless Postmortems Matter",[13,33,34],{},"Blameless reviews help organizations:",[36,37,38,45,51,57],"ul",{},[39,40,41,44],"li",{},[24,42,43],{},"Learn from incidents faster",".",[39,46,47,50],{},[24,48,49],{},"Improve psychological safety"," so teams share facts openly.",[39,52,53,56],{},[24,54,55],{},"Identify system weaknesses"," in tooling, process, communication, and architecture.",[39,58,59,62],{},[24,60,61],{},"Reduce repeat incidents"," through tracked corrective actions.",[16,64,66],{"id":65},"what-a-good-postmortem-includes","What a Good Postmortem Includes",[13,68,69],{},"A useful postmortem usually covers:",[36,71,72,75,78,81,84],{},[39,73,74],{},"the incident timeline,",[39,76,77],{},"customer or business impact,",[39,79,80],{},"contributing technical and operational factors,",[39,82,83],{},"what worked well in the response,",[39,85,86],{},"follow-up actions with owners.",[13,88,89],{},"Blameless does not mean avoiding accountability. It means fixing the system conditions that allowed the incident to happen.",[16,91,93],{"id":92},"related-terms","Related Terms",[36,95,96,103,109],{},[39,97,98],{},[99,100,102],"a",{"href":101},"\u002Fglossary\u002Fincident-management","Incident Management",[39,104,105],{},[99,106,108],{"href":107},"\u002Fglossary\u002Fmean-time-to-detect","Mean Time To Detect",[39,110,111],{},[99,112,114],{"href":113},"\u002Fglossary\u002Ftime-to-restore-service","Time To Restore Service",{"title":116,"searchDepth":117,"depth":117,"links":118},"",2,[119,120,121,122],{"id":18,"depth":117,"text":19},{"id":30,"depth":117,"text":31},{"id":65,"depth":117,"text":66},{"id":92,"depth":117,"text":93},"A blameless postmortem is an incident review that focuses on system causes and process improvements rather than individual fault.","md",{"category":126,"tags":127},"B",[128,129,130],"Incident Response","Reliability","Engineering Culture",true,"\u002Fglossary\u002Fblameless-postmortem",{"title":5,"description":123},"glossary\u002Fblameless-postmortem","Bxljju3FQNRSIRgE1Z2m9NrMab3mxlwUeviioA2pxhA",1775216700862]