Run a Premortem on the Fall Catalog
Run a project premortem to surface publishing risks before launch execution.
A fall catalog looks on track at kickoff, but hidden dependencies could force expensive late changes. Project premortem: assume the project failed, identify why, then prevent the most likely causes. The common trap is asking 'What risks do we see?' in a room where people want to appear aligned. That question often produces polite, shallow answers. The premortem prompt makes risk naming safer. State the failure It is six weeks from now. The fall catalog missed sales conference and required a rushed PDF patch. Use a vivid failure so people stop defending the current plan. List causes silently Each person…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in