Screenshot the information that depends on appearance or spatial structure
- Architecture and sequence diagrams.
- Roadmaps, timelines, and dependency maps.
- Spreadsheets, budget tables, and metric dashboards.
- Product mockups, Figma screens, and before/after UI states.
- Code, configuration, terminal output, and error messages.
- Whiteboards, equations, flowcharts, and decision matrices.
Capture the frame when the speaker is referring to it
The best moment is usually when the presenter explains why the visual matters. The timestamp then links what was shown to the conversation that interprets it.
Skip screenshots that add no retrieval value
- Title slides and decorative imagery.
- A slide whose full meaning was already captured clearly in the transcript.
- Repeated frames where nothing material changed.
- Participant grids unless who was present is itself important.
- Sensitive information you do not need to retain.
Prefer fewer high-value screenshots
A hundred screenshots create another archive to search. Capture the frame only when future you would lose meaning without seeing it.
Place the image beside the topic it explains
A screenshot is most useful when it appears beside the relevant summary section or can be retrieved with the discussion later. Avoid a detached image dump that forces the reader to reconstruct context manually.