Implementation Guides
Step-by-step walkthroughs for setting up productivity systems, configuring specific tools, and implementing automation workflows. Includes: system setup guides (e.g., building a GTD system in Obsidian, setting up a Second Brain in Notion), workflow automation recipes (e.g., auto-saving Zoom meeting notes to Notion via Zapier), and feature-specific how-tos (e.g., converting handwritten notes to text in GoodNotes). Each guide includes a difficulty level, estimated time, required tools, and step-by-step instructions with screenshots or code snippets where needed. Excludes high-level framework explanations without implementation steps (→ frameworks-and-methods) and tool overview content (→ tool-profiles). Serves users in implementation mode who have already chosen a tool or system and need execution help.
The implementation section — for people who have already chosen a tool and need step-by-step execution help. Check the difficulty badge before you start.
Automation Recipe
Learn how to automatically capture, transcribe, and distribute meeting notes using Zapier, an AI note-taker, and your favorite apps — all without coding. Perfect for knowledge workers attending 3+ meetings daily.
System Setup
A step-by-step guide to implementing David Allen's Getting Things Done methodology inside Notion using a single master task database, relational projects database, filtered linked views for each GTD list, context tags, and a repeatable weekly review workflow — written for knowledge workers, students, and freelancers who want to build the system from scratch and understand the architectural decisions behind it.
System Setup
A practical, opinionated setup guide for knowledge workers and students who want a working Second Brain in Obsidian — covering vault setup, organizational method selection, essential plugins, daily capture habits, and the common mistakes that cause most beginners to quit.
System Setup
Most PARA-in-Notion setups fail because they treat Notion like a folder system — this guide shows knowledge workers and students how to implement PARA correctly as a relational database system, using linked views, relation properties, and Archive-as-Status to preserve metadata and eliminate the 'where does this go?' friction.
