Also make sure to retag the question if necessary. I have a sneaky suspicion they were tagged badly to begin with.

@BigHomie It probably won't hurt but it certainly can. The purpose of a postmortem is to review the facts of SB incident with as little attribution or qualitative analysis as possible. The goal is to identify not only which button was clicked incorrectly but more importantly what was the root cause that resulted in the button being couched incorrectly. By discussing it before the report had verb released we run the risk of tainting the process with incomplete, or incorrect, data.

As much as you're trying to so the postmortem correctly -- HUZZAH -- it really needs to wait until after the incident report has been written and distributed. Otherwise we end up making assumptions that can disrupt the fact-only analysis of the issue.

@Shog9 You're trying to find out what happened. That's good! That's what needs to happen. What made me uncomfortable is that most of your communication, thus far, has been unreasonably aggressive and inflammatory. It indicates an investigation to prove your correctness rather than to uncover truth. That's what I'm concerned about and what I'm trying to warn against. Not sanctity of data or chain of custody. As you implied, being held to those standards would be just silly. Removing all preconception and emotion is a necessary component to investigation, whether murder or who shrunk a sweater

@Shog9 I've been watching this bonfire to see what happens but this comment of yours concerns me, "I'm not at all convinced this is true...." (context snipped). It seems very much like you're investigating to prove malice which is a very bad sign. Speaking as a professional forensics examiner and incident responder if you make any assumptions as to outcome you MUST be relieved. It sounds like you're trying to prove malicious intent instead of determining intent. One is admirable, the other is abhorrent and completely unprofessional.

Shouldn't the BSOD represent the underlying architecture?

@Nick: This topic comes up with unfortunate regularity.