Notion Office Hours: Tiago Forte ✍️

A weekly blogging workflow becomes reliable when it’s treated as a pipeline of “mature” processes—ideas move through clear stages, while the messy work of writing stays in tools built for drafting. Tiago Forte lays out how he uses Notion less as a place to write finished posts and more as a planning, status, and checklist system that keeps weekly publishing on track.

Forte starts with a bottom-up approach to building a system. Instead of designing a perfect architecture up front, he runs small experiments in Notion—testing what works for his day-to-day—then keeps only what supports real workflows. That mindset also explains why he doesn’t over-customize: he relies heavily on built-in templates and avoids advanced features until they’re clearly useful.

His core Notion setup centers on a Kanban-style board that tracks blog production from the first idea to publication and distribution. Cards flow through stages such as notes/outline, drafts, blog posts, email sends, social media, and an archive. The practical payoff is visibility: seeing 40–50 active items at once reveals patterns, relationships between ideas, and opportunities to combine related topics so multiple announcements can ship together. The system also supports links out to other tools—especially Evernote pages and Google Docs—so Notion becomes the control layer rather than the content authoring layer.

Forte’s workflow is intentionally “just enough structure.” He argues that building too much structure early creates a maintenance burden and can turn a system into a “monster” that doesn’t match daily life. Instead, structure should be added on demand when a real need appears. That principle extends to creative work: writing is chaotic by nature, so Notion is used for planning, status, and checklists, while Google Docs handles the actual drafting and collaboration.

Twitter plays a distinct role as a live testing ground. Forte treats it as a pre-idea stream of unfiltered thoughts; the posts that earn strong engagement become candidates for the “ideas” stage in Notion. He doesn’t try to pre-collect everything—he only invests time when there’s early signal. When a tweet thread resonates, he can clip it into Notion and later reference it while building a blog post, using social proof to guide what gets developed.

Beyond publishing, Forte uses Notion for process documents: checklists for course launches, recording workflows, and even operational routines like onboarding-style guidance for teams. He also emphasizes that maintenance work is handled predictably—through a weekly review checklist—so creative time can be protected. His schedule splits time into obligation-heavy days (meetings and admin) and creative days (Tuesdays/Thursdays), where he focuses on turning outlines into finished work.

The broader message is systems thinking for knowledge work: structure reduces mental clutter and quiets the inner critic, enabling deeper focus. Forte’s Notion approach isn’t about getting everything perfect; it’s about building a pipeline that can be iterated, trusted, and used consistently—so weekly publishing (and other repeatable processes) becomes a matter of flow, not willpower.