Meeting Workflows

How to Take Notes During Product Demos and Design Reviews

Preserve user-flow decisions, visual states, objections, bugs, requested changes, and the screenshots that make product feedback actionable.

Published 2026-09-26 · Updated 2026-10-13 · RecapFox Learning Center · By Rakesh Kalra

Capture what changed in the product understanding

Screenshot the state that triggered the discussion

For UI feedback, the visual state is evidence. Capture the screen before the presenter navigates away, especially when a layout, label, empty state, error, or interaction is being discussed.

Do not turn every comment into a requirement

Separate observations, suggestions, confirmed decisions, and assigned actions. A casual idea should not silently become roadmap commitment.

Keep customer language when it matters

Exact wording can be valuable for research and positioning. Preserve the transcript moment for strong statements about pain, value, confusion, or objections.

Link follow-up work to the evidence

The designer or engineer should be able to open the task and recover the screen, discussion, and decision that created it.

Continue from here

Evidence rule: Treat transcripts and captured visuals as source evidence. Summaries, notes, and generated answers are retrieval aids that should remain easy to verify when the detail matters.

← Back to all guides