Introduction to Notion with Examples
Based on Tools on Tech's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Notion is positioned as a hybrid of notes, wiki pages, and database structure, enabling long-term organization through structured data.
Briefing
Notion is presented as a long-term organization tool that merges note-taking, wiki-style pages, and database structure into one system—so scattered thoughts can be turned into repeatable, searchable workflows. The core appeal is the database approach: instead of treating notes as static text, users build structured data (with fields and tags) that can be filtered, sorted, and reused over time. That difference is positioned as why Notion can outperform simpler note apps that either lack key features (like image support) or become hard to search and maintain as collections grow.
The transcript frames Notion as a practical solution for someone who struggles to keep notes organized over the long run. After years using task tools like Todoist, the creator describes trying multiple note options—including Google Docs, workflow-focused tools, and markdown-oriented apps—yet running into limitations such as poor image handling, weak search, or the ongoing burden of maintaining organization. Notion is offered as the alternative because it reduces the need for constant manual upkeep: templates and structured layouts help turn “how do I organize this?” into “which template do I use?”
Templates are highlighted as a major productivity lever. They let the user plan how to solve a recurring problem and then repeat the setup. The transcript also mentions using multiple task lists alongside pages—especially for meetings—so the right questions and steps are always visible, reducing the chance of forgetting key items.
The main drawbacks are technical rather than conceptual. Mobile performance is described as slow to start on Android and iPhone, with particularly weak offline support on an Android tablet (the example device is a Galaxy S6). The creator says these issues appear on Notion’s roadmap, implying improvements are expected.
Several concrete examples show how Notion’s database features translate into real workflows. A recipe book uses a gallery view with images and tags (e.g., vegan/vegetarian, dinner, salad) so recipes can be filtered—such as showing all vegetarian options. It also uses a Notion extension to add web content (like a crockpot red lentil curry) while still storing extra personal data, such as metric measurements for shopping in the Netherlands and ingredient photos to quickly identify items in-store.
A wishlist and watch list uses gallery views with fields like price and ownership status. Items can be filtered to show what’s available now versus what’s saved for later, and the list can be shared with others for birthday gift ideas. Multiple galleries act as preset filters (e.g., “play” and “own”).
For content production, a board view supports a left-to-right process (ideas → map thumbnail → film → cut → b-roll → edit → publish), with drag-and-drop movement through steps and templates for faster video preparation.
Finally, a shared Japan trip planning page demonstrates Notion’s embedding capabilities: Google Maps for itinerary context, subpages for flights, food, places to visit, and packing lists, plus embedded Lucidchart diagrams and Google Drive documents for quick scanning of external materials. Overall, Notion is portrayed as a flexible system where structured data, templates, and embeds combine into a maintainable “second brain” for both personal and shared planning.
Cornell Notes
Notion is framed as a unified system that combines notes, wiki-style pages, and database structure, letting users turn messy ideas into organized, filterable information. The database approach—using fields, tags, and views—reduces long-term maintenance because content can be searched and sorted rather than manually arranged. Templates and side task lists help standardize recurring workflows, such as meeting checklists and repeatable planning. Several examples illustrate this: a recipe database with tag filters and ingredient photos, a wishlist/watch list with price and ownership fields, a YouTube production board with drag-and-drop steps, and a shared Japan trip plan built with embedded maps, diagrams, and documents. Mobile speed and offline support are the main pain points, though they’re described as roadmap items.
Why does the database approach matter more than “just storing notes” in Notion?
How do templates and task lists reduce the effort of staying organized?
What features make the recipe book example work as a practical database?
How does the wishlist/watch list use fields and views to support real decisions and sharing?
How is the YouTube video process organized for execution?
What role do embeds play in trip planning and cross-tool workflows?
Review Questions
- Which Notion view types (gallery, board) are used for recipes, wishlists, and video production, and what does each view make easier?
- How do tags and fields enable filtering in the recipe book and wishlist examples? Provide one specific filter example from each.
- What are the main mobile limitations described, and what workaround is used on an Android tablet?
Key Points
- 1
Notion is positioned as a hybrid of notes, wiki pages, and database structure, enabling long-term organization through structured data.
- 2
Templates and context-specific side task lists help standardize recurring workflows and reduce forgetting key steps.
- 3
A recipe database can be managed with gallery views plus tags, allowing filters like “vegetarian” to work as the collection grows.
- 4
Wishlist and watch lists become actionable by using fields such as price and ownership status, then sharing filtered views with others.
- 5
A YouTube production workflow can be tracked with a board view and drag-and-drop steps from ideas through publish.
- 6
Trip planning benefits from embeds (Google Maps, Lucidchart, Google Drive) so external resources stay searchable and connected to the plan.
- 7
Mobile performance and offline support are described as weak on Android/iPhone, with a browser workaround on a tablet and roadmap expectations for improvement.