Post-event retro deck
Recall a post-event retrospective structure that produces one owner-backed improvement.
Retro flow FACT Use FACT for a 12-minute catering retro. Story vs. learning Which retro move turns event stories into improvement? Retrospectives need action ownership to matter. Objection We are too busy to debrief. The next event starts tomorrow. This is the common reason catering teams repeat preventable errors. Your line That is exactly why we will do 12 minutes now: one repeat pattern, one owner, one change before tomorrow. Skipping the retro saves minutes and spends the same mistake again. It keeps the meeting small and tied to the next event. Owner check What must every retro action include?…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in