How to Choose a Digital Notes App as Your Second Brain
Based on Tiago Forte's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Treat the “second brain” as a multi-layer stack of tools, not a single app choice that must last forever.
Briefing
Choosing a digital notes app for a “second brain” isn’t about locking into a single platform forever—it’s about building a flexible stack with a reliable long-term home for ideas. The core message is that the stakes feel too high because most people treat notes as one app choice, when the real system is a constellation of tools that evolve as needs, workflows, and software capabilities change.
Tiago Forte frames the “second brain” as a layered stack rather than one product: like a computer made of hardware, firmware, operating systems, and apps, knowledge work is distributed across capture tools, storage, organization, collaboration, and creation. In that stack, he argues there’s a missing link for many people: digital notes apps. Earlier generations of software—word processors for publishing, social media for engagement, cloud storage for syncing, and collaboration tools like Google Docs—support structured output and teamwork. Notes apps, by contrast, are the first generation built specifically for creative output, which tends to be informal, messy, and open-ended. That makes notes the “repository” layer where scattered inputs can become durable knowledge.
Forte reduces the case for digital notes to seven requirements: they should be personal (chosen by the individual), informal (like a sketch on a napkin), open-ended (capturing before you know what something is for), multimedia-friendly (text, images, links, PDFs, drawings, voice, and more), transparent (what’s inside is visible immediately), durable (format longevity and upgrades), and centralized (synced across devices without constant exporting). These traits are meant to support the everyday behaviors that already happen—capturing highlights, quotes, photos, and meeting notes—rather than asking people to adopt a futuristic “upload your mind to the cloud” fantasy.
When it comes to choosing among mainstream options, Forte points to three dominant contenders—Evernote, Notion, and Rome—positioned as different “personality types” across the creative process. Evernote is likened to a library: structured, hierarchical, and strong at intake and capture. Rome is compared to a garden: bottom-up, connectivity-driven, and suited to developing ideas through emergent relationships. Notion is treated as architecture: it supports planning, hierarchy, and repeatable structure, making it strong for implementation and integration.
He ties these tool preferences to thinking styles using an assessment based on four creative problem-solving types: clarifier, ideator, developer, and implementer. In a live poll, the group skewed toward developer, clarifier, and implementer, and Forte uses the results to argue that people naturally gravitate toward tools that match how they think—though they can expand over time. The practical takeaway is to start with what feels workable, not what looks perfect, and to prioritize implementation habits over tool features.
Finally, he distinguishes personal vs. collective knowledge management. Forte uses Evernote for his personal organization (casual, informal notes) and Notion for team operations at Forte Labs (dashboards, SOPs, and structured, reusable documentation). The broader lesson: build a minimum viable workflow that moves information through the right stages—capture, organize, distill, express—then iterate. Implementation remains the bottleneck no app can solve for someone else.
Cornell Notes
The “second brain” is best understood as a stack of tools, not a single app. Digital notes apps are positioned as the missing link because they’re designed for creative output—informal, open-ended, multimedia, transparent, durable, and centralized across devices. Forte argues that Evernote, Rome, and Notion map to different stages of the creative process: Evernote for capture like a library, Rome for connectivity like a garden, and Notion for structure and implementation like architecture. People tend to gravitate toward tools that match their thinking preferences, so the most effective choice often comes from intuition and early usability rather than trying to perfect a setup. Over time, the stack can expand as needs and software capabilities evolve.
Why does Forte treat “second brain” as a stack instead of one app?
What makes digital notes apps the “missing link” in most people’s tool stacks?
What are the seven requirements Forte uses to justify digital notes apps?
How do Evernote, Rome, and Notion differ in Forte’s “library–garden–architecture” model?
How do thinking preferences influence which app someone should choose?
Why does Forte separate personal knowledge from team knowledge in different apps?
Review Questions
- Which of Forte’s seven digital notes requirements would be hardest for you to satisfy, and what would you change in your workflow to compensate?
- In the library–garden–architecture model, what stage of your creative process do you rely on most today (capture, connectivity, or implementation), and which app best supports that stage?
- How would you design a minimum viable workflow that moves information from capture to output without trying to perfect one app setup?
Key Points
- 1
Treat the “second brain” as a multi-layer stack of tools, not a single app choice that must last forever.
- 2
Use digital notes apps as the central repository layer because they’re built for creative output—informal, open-ended, and multimedia-rich.
- 3
Evaluate notes apps against seven traits: personal, informal, open-ended, multimedia, transparent, durable, and centralized (synced across devices).
- 4
Choose among Evernote, Rome, and Notion based on the stage of work you need most: capture (Evernote), connectivity (Rome), or implementation structure (Notion).
- 5
Expect your tool stack to evolve as your goals change and as platforms gain or lose capabilities; software obsolescence is part of the process.
- 6
Separate personal knowledge from collective/team knowledge: keep personal notes casual and team systems structured so SOPs and dashboards remain usable.
- 7
Prioritize implementation habits over perfect tool configuration; the hardest part is turning captured ideas into outputs.