Capture what changed in the product understanding
- Usability problems someone encountered.
- Requirements clarified during the demo.
- Feature requests and the reason behind them.
- Bugs or unexpected behavior.
- Decisions to keep, change, or remove a flow.
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.