Thomas Frank Explains
Notion, productivity systems, and workflow automation with a focus on advanced formulas and technical implementation.
Nutrition Label
Thomas Frank Explains delivers high-fidelity tutorials that bridge the gap between productivity philosophy and technical implementation, specifically within the Notion ecosystem. Viewers can expect deep dives into formulas, API integrations, and complex workflow builds, all presented with exceptional clarity. While the content is highly practical, it occasionally features high-production satire or opinion pieces that deviate from standard tutorials.
Strengths
- +
- +
- +
Notes
- !Occasional high-production satire videos may mimic genuine tutorials; verify features exist before trying them.
- !Workflow advice is often based on personal anecdotes rather than empirical productivity data.
Rating Breakdown
Breakdown across the key dimensions we rate. Methodology →
Recent Videos
How to Add Time Tracking to Notion (For Free)
Turn Notion into the ultimate daily planner (full build)
This is why your task manager overwhelms you.
The Notion note-taking template you'll actually use (full build)
Notion just changed how databases work
Notion Finally Works Offline
Notion just added one of Excel's best features
Notion Formulas for Beginners: The Complete Course
Notion just made a huge change to databases
The Notion task manager you'll actually use (full build)
30+ new Notion features you should know about
Notion FINALLY Made Recurring Tasks Work.
I didn't think Notion would ever fix this
Layouts will make your Notion pages 10x better
Why this rating
Evidence receipts showing why each dimension is rated the way it is.
“Re-locking the Tasks database”[33:15] →
Shows domain expertise by addressing data integrity and accidental edits, a common issue for power users.
“Adding the formulas to the formula properties”[1:00:12] →
Demonstrates advanced Notion usage by writing custom code/formulas rather than relying solely on basic UI properties.
“Turning the databases into separate pages and locking them to prevent unintended changes”[1:28:30] →
Addresses a specific, real-world friction point (accidental database edits) that only arises from actual long-term usage.