Notion Office Hours: YouTube Workflows with Thomas Frank 📹

Thomas Frank’s Notion workflow hinges on one practical idea: treat Notion less like a single all-in-one app and more like a relational “content operating system” where databases and templates connect the right tools to the right jobs. Tasks that need fast capture and smart lists live in Todoist, daily habits sit in Habit/“habits” style tracking, and Notion becomes the hub for projects, editorial calendars, and the structured artifacts that make content repeatable—scripts, research notes, b-roll plans, checklists, and publishing records.

The clearest example is how his YouTube channel runs end-to-end from a Notion database. Each video is its own project page, fed by a template that generates the scaffolding: a script area, research and notes, status tracking (research → editing → published), and a publishing checklist. The database also supports relational data—sponsor information comes from a separate sponsor table and links back to each video—so updated talking points can be copied into descriptions without retyping. He uses Evernote for the messy, early-stage “idea dump” phase, keeping Notion for when a topic is concrete enough to warrant a structured template.

Behind the scenes, the most distinctive system is b-roll management. After filming, he and his editor work through an A-roll cut (the talking-head version) and then use Frame.io for collaboration and time-stamped comments. Those comments are exported as CSV, merged into a Notion database, and then reorganized using tags and templates so b-roll work can be batched by type—overhead filming, internet screen recordings, stock footage, or After Effects animation. Notion views then slice the same database into different operational lanes: a chronological “Crono” view for playback order, a “Gather” view for what still needs to be collected, and an “Edit” view that filters by whether Premiere or After Effects steps are complete. This turns a chaotic stream of clip requests into a workflow that reduces context switching for editors.

Frank also uses Notion as a company wiki and documentation engine, leaning on quick screenshot capture and Loom screen recordings (via Loom integration) to create searchable articles that prevent teammates from watching long screencasts for small fixes. For editing feedback, he keeps “editor notes” pages inside projects, including screenshots and parameter changes.

In the Q&A, he argues that Notion’s biggest strengths are relational databases plus templating, while its friction points—like limited text precision across blocks, lack of audio recording, and missing calendar conveniences such as a true week/day view—make it less ideal as a primary note-taking or calendar tool. He compares Notion to Todoist, Asana, ClickUp, and Airtable, praising Notion’s flexibility but noting tradeoffs. For long-term writing like dissertations, he recommends looking at tools purpose-built for research and citations (e.g., Scrivener-style drafting and dissertation-focused citation/PDF annotation apps) and then integrating the structured outputs into Notion.

Overall, the workflow matters because it shows how to design a system around content production realities: capture ideas where they’re easiest, structure projects where repeatability pays off, and use integrations and CSV merges to connect specialized tools without forcing everything into one interface.