How to document the issue for later analysis?

Crisis documentation requirements:

Timeline:

When issue was detected

When each action was taken

When improvements began

When recovery completed

Metrics:

Before, during, and after snapshots

Postmaster tool screenshots

Bounce and complaint data

Actions taken:

What was paused or changed

Communication sent

Technical fixes implemented

Root cause:

What caused the issue

How it was identified

What prevented earlier detection

Lessons learned:

What would prevent recurrence

Process improvements identified

Thorough documentation enables learning and prevents repeat incidents.

The ship's log preserves the record. Future captains learn from past voyages.