Capture what-worked retro notes
Distils a short structured retro from the educator's raw post-event observations — what worked, what didn't, what to change — written into the event log for future iteration.
In / outEducator's raw post-event observations → Structured retro entry (worked / didn't work / change next time) for the event log
You might say…
“I make the same mistakes every quarter because I never write down what I noticed — I want the retro done while it's fresh, even if it's only five lines.”
What it does
Distils a short structured retro from the educator's raw post-event observations — what worked, what didn't, what to change next time — written into the event log so future iterations of the recurring slot improve. Used as a single reflective judgement after the recap is sent.
Trigger: Use after the event recap is sent to capture retrospective notes while observations are still fresh.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation