Hacker News new | ask | show | jobs
by kwooding 1607 days ago
Recently, I was a co-organizer for a conference. The event was almost over, and we were in the process of scheduling our event postmortem when one of our fellow organizers suffered the loss of a close family member.

As you can imagine, we all became instant members of the “we need a better name for this process” club. Thank you, OP for giving us a completely viable alternative. I’m calling it a “disquisition” from here on in.
1 comments
justsomehnguy 1607 days ago
> of scheduling our event postmortem

Did your group somehow started using 'postmortem' instead of 'afterparty'? Because if every event you organize require scheduling a postmortem then it is no longer a postmortem and just a regular activity.

link
kwooding 1607 days ago
In any live event, things go wrong. Tearing in to what went well, what didn’t go well, and suggesting process changes for the next event is an important process not only for making future events easier, but also for improving the mental Health of the organizers who tend to focus on the “what went wrong” parts.

So technically, we only hold one if things went wrong.

If we ever held an event where everything went right, then yes, we’d totally call that one an afterparty.

link
justsomehnguy 1604 days ago
Yes,

> Tearing in to what went well, what didn’t go well, and suggesting process changes for the next event

is the regular [performance|postfactum|event] analysis, but it IS NOT the postmortem!

From your previous comment you understand what the term means "after death". Did you really think "after death" and "after event" are the same?

link