debrief

A post-event debrief works by conducting a segment-by-segment interview where the system asks one question at a time to capture specific observations. It adapts its follow-up prompts based on the event type, such as teaching, facilitation, or meetings, to drive useful specifics without unnecessary analysis.

Yes, you can generate meeting notes and todos from a coaching session debrief by capturing segment-level observations and interactive elements. The process produces a standardized Markdown document that includes overall ratings, prioritized fixes, and surfaces created todos for future improvements to revisit next time.

Yes, this structured debrief process works for lectures, class sessions, conference talks, workshops, mentoring sessions, performances, and meetings. It applies targeted, event-type follow-up prompts to ensure the collected observations remain relevant and specific to the context of your delivered event.

The best way to identify a concrete improvement for a lecture is to conduct an interview-based debrief that captures segment-level details and interactive elements. This process concludes with a final synthesis that highlights a single prioritized fix to implement in your next iteration.

When you finish a post-event reflection interview, the notes are saved as a self-contained Markdown file. The output path and filename are automatically derived from the event slug and the date, ensuring your debrief documents are consistently organized for future review.