Learn Notion with AI
Notion can be a second brain or a second headache. The difference is understanding databases, relations, and views — which is exactly what most people get stuck on.
Why Notion Has a Steep Learning Curve
Notion looks like a note-taking app but behaves like a database application wearing a note-taking costume. The fundamental confusion starts with the difference between a page and a database entry. Pages live freely in your workspace. Database entries live inside databases and have properties. When people try to use Notion like a note app, they create pages. When they realize they need structure, they convert to databases. Then they discover that a database page and a regular page behave differently and the frustration begins.
Relations link entries between databases — connect a task to a project, a project to a client. Rollups pull data from related entries — show the total hours logged across all tasks in a project. These two features are what make Notion powerful for project management, but the setup is unintuitive. You have to create the relation property first, then configure the rollup to reference a specific property through that relation. Most people give up before they get it working.
Formulas broke for many people when Notion switched from the old syntax to the new formula 2.0 syntax. Properties that were referenced by name in quotes now use a different syntax. If you rename a property, old formulas may break silently. And the formula editor gives minimal error feedback — you get a red underline and no explanation.
How Talk To Your Computer Changes This
Share your Notion workspace and ask: "how do I create a relation between these two databases?" Talk To Your Computer sees your actual database properties and can walk you through adding the relation and configuring the rollup step by step. No generic tutorial — specific guidance for your specific databases.
Formula debugging is especially effective. Say "my formula stopped working after I renamed a property" and the AI can see your formula, spot the broken reference, and tell you exactly what to change. It is faster than re-reading the formula documentation and trying to figure out what "Syntax error at position 34" means.
What You Can Ask
Databases vs Pages — The Mental Model That Makes Notion Click
Everything in Notion is a block. A page is a block. A database is a block that contains pages with structured properties. Once this clicks, Notion makes sense. A database is not a spreadsheet — it is a collection of pages that share a schema. Each "row" is actually a full page with a title, properties, and its own content area.
Inline databases live inside a page. Full-page databases are their own top-level page. Linked database views are filtered windows into an existing database — they do not duplicate data, they just show a different view of it. Understanding which one you need for your use case avoids the most common Notion mess: duplicate data scattered across pages that slowly fall out of sync.
Relations and Rollups Without the Frustration
A relation is a property type that links entries between two databases. Create a "Project" relation on your Tasks database and you can assign each task to a project. The project page then shows all related tasks automatically. This is the foundation of every useful Notion workspace.
A rollup goes one step further — it reaches through a relation and pulls data from the related entries. If each task has an "Hours" property, a rollup on the Project database can sum all hours across related tasks. The setup is: create the relation first, then add a rollup that references the relation and specifies which property to aggregate and how (sum, average, count, etc.). Ask Talk To Your Computer to guide you through this while looking at your actual databases.
Building Views That Actually Save You Time
A Notion database can be viewed as a table, board, calendar, timeline, gallery, or list. Each view can have its own filters, sorts, and visible properties. Most people create one view and try to make it work for everything. The power move is creating multiple views of the same database — a board view filtered to your tasks, a calendar view for deadlines, a table view for everything.
Filters are where most people make mistakes. A filter that says "Created by is me" works differently than "Assigned to contains me." If your view is not showing what you expect, share your screen and ask. The AI can see your filter configuration and spot whether the logic is wrong or the property reference is off.
Try it free — no install needed
Share your screen. Hold the mic button. Ask anything.
Get Started Free