Common Questions I Get About Notion
Based on Red Gregory's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Treat Notion as a tool: build a productivity system first, then implement it inside Notion.
Briefing
Notion productivity doesn’t come from the app itself—it comes from building a system that fits the user, then using Notion as the workspace for that system. A common question from inboxes is how to get more done in Notion, and the answer centers on treating Notion as a tool rather than a ready-made productivity method. The system has to be designed (often by borrowing ideas from other “systems” creators), then customized inside Notion through trial and error. Even a well-built task-management setup only works when it matches real working patterns, energy levels, and routines.
Instead of focusing on task management, the approach described leans heavily toward reflection. The productivity setup includes a “productivity table” that logs what happened during the day: a daily input goal (for example, reading a certain number of pages or doing specific research) and a corresponding output goal (such as content creation or drafting). After the day’s work, productivity gets rated in a property, supported by trackers like mood trackers and habit trackers. The underlying logic is that tracking reveals strengths and weaknesses over time—like identifying which days of the week tend to be hardest and why. If Wednesdays consistently bring low motivation and exhaustion, the system should adapt: avoid assigning heavy tasks on Wednesdays or plan for lighter work.
Another recurring question asks why build habit trackers inside Notion when dedicated habit-tracking apps exist. The response is consolidation and preference. If Notion can do it reliably and looks good, keeping everything in one place reduces the hassle of switching between apps. There’s also a creative incentive: building inside Notion can be more fun and more customizable than many standalone apps.
Formulas are the next sticking point. The advice is practical: start with date-related functions first because deadlines and date ranges show up constantly in databases. Learn date add/subtract and date-between style logic, then move to conditional logic (“if this then that”). For filtering or tagging, the “contains” function is highlighted as a key tool for true/false checks—such as determining whether a property includes a specific tag or element. The guidance also encourages experimenting directly in the formula field by trying functions and using the built-in explanations.
Finally, the personal use of Notion is framed less as a job tool and more as a hobby and writing workspace. The day-to-day work described (waitressing and cleaning laundromats) doesn’t rely on Notion now, though it was used earlier to track laundry items, what needed cleaning, and what machines were broken. The current interest began with Notion’s gallery view, which enabled card-like layouts with images and stats—something inspired by an old baseball simulation concept. Over time, Notion became a “history hub” with timelines and events connected to people, plus a family-tree link. The same workspace also supports free writing (25 minutes daily) and plans for a future content calendar planner built around recurring tasks.
Cornell Notes
Notion productivity hinges on customizing a system to fit the user, using Notion as the workspace—not as a turnkey solution. The productivity method described emphasizes reflection: daily input/output goals, then ratings, supported by mood and habit tracking to identify patterns like low-energy weekdays. Consolidating tools into Notion is presented as a reason to build trackers there instead of using separate apps. For formulas, the recommended learning path starts with date functions and then conditional logic, using “contains” for tag/property checks. Personal use centers on hobbies—history timelines, gallery-style card layouts, and daily free writing—rather than job-specific workflows.
Why does “Notion productivity” depend more on customization than on the app itself?
How does the productivity setup described measure progress day to day?
What role do trackers play beyond recording habits?
Why build habit trackers in Notion instead of using dedicated apps?
What’s the recommended starting point for learning Notion formulas?
How is Notion used personally in this workflow?
Review Questions
- What evidence from tracking would justify changing your weekly task schedule, and how would the system adapt?
- Which Notion formula functions are suggested as the first steps to learn (and why are dates prioritized)?
- How does the approach distinguish between task management and reflection as the main productivity lever?
Key Points
- 1
Treat Notion as a tool: build a productivity system first, then implement it inside Notion.
- 2
Customize any workflow using trial and error; systems only work when they match real user habits and energy patterns.
- 3
Use reflection-based tracking (daily input/output goals plus ratings) rather than relying solely on task lists.
- 4
Track mood and habits to identify recurring low-performance days, then adjust scheduling to protect those periods.
- 5
Consolidate workflows in Notion when it’s reliable and customizable enough to replace multiple apps.
- 6
Learn formulas by starting with date functions, then adding conditional logic and using “contains” for tag/property checks.
- 7
Use Notion according to personal needs—often for hobbies, timelines, and writing—not necessarily for job tasks.