The setup The team wants to say the date out loud, but critical dependencies have not been pressure-tested. The later the review, the more expensive honest risk becomes. The framework Premortem Assume the launch failed and work backward while you can still change the plan. Imagine failure early Then turn the causes into preventive moves. Fewer surprise blockers after promises are public The best risk meeting happens while change is still cheap enough to choose. Timing choice Step 1 You can run the review now, two weeks earlier, or keep it as a near-launch checkpoint. Which timing is strongest? Facilitation…
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in