Master Notion: From Confused to Confident with Marie Poulin's Coaching

A major source of Notion stress isn’t the app’s complexity—it’s the lack of a reliable structure for changing content without losing authority. In a coaching session with Marie Poulin, the focus lands on turning a constantly evolving “speaker notes” document into a system that stays trustworthy even as new cohorts, resources, recordings, and feedback keep arriving.

The workflow starts with a tension many teams recognize: one “canonical” document that must remain stable versus the reality that improvements keep demanding edits. The solution is to stop treating pages like static truth and instead build a database-backed template where changes are fast, reversible, and automatically organized. Rather than relying on folders where data lives in one place, the approach leans into Notion’s ability to access the same information in multiple contexts—so the same speaker notes can be filtered, embedded, and reused without duplicating chaos.

Poulin demonstrates this by creating a database on the “parent page” for “live session speaker notes,” then dragging existing pages into that database. Key properties are added to make the records usable over time: automated timestamps like created time and last edited time, a version/cohort tag (e.g., “V 15”), status phases (planning, preparation, delivery, finished), and practical links such as a URL for the keynote file or related assets. Person properties help assign ownership so team members can work without seeing everything.

From there, the dashboard becomes the control center. Resources and past-session material are organized into headings and pulled into a table of contents so staff can find what matters quickly. Filtering by cohort/version (for example, showing only items tagged with “v15”) keeps views clean and prevents accidental clutter. The system also anticipates operational needs: where recordings live (e.g., Panopto), where feedback is stored, and how responsibilities shift over time through “responsible person” assignments and filtered views.

A second database for “in-class resources” adds another layer of reuse. Resources can be stored once (as URLs, file properties, or attachments like worksheets), then linked to sessions through relations. Two-way relations let a resource page show every session where it was referenced, enabling consistent reuse of high-value materials without hunting through scattered Google Drive folders or video links.

Finally, the session turns these building blocks into templates. Instead of starting from scratch each time, the content for each course section (e.g., “Express” and “distill”) is copied into templates and converted into text blocks inside the template so new sessions inherit a proven starting point. The result is a repeatable “starting script” that reduces fluster and preserves consistency—while still allowing edits where they matter.

The coaching takeaway is as much behavioral as technical: build systems that match existing habits, then standardize them. The goal isn’t to impose rigid rules that make people feel worse—it’s to make the next session easier to run, easier to update, and easier for a team to maintain with confidence.