Notion

Build the mental model

Notion is a workspace tool built from a small set of building blocks — pages, blocks, databases, properties, views, relations, templates — that combine into almost anything.

Building Block	What It Does
Page	A single document you write and read, like a document or a wiki article.
Block	One piece of content inside a page — a paragraph, an image, a to-do, an embedded database.
Database	A structured collection of items, each with its own properties, that can be viewed in different ways.
Property	A field on a database item, like Status, Priority, or Due Date.
View	A way of displaying a database's items — Table, Board, Calendar, or List.
Relation	A link between two databases, so an item in one references an item in another.

A beginner-friendly example is a Personal Dashboard: one page linking Today, Tasks, Notes, Projects, Learning, and Resources, where Tasks/Projects are real databases. The key distinction is page (write/read) versus database (structured data).

Structured data
Easy team collaboration
Flexible dashboards
Reusable templates
Online / offline dependency
Setup complexity
Overbuilding risk
Tool lock-in

text

NOTION PERSONAL DASHBOARD
-------------------------
NOTION PERSONAL DASHBOARD
-----
+-----------------------------+
|     PERSONAL DASHBOARD       |
|           (page)             |
+-----------------------------+
     |          |          |
     v          v          v
+--------+  +--------+  +--------+
| TASKS  |  |PROJECTS|  | NOTES  |
|  (db)  |  |  (db)  |  | (page) |
+--------+  +--------+  +--------+
     |            |
     +--relation--+

Connect it to a real scenario

Tasks database

Properties: Task, Status, Priority, Due Date, Project.

Projects database

Properties: Project, Status, Goal, Deadline — link Tasks with a relation.

Resist overbuilding

Resist adding a third database or extra properties on day one.

View Tasks as a Board grouped by Status for daily work, and switch to Table view to sort by Due Date or filter by Project — the same data viewed differently is the point of a database.

Only add a third database once the two-database setup feels natural after a few weeks — growing slowly avoids the overbuilding trap that causes most people to abandon Notion.

Notion is built from pages, blocks, databases, properties, views, and relations that combine into custom workflows
A database's real power is having one set of data viewable multiple ways (table, board, calendar) instead of duplicating lists
Notion's convenience comes with real costs: online dependency, complexity, overbuilding risk, and lock-in

Try the working example

javascript

// A Notion Tasks database row, shown as its underlying data shape
const taskRow = {
  Task: "Write project proposal",
  Status: "In Progress",
  Priority: "High",
  DueDate: "2026-08-28",
  Project: "Website Relaunch"
};

console.log(taskRow);

Not runnable here

This template/structure is illustrative and can't be run -- try it in your own Notion or Obsidian workspace.

You should see

This isn't run — it's a data shape reference. If this row lived in a real Notion Tasks database and you switched to a Board view grouped by Status, you'd see a column for each status value (Not Started, In Progress, Done) with this task's card sitting in the 'In Progress' column, showing its Priority and Due Date on the card face without opening it.

5-minute try-it

Create a Tasks database with the five properties from this lesson (Task, Status, Priority, Due Date, Project) using any three real tasks from your week. Then view it as a Board grouped by Status and describe in one sentence how that view helps you compared to a plain list.

One important caution

Overbuilding an elaborate system on day one instead of starting with two simple databases

Treating Notion as automatically the best tool for everyone, ignoring its offline and lock-in weaknesses

Intro to Databases - Notion Help Center — Productivity Systems