Turn the event recap into learning
Run an After Action Review that compares intent, reality, causes, and next changes for a developer event.
A hackathon intended to produce 25 working prototype submissions ended with 9 submissions and uneven attendee feedback. After Action Review: intent, actuals, causes, sustain/change The common shortcut is declaring the event a success or failure from one metric before studying why the result happened. After Action Review Intent What did we set out to accomplish? Actuals What happened, using evidence rather than impressions? Causes Why did the gap appear? Next changes What should we sustain, improve, or stop? Write the original objective: 25 working prototypes using the new API, with at least 10 teams continuing after the event. The objective…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in