Research workflow
A practical workflow for turning public videos into research notes.
Video research often starts as a messy list of links. A good workflow converts those links into reviewable notes while keeping enough source context to audit the work later.
Collect fewer links, but describe why each link matters
A long watch-later list is not a research system. Before summarizing anything, group videos by purpose: background learning, competitor research, product demo, conference talk, tutorial, or interview. Then add one sentence explaining why each video is in the set.
This small step prevents accidental over-collection. If a video has no clear role, it can wait. If it does have a role, the generated brief can be evaluated against that role instead of treated as generic content.
Create a source bundle for the team
When research is shared with a team, the output should not be a single opaque answer. It should be a bundle: source links, short summaries, section notes, timestamp evidence, and any analyst comments. Markdown is useful because it can live in GitHub, Notion, Google Docs, a wiki, or a prompt without conversion work.
Youtubebrief's CLI and MCP beta are built for this direction, while the public web page is designed for one-off free briefs. The same principle applies in both cases: keep the generated note and the original source connected.
Review before using the brief in public work
A generated research brief should not be the last step before publishing. Use it to decide what to inspect. For public posts, customer-facing documents, or strategy decisions, open the relevant timestamps and confirm that the brief did not remove an important caveat.
This review step also improves future prompts and workflows. If you notice that the brief missed a visual chart, a speaker's uncertainty, or a key example, write that down. Over time, your team learns which kinds of videos are safe to process quickly and which require manual review.
Document what was excluded
A useful research packet says not only what was summarized, but also what was left out. If you skipped a video because it was off-topic, duplicated another source, or lacked enough substance, record that decision near the final notes.
This prevents future readers from assuming the brief represents every available source. It also keeps the workflow honest: a video-to-research process should make source selection more transparent, not hide it behind a polished output.
Checklist
Research handoff checklist
- Group video links by research purpose before summarizing.
- Keep source URLs and timestamp evidence in the shared note.
- Mark uncertain claims instead of rewriting them as facts.
- Use generated briefs to choose what to verify, not to skip verification entirely.
- Archive the final Markdown with the date and project context.
Related reading