Get AI summaries of any video or article — Sign up free
Introduction to Notion with Examples thumbnail

Introduction to Notion with Examples

Tools on Tech·
5 min read

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.

TL;DR

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?

The transcript emphasizes that Notion treats information as structured data rather than plain text. By using fields and tags, the user can create views like gallery and board layouts, then filter and sort content later—for example, filtering recipes by tags such as vegetarian/dinner/salad once the list grows. This turns organization into something repeatable and searchable over time, instead of relying on manual filing.

How do templates and task lists reduce the effort of staying organized?

Templates let the user plan a recurring workflow once—like how to prepare for a video or handle a common problem—then reuse the same structure repeatedly. Side task lists are used as focused subsets for specific contexts (such as what to ask in a meeting), ensuring steps and questions aren’t forgotten and providing guidelines that reduce the thinking load when writing or figuring things out.

What features make the recipe book example work as a practical database?

The recipe book uses a default gallery view that shows recipe sub-pages with images and text tags (e.g., vegan/vegetarian, dinner, salad). When the collection becomes large, filters can narrow results—for instance, showing all vegetarian options. The user also adds extra data beyond a web link by embedding content via an extension, storing metric measurements for shopping in the Netherlands, and placing ingredient photos at the top for quick in-store reference.

How does the wishlist/watch list use fields and views to support real decisions and sharing?

The wishlist uses gallery views with fields such as price and ownership status. A filter like “do I own this” separates items already owned from items still wanted, and sorting by price helps prioritize what can be obtained now versus what’s saved for later. Because the list is shareable, it becomes a practical gift guide for friends and family, with multiple galleries functioning as preset filtered views (e.g., “play” and “own”).

How is the YouTube video process organized for execution?

A board view maps the workflow from left to right as a sequence of steps: ideas → map thumbnail → film → cut → b-roll → edit → publish. Videos can be dragged across the board until they reach the final stage. Templates provide a quick overview for prepping a new video, including follow-up lists and prompts for filling in details like the description.

What role do embeds play in trip planning and cross-tool workflows?

Embeds connect Notion pages to external tools and content. The Japan trip page uses an embed for Google Maps to show itinerary details and supports subpages for flights, food, places to visit, and packing lists. It also uses Lucidchart embeds for diagrams and flow charts, and can embed Google Drive documents (presentations or files not stored in Notion) so they remain quickly scannable during planning.

Review Questions

  1. Which Notion view types (gallery, board) are used for recipes, wishlists, and video production, and what does each view make easier?
  2. How do tags and fields enable filtering in the recipe book and wishlist examples? Provide one specific filter example from each.
  3. What are the main mobile limitations described, and what workaround is used on an Android tablet?

Key Points

  1. 1

    Notion is positioned as a hybrid of notes, wiki pages, and database structure, enabling long-term organization through structured data.

  2. 2

    Templates and context-specific side task lists help standardize recurring workflows and reduce forgetting key steps.

  3. 3

    A recipe database can be managed with gallery views plus tags, allowing filters like “vegetarian” to work as the collection grows.

  4. 4

    Wishlist and watch lists become actionable by using fields such as price and ownership status, then sharing filtered views with others.

  5. 5

    A YouTube production workflow can be tracked with a board view and drag-and-drop steps from ideas through publish.

  6. 6

    Trip planning benefits from embeds (Google Maps, Lucidchart, Google Drive) so external resources stay searchable and connected to the plan.

  7. 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.

Highlights

Notion’s database approach turns notes into filterable records—tags and fields make organization scale beyond simple text storage.
Ingredient photos and metric conversions show how Notion can store personal context that bookmarks alone can’t capture.
A left-to-right board view provides an execution pipeline for video production, with drag-and-drop movement through steps.
Shared planning pages can combine embedded maps, diagrams, and documents into one navigable itinerary.
Mobile startup speed and offline limitations are treated as the main friction points, not the core concept of Notion.

Topics