Learn to run a premortem with independent concerns, evidence-aware risk review, concrete preventive work, and assigned owners and review dates.
A premortem considers causes of failure before a project begins by imagining an unsuccessful outcome. Use it to identify overlooked work and scheduling risks.
Imagined causes are different from measured probabilities. Define research and preventive actions with owners and review dates.
For a delayed launch, consider missing copy, pending review, or untested operations. Atlassian’s premortem includes individual writing time. (Atlassian: Premortem)
Record concerns from actual experience before group discussion.
Record impact and evidence needed for each concern. Avoid assigning unsupported probabilities to rank risks.
Identify the copy, author, and due date so unfinished work can be tracked.
Add preventive actions to the work plan and track completion. Reconsider risks and actions as the project changes.
Update public schedules and intake information against actual readiness.
SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.
To publish a website keeping project dates and intake information current, give SpreadSite a try!
A: A method for considering failure causes and preventive actions before a project.
A: No; investigate supporting evidence separately.
A: Write causes and actions with review dates.
A: Add preventive work with ownership and dates.
