Notion
Notion is a flexible workspace built from pages and blocks. You get docs, wikis, tables, kanban boards, and project trackers in one product. A free tier and minimal structure make it easy to start; this guide covers how to use it without ending up in a mess of nested pages.
Notion Training: The Basics
Why notion fits product work
Core concepts that matter
Pages and hierarchy
A page is a doc. Pages can live in other pages (nested). Sidebar shows the tree. Keep depth shallow (2–3 levels). Use a few top-level “hubs” (e.g. Product, Engineering, Company) and branch from there. Avoid one giant folder of orphan pages.
Blocks
Blocks are the units: paragraph, heading, list, table, image, code, embed, toggle, etc. Use toggles for “expand if needed” (e.g. appendix, details). Use callouts for warnings or tips. Consistent block use makes pages scannable.
Databases
A database is a collection of entries (rows) with properties (columns). View as table, kanban, calendar, or gallery. Linked databases show a filtered view of another database. Use one database per “kind of thing” (e.g. projects, features, meeting notes) and link or embed views where needed.
Templates
Templates are page or database layouts you save and reuse. Use them for recurring structure: spec template, retro template, 1:1 template. Create from the “+” or from a database property. Start from Notion’s gallery or build a few of your own.
10 Notion Tips to Speed Up Your Workflow
Sharing and permissions
Share by link or by invite. Permissions can be by workspace, by page, or by database. Use “share with workspace” for team defaults; restrict only when needed. Avoid sharing every single page one-by-one.
Practical habits
When notion isn’t the fit
Pricing (high level)
Free - Core blocks, collaboration, some integrations. Enough for small teams and personal use.
Plus and above - More members, advanced permissions, analytics, API, support. Check Notion’s pricing for current plans.
Getting to know databases in Notion
Notion is a strong default when you want one workspace for docs, wikis, and light project tracking. Keep the hierarchy shallow, use databases for repeated structure, and lean on templates so structure stays consistent.

