Make with Notion 2024: Notion as a curiosity engine
Based on Notion's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Notion is used as a flexible learning and reflection system, not a one-size-fits-all productivity machine.
Briefing
A long-running Notion setup is being used less as a rigid productivity system and more as a “curiosity engine” that adapts to how one person’s mind works—especially around ADHD, energy, and time blindness. The core claim is practical: when a workspace reduces decision fatigue and cognitive overload, reflection becomes easier, follow-through improves, and learning accelerates. Instead of forcing information into neat boxes, the system treats friction as data and uses journaling plus lightweight automation to turn daily experience into better decisions.
The journey starts with a permaculture design certificate in 2018, where the sheer volume of course emails, handouts, and project requirements created cognitive overload. Notion became the tool to wrangle that context switching. Over time, a set of foundational databases emerged—tags, a library, and notes/ideas—connected to content so items could be discovered by theme. After finishing the certificate, a longer diploma project pushed the customization further: project-specific requirements were stored in custom databases, then mixed with teacher notes and questions in a single tailored project page. Sharing these dashboards triggered two very different reactions: some people felt seen because the structure matched their own brain, while others criticized the use of images and argued for more data density. The response reframed the goal—reducing overload and improving understanding, not maximizing information per screen.
A major theme is that the system is designed around energy management rather than strict time management. Time blindness is addressed with a “Horizon” snapshot that surfaces what matters today (one most important task), plus project focus at the weekly level and skill focus at the quarterly level. Skill learning is supported by linking saved resources, tags, and practice items—so a new interest can be turned into a structured focus without starting from scratch.
At the center sits a daily journal that has been maintained since 2018. Entries capture “winds and highlights,” gratitude, and learning in short form, and the journal feeds other parts of the workspace. Date-based filtering lets the user review past days quickly, while reflection helps catch patterns like taking on too many clients. The journal also powers an energy management workflow: energy buttons update mood and suggest activities, which then inform what to focus on next. A daily “startup” ritual primes the brain based on energy—reviewing principles, choosing the one most important thing, and moving tasks into “now.”
Weekly review follows the same loop: close gaps, reflect without judgment, and look for recurring challenges. The system emphasizes curiosity over self-criticism, even when capacity is exceeded.
Notion also supports deep learning through side quests. When a sports injury triggered hyperfocus, a hip physio and rehab dashboard used Notion graphs and automations to track pain levels multiple times per day, connect emotions and symptoms, and log exercises with one-click buttons that update related records. Finally, curiosity extends to hobbies via custom dashboards and custom journals—like culinary, gardening, skincare, and travel—kept separate from the main workspace so messy exploration doesn’t break the core system.
Overall, the setup argues for meta-work: designing templates, prioritization, and workflows around personal friction. The payoff is a workspace that feels compassionate, flexible, and fun—conditions the creator links directly to getting things done and learning more effectively.
Cornell Notes
Notion is used as a “curiosity engine” rather than a rigid productivity tool. The system is built around reducing decision fatigue and cognitive overload, using reflection (especially a long-running daily journal) to turn daily experience into better choices. Energy management and time blindness are handled through dashboards like “Horizon,” which surfaces one key task for the day and organizes focus at weekly and quarterly levels. Buttons and automations make logging and linking information fast, so the workspace stays easy to use when motivation is low. Deep interests become custom dashboards and custom journals—kept separate from the main system—so messy learning can coexist with reliable review routines.
Why did Notion become the “entry point” for this workspace, and what problem did it solve first?
What reactions to the dashboards reveal about the system’s design priorities?
How does the system address time blindness and daily prioritization?
What role does the daily journal play beyond record-keeping?
How do buttons and automations change the usability of the system?
How does the workspace support deep learning without disrupting the main system?
Review Questions
- Which parts of the system are explicitly designed to reduce decision fatigue and cognitive overload, and how do they work in practice?
- How does the daily journal influence other workflows like energy management and weekly review?
- What design choice helps the workspace support “messy” curiosity without breaking the main productivity structure?
Key Points
- 1
Notion is used as a flexible learning and reflection system, not a one-size-fits-all productivity machine.
- 2
Core databases (tags, library, notes/ideas) emerged to tame context switching and make information discoverable.
- 3
The “Horizon” snapshot prioritizes one key task daily while organizing projects weekly and skills quarterly to counter time blindness.
- 4
A long-running daily journal drives reflection and feeds other dashboards, including energy-based recommendations.
- 5
Buttons and automations keep logging friction low—critical for ADHD-friendly usability and for real-time tracking like pain graphs.
- 6
Deep interests are handled through separate custom dashboards and custom journals so side quests don’t destabilize the main workflow.
- 7
Friction is treated as feedback for meta-work (template design, prioritization choices, and self-compassion), not as a sign the system failed.