Categorize risks to prioritize action. 'Tigers' are critical threats that will kill the project. 'Paper Tigers' are perceived risks that are actually under control, requiring only reassurance. 'Elephants' are the unspoken, uncomfortable truths that need to be surfaced for discussion.
AI tools accelerate development but don't improve judgment, creating a risk of building solutions for the wrong problems more quickly. Premortems become more critical to combat this 'false confidence of faster output' and force the shift from 'can we build it?' to 'should we build it?'.
Premortems are not just for project kickoffs. They are a powerful diagnostic tool when a project feels 'off track' or when teams are 'speaking from different sheets of music.' This can surface misalignments and communication breakdowns that sprint retrospectives might not catch.
Extend premortems beyond failure scenarios to consider overwhelming success. This reframes success as a potential failure if you're unprepared, helping teams proactively identify and plan for scaling risks and organizational readiness before they become critical issues.
A key, often overlooked benefit of a premortem is that it forces a team to agree on the project's objectives. To imagine a launch has failed six months later, the team must first have a shared, concrete definition of what success would have looked like, preventing misalignment down the line.
Avoid using premortems for vague, ongoing work like platform backlogs. Without a concrete launch or decision to frame the 'failure' against, the exercise loses focus. It devolves into a session for venting about team dynamics rather than identifying actionable, project-specific risks.