小心效率陷阱：為什麼你不需要"第二大腦"或者"個人知識庫"？

Summary

本文探讨了'构建第二大脑'概念的常见误解，并阐述了其真正核心价值。作者认为，真正的生产力提升不在于存储大量信息，而在于以'输出决定输入'的理念，有目的地收集和组织信息，以实现具体目标。通过简化的笔记方法PC(O)，即项目导向的笔记整理，提倡集中精力于产出而非工具本身，同时提醒观众在选择工具和方法时要结合个人需求，避免盲目模仿。

Takeaways

• 🧠 第二大脑（Second Brain）是一种数字笔记系统，其核心在于提升行动力（Actionability），而非简单的信息存储。
• 📚 作者Tiago Forte的《Building a Second Brain》一书被一些人误解为强调高效率的工具和方法，而实际上更注重笔记的实用性和产出。
• 🔍 第二大脑的误解之一是认为它是一个“存储现在，将来使用”的系统，而正确的理解应该是“产出决定输入”。
• 📝 笔记的价值在于它们能够服务于特定的产出或行动，如解决方案、文章、书籍、视频等，这些都是项目的表现形式。
• 🤔 笔记系统的真正核心是围绕“行动力”组织信息，而不是简单地收集信息。
• 📈 产出的第一步是设定一个产出目标，然后有目的地输入，最终实现产出，这与生产力（Productivity）的定义紧密相关。
• 🏆 费曼的“十二个最喜欢的问题”方法强调，信息的筛选标准是这些重要问题，即“产出决定输入”。
• 📂 PARA结构（Project, Area, Resource, Archive）是围绕行动力来组织信息的一种方式，但它并非一个文件系统，而是一个生产系统。
• 🔑 作者提倡的“最高效的输入方式”是为每条信息找到一个“家”，即具体的“项目”。
• 🔄 笔记的消化和吸收是产出的必要过程，作者建议“我们的笔记是为了使用，而不是为了收集”。
• 🛠️ 极简主义笔记法则提倡两个类型的笔记系统：一个用于记录各种杂事的普通笔记本，另一个是专门帮助产出的“项目盒子笔记”。
• 👨‍🏫 对于生产力工具和方法，我们应该从中获得灵感，而不是简单模仿，因为每个人的需求和产出类型都是独特的。

Q & A

什么是'第二大脑'（Second Brain）的概念？

第二大脑是一个数字笔记系统，旨在帮助个人提高生产力。它基于Tiago Forte的同名书籍，但许多人对这个概念有误解，认为它是一个存储系统，用于记录一切以备将来使用。

为什么作者认为许多人误解了'第二大脑'的概念？

因为许多人将'第二大脑'看作一个存储系统，认为只要有足够的输入质量和数量，就能自动产生想法和产出，这与作者在书中强调的'可操作性'（Actionability）和'产出决定输入'（output determines input）的理念相违背。

作者提到的'极简笔记规则'是什么？

作者提出的'极简笔记规则'包括两个部分：一是用于记录各种杂项事物的普通笔记本；二是专门用于帮助'产出'的'项目盒笔记'（PCO），其中P代表项目，C代表捕捉信息，O代表组织信息，但作者建议尽量避免组织这一步，以简化笔记流程。

为什么作者建议避免使用复杂的笔记工具？

作者认为，原则比工具更重要。每个人有自己独特的需求和产出类型，应该选择适合自己的软件和技术。过于复杂的工具可能会增加分类和整理的难度，降低笔记的实用性。

作者如何定义'行动性'（Actionability）？

作者认为'行动性'是指笔记应该服务于特定的产出或行动，这些行动可以是解决方案、文章、书籍、视频、课程、音乐、播客、软件、学习或旅行计划等，所有这些都可以用'项目'一词来概括。

作者提到的'CODE'笔记过程是什么？

CODE是一个缩写，代表捕捉（Capture）、组织（Organization）、提炼（Distill）和表达（Express）。这个过程强调了笔记的目的是为了使用，而不是仅仅为了收集。

为什么作者不喜欢PARA结构？

作者认为PARA结构过于复杂，它试图定义一个涵盖一切的概念，使所有事物相互联系，这可能导致人们在分类和整理笔记时感到困惑和压力。

作者如何解释'项目'（Project）的两种类型？

作者将'项目'分为两种类型：'冲刺'项目（Sprint project）和'慢烧'项目（Slow Burn project）。冲刺项目是当前集中精力需要完成的项目，而慢烧项目是已经建立但需要在未来完成的项目，它们处于'休眠孕育期'。

作者为什么认为YouTube上的生产力博主（包括他自己）的建议需要谨慎对待？

因为许多YouTube博主推荐的工具或方法最适合他们自己，他们的工具和方法可能主要针对视频内容产出，而这不一定适用于所有人。每个人都应该根据自己的需求来选择工具和方法。

作者如何看待'笔记'和'创造'之间的关系？

作者认为'笔记'和'创造'是两个不同的过程，前者相对容易，后者则更为困难。笔记是创造过程中的一个环节，但创造本身需要勇气、执行力以及长期的产出和积累。

Outlines

00:00

🧠 第二大脑的真正含义

视频首先提出了关于'第二大脑'概念的普遍误解，并指出人们常常将其与个人知识库混淆，导致生产力并未真正提升。作者强调，真正的第二大脑是数字笔记系统，其核心在于'可操作性'，即笔记应服务于特定的输出或行动。这一点与Tiago Forte的书籍《Building a Second Brain》中的定义相符，但许多人却误解了其含义，陷入了所谓的'生产力陷阱'。视频中还提到了Feynman的问题筛选法，强调了信息的'行动性'，即信息应与我们正在思考的问题或项目相关联。

05:02

📚 项目导向的笔记方法

第二段深入探讨了'第二大脑'的实践方法，特别是作者提出的CODE笔记过程和PARA结构。CODE代表捕获、组织、提炼和表达，而PARA则是项目、领域、资源和归档的缩写。作者通过一个著名编舞家的例子，说明了项目盒子如何帮助保持创造力。此外，视频还讨论了'冲刺'项目和'慢燃'项目的概念，强调了信息收集和组织应围绕明确的项目目标进行。作者批评了将'第二大脑'简单理解为'现在存储，将来使用'的观念，认为这是一种错误的自我安慰。

10:06

📝 极简主义笔记法则

最后一段提出了一个简化版的笔记方法，称为PC(O)，即以项目为中心的笔记系统。作者建议使用两种类型的笔记系统：一种是用于记录日常琐事的普通笔记本，另一种是专门用于项目输出的'项目盒子笔记'。作者强调了在捕获信息时的即时性和简化项目管理系统的重要性，以避免信息的堆积和遗忘。此外，作者提醒观众在选择工具和方法时应考虑个人需求，而不是盲目模仿他人。最后，作者指出，对笔记软件的迷恋反映了创造过程中的困难，真正的创造需要勇气、执行力和长期的积累。

Keywords

💡第二大脑

第二大脑是Tiago Forte在其著作《Building a Second Brain》中提出的一个概念，指的是一种数字化的笔记系统。在视频中，作者指出许多人对这个概念存在误解，认为它是一个存储系统，用来记录一切，以便将来使用。然而，真正的核心是“输出决定输入”，即笔记应该服务于特定的输出或行动，而不是仅仅作为信息的存储。

💡行动导向

行动导向是视频中强调的一个核心概念，意味着笔记和信息的收集应该围绕特定的输出或行动进行。这与“输入决定输出”的传统观念相反，强调的是首先设定输出目标，然后有目的地输入信息，最终实现输出。

💡CODE系统

CODE系统是Tiago Forte提出的笔记方法，分别代表捕获(Capture)、组织(Organization)、提炼(Distill)和表达(Express)。这个过程强调了笔记的最终目的是帮助输出，而不仅仅是信息的收集。

💡PARA结构

PARA结构是用于组织信息的一种方法，包括项目(Project)、领域(Area)、资源(Resource)和归档(Archive)。在视频中，作者提到PARA不是一个文件系统，而是一个生产系统，强调了输出的重要性。

💡行动性

行动性或可操作性是视频中反复强调的一个概念，指的是笔记应该服务于具体的输出或行动。例如，笔记可以是解决方案、文章、书籍、视频、课程等，这些都是行动性的具体体现。

💡存储现在，使用未来

存储现在，使用未来是一种常见的误解，认为第二大脑是一个存储系统，用于记录所有信息以备将来使用。视频中指出，这种理解忽略了信息收集应该有明确的目标和行动性，而不是无目的地存储。

💡项目

项目在视频中被用来指代一个具体的输出目标，可以是一个短期的冲刺项目(Sprint project)或长期的慢燃项目(Slow Burn project)。项目是信息收集和组织的核心，体现了“输出决定输入”的原则。

💡费曼的十二个问题

费曼的十二个问题是指诺贝尔奖得主理查德·费曼用来保持在多个领域卓越的方法。他总是将十二个最紧迫的问题记在心中，并将新信息与这些问题进行比较，看是否有助于解决它们。这种方法强调了信息过滤的行动性。

💡极简主义笔记规则

极简主义笔记规则是作者根据自己的经验提出的一套简化笔记方法。它包括两种类型的笔记系统：一种是用于记录各种杂事的普通笔记本，另一种是专门用于输出的“项目盒子笔记”，即PC(O)系统。

💡工具与原则

视频中提到，在选择笔记工具和方法时，应该更注重原则而不是工具本身。每个人有不同的需求和输出类型，应该选择适合自己的工具和技巧，而不是盲目模仿他人。

💡创作

创作是视频中讨论的另一个重要主题，它涉及到勇气、执行力以及长期的输出和积累。作者指出，对笔记工具的迷恋实际上是对创作困难的一种外在反映，而创作本身充满了不确定性，没有简单的公式可以遵循。

Highlights

构建第二大脑的理念可能被许多人误解，并不能真正提升生产力。

第二大脑并非一个所谓的个人知识库，其核心在于行动性。

《Building a Second Brain》这本书的作者Tiago Forte定义第二大脑为数字笔记系统。

许多人对第二大脑的理解存在误区，认为它是一个存储系统，帮助记录一切。

真正的第二大脑理念是“输出决定输入”，而非“输入决定输出”。

生产力的本质是产出，即先设定输出目标，然后有目的地输入。

作者强调行动性，即笔记应服务于具体的输出或行动。

第二大脑的CODE笔记过程：捕获、组织、提炼、表达。

Feynman的“十二个最喜欢的问题”方法，用以过滤信息。

信息的“行动性”是其帮助解决问题的能力，而问题则是信息过滤的标准。

作者提倡围绕行动性组织信息，使用PARA结构：项目、领域、资源、归档。

PARA结构不是文件系统，而是一个生产系统，强调输出。

项目分为“Sprint”项目和“慢烧”项目，分别对应不同的工作重点和时间安排。

存储现在，使用未来的误区在于缺乏明确的目标和项目定义。

消化和吸收笔记是输出的必要过程，作者提供了一些技巧。

表达和创造是第二大脑的起点和终点，作者提供了一些创意技巧。

许多人对第二大脑的理解偏差部分原因是书籍追求全面概念，内容复杂，失去焦点。

作者提出的PARA结构和CODE系统可能过于复杂，作者有自己简化的观点。

原则比工具更重要，选择适合自己的软件和技巧。

对生产力专家推荐的工具和方法应有所启发，而不是简单模仿。

创造需要勇气和执行力，以及长期的产出和积累才能找到自己的道路。

我们对笔记软件的迷恋反映了创造的困难，创造充满了不确定性。

Transcripts

If you care about personal productivity,

you must have heard of the concept of "Building a Second Brain".

But what I want to say is,

many people might have misunderstood the "Second Brain" concept.

The "Second Brain" built based on these misunderstandings

will not enhance your productivity.

You also don't need a so-called "personal knowledge base".

So in today's video,

I want to discuss the biggest misconception about the "Second Brain".

What the real essence of the "Second Brain" is,

the "minimalistic note-taking" rules I've derived from it,

and why you should be wary of YouTube productivity bloggers, including me.

The term "Second Brain" comes from Tiago Forte's book

"Building a Second Brain".

According to the author's definition,

building a second brain is a method,

simply put, the "Second Brain" is a digital note-taking system.

Yes, it's about note-taking.

Regarding this book,

I have a love-hate relationship.

I like it because some concepts in it genuinely helped me,

but I dislike its name and some content

because they led many people to misinterpret the book's meaning of the "Second Brain",

becoming obsessed with the so-called "high productivity",

spending lots of money and time on tools,

and falling into the "productivity trap".

Many videos about the "Second Brain" have titles like

"How I Remember Everything".

This gives the impression:

The "Second Brain" is a "storage" system that helps you "record everything",

and many people think,

the "Second Brain" offers a promise of "store now,

use in the future".

If you now build a so-called "personal knowledge base",

Storing all the useful articles, videos,

podcasts,

and book summaries you've read,

so that when you need them in the future,

you can find them and increase productivity.

The above two interpretations of the "Second Brain"

are based on a flawed underlying logic,

which is "input determines output".

As long as you have enough input quality and quantity,

you will generate ideas and be productive,

leading to "output".

While this logic sounds reasonable,

it's very counterintuitive and goes against the essence of "productivity".

It's not how the author defines the "Second Brain" in the book.

So, why is that?

Next, I will try to correct this misunderstanding

and help you understand the core value of this book.

Many people might think that the essence of this book

lies in the CODE system and the PARA note structure,

but personally, I believe,

its real value is in the author's emphasis on "Actionability",

or "Operability".

Simply put,

your notes serve specific outputs or actions,

this output can be a solution,

article, book, video, course, music,

podcast, software, learning,

or even a travel plan.

All these can be summed up with one word,

that is, "Project".

The real core of the "Second Brain" is "output determines input",

not what many people think, which is "input determines output".

This is actually related to the very definition of "productivity",

The English word for productivity or productivity is "Productivity",

the root word is "produce", meaning to produce.

Thus, to measure "productivity",

you must first have "productive activity".

This means first setting an output goal,

then inputting purposefully,

and finally achieving the output.

So, it's "output determines input".

The secret to improving productivity lies in focusing on "output",

rather than expecting results to emerge automatically from collected information.

This is reflected in all aspects of the author's "Second Brain".

Let's start with the author's "CODE" note-taking process.

It's an acronym:

C- Capture, gather information;

O- Organization, organize the information;

D- Distill, digest the information;

E- Express, use information to assist in output creation;

So, in the Capture phase,

what information should we gather?

The author recommends the Nobel Prize winner,

Feynman's "Twelve Favorite Problems" method.

When asked how he excelled in multiple fields,

Feynman explained,

"You must always keep the 12 most pressing problems in your mind,

most of the time these problems are in a "dormant state".

Whenever you get new information,

you compare it with these problems one by one,

to see if it can help you solve them.

Over time,

you will eventually encounter new information that helps you tackle a major challenge.

Feynman believes that the criterion for information filtering is these important "questions".

The ability to help solve a problem is the information's "actionability",

but you need to have questions first to filter,

this is "output determines input".

The author says,

We should focus on gathering information that resonates deeply with us.

The reason we "deeply resonate"

is because this information is related to the issues we are thinking about

or projects.

In other words,

The "most efficient way of inputting" is to find a home for each piece of information,

and that home is your specific "Project".

During the Organize phase,

the author emphasizes again that organizing information should revolve around "actionability".

To achieve this,

he introduced the PARA structure.

In this structure,

P (Project) represents specific tasks you want to accomplish,

A (Area) represents areas you need to focus on or be responsible for in the long term,

R (Resource) are the references available to you,

and the final A (Archive) is for archiving notes that are no longer needed.

However, to be honest,

I'm not particularly fond of this PARA structure,

and even including the CODE system,

I have some of my own views.

I will share them with you later,

but let's return to PARA.

The author states that PARA is not a "file system"

it's a "production system",

again emphasizing "output".

He also mentioned that this system was inspired by a famous choreographer,

whose method of maintaining creativity over a 60-year career was the "project box".

Whenever she starts a new project,

She would use a new box

To store all notes and information related to that project.

This gives her a clear focus

And allows her to work more methodically.

These "boxes" representing projects

Are what we just referred to as "destinations for the notes".

So again, "output determines input".

Some viewers might ask,

Isn't this just the concept of "store now

Use in the future"?

Why do you say it's a misconception?

To understand this,

We need to categorize "Project" into two types.

One is a "Sprint" project,

And the other is what the author calls a "slow burn" project.

Sprint projects are those you are currently focusing on,

Needing to complete intensively, like a "sprint".

Like this video you're watching now,

Which I produced in just a few days.

The Slow Burn projects are those you've established,

But need to complete in the future.

The reason they're called Slow Burn

Is because the project is in a "dormant gestation period",

Simmering like a slow stew,

You gradually gather information and inspiration,

And when the time is ripe,

You turn it into a Sprint project,

Focusing intensely to complete it.

With all your energy and resources.

The "dormant questions" that Feynman mentioned earlier,

and most of the choreographer's boxes are slow-burn projects.

Most of my videos also belong to slow-burn projects.

So in "store now, use in the future", the "store"

still needs a defined goal.

They are often slow burn projects.

If you can quickly find a place for a piece of information,

then that information is worth collecting and organizing.

If you can't,

it makes no difference whether it remains on the internet or in your notebook.

But what most people understand as "store now

and use in the future"

does not have well-defined projects.

They just hope that "what they store now

might be useful one day?"

This is more like a hoarder's optimistic promise to themselves.

Unfortunately, it's a promise that's hard to keep.

A "second brain" or "personal knowledge base" without a clear output definition

is a pseudo-need.

D- Digesting and absorbing the notes

This step is actually a necessary process for your output.

During the Distill phase, the author says,

"Our notes are meant to be used,

not collected",

and then provides some techniques to digest and absorb notes.

This is still "output determines input".

The final step, E- Express, express

create, output,

This is the starting and ending point of the second brain.

In this section,

the author provides some creative techniques

and methods on how to reuse completed projects in the future.

Now, looking at it as a whole,

"The Second Brain" emphasizes "actionability" everywhere,

the importance of output.

But why do many people's understanding of "The Second Brain"

become something that "helps you remember everything",

emphasizing the "input" of a "personal knowledge base"?

In my opinion,

part of the reason is

this book overly pursues a "comprehensive concept",

making the content complex and losing focus.

For instance, CODE discusses the process,

while PARA discusses the structure.

This is already quite complicated.

Then, within PARA, you have to differentiate between P,

A,

R,

and A.

This is harder than you might think.

For example, if I want to record a company purchase receipt,

it can be a Project,

as it's part of my tax filing process.

But according to the author,

it can also be a long-term "Area" I'm responsible for.

Could it also be a Resource?

Because I need this receipt when claiming a warranty from the vendor.

Also, in a project, I'll use some resources.

Do these resources go into the resource notes,

or directly into my Project notes?

In reality,

this PARA describes two types of notebooks.

One is for project management (P),

the main focus of the book;

the other is our usual notebook (A).

For jotting down miscellaneous things,

with no real actionability.

While such notes are certainly important,

they are simple.

There's no need to overcomplicate.

Yet the author wants P and A to share R.

The author is overly keen on defining a concept that covers everything,

making everything interconnected.

While emphasizing "actionability",

he also hopes "not to waste any notes".

This is a "wanting both" mentality.

It may sound cool,

but it only complicates things,

forcing you to make more choices,

diluting the book's core idea of "project-oriented".

Moreover,

I don't like the term "The Second Brain",

because it easily makes one think of a "memory tool",

rather than the "action" and "method" emphasized in the book.

In fact, what this book talks about

is essentially a "project management note method",

but this name is obviously not as "sexy" as "The Second Brain",

and not as appealing as "Helping You Remember Everything".

So next,

based on the core of this book and my years of creative experience,

I'll help simplify things for everyone,

sharing a "Minimalist Note-taking Rule" I've always used.

In my opinion,

everyone needs two types of note systems.

The first one is the notebook you already have,

used to jot down various miscellaneous things.

It doesn't need to be complex,

and you don't need to stress about making it perfect or efficient.

Because for most people,

your notes are just like the files on your computer hard drive.

Over time, they'll become cluttered,

and you'll always need to clean them up periodically.

This type of notebook isn't the most important to you,

it won't determine your success or failure.

Any free note-taking software can be used for these notes,

I personally use Apple's built-in Apple Notes.

The second note system,

is the "Project Box Notes" introduced by the choreographer I mentioned earlier.

Its sole purpose is to help you "output".

It's simple, it makes sense.

To be specific,

it's a simplification of the book author's "Second Brain" using CODE and PARA.

It's referred to as PC(O).

P, as before, stands for Project.

It could be a Sprint Project,

or what's called a Slow-Burn Project.

These are your boxes,

which in different note-taking apps might be represented as folders,

spaces,

or boards.

So, all the "information, ideas,

and resources"

are thrown into this box.

Any note-taking software can be used for project management.

You can use specialized software for your industry,

or mainstream apps like Apple Notes,

or Notion.

You can even mix and match software.

For instance, I use Apple Notes + Milanote.

Putting P (Project) at the forefront means,

before taking notes, there must be a "project" in place,

akin to Feynman's "12 most challenging problems."

C stands for Capture.

When you resonate deeply with a piece of information,

it's likely related to your project.

If possible,

capture it immediately and place it in the corresponding project.

If you come across exciting information that doesn't fit an existing project,

it may indicate the need to "initiate a new project",

to create a new box for it.

Whether you ultimately abandon this project or not,

falls under project management and creation,

and isn't something to contemplate when capturing notes.

Many note-taking apps come with information capture functionality.

For example, on Apple devices,

you can easily share information directly to the respective note-taking app.

You can also use dedicated note-capture tools.

For instance, in my case,

given my broad and diverse consumption,

I end up using many

capture tools.

For example, using custom Apple shortcuts,

self-made ChatGPT voice notes,

Readwise,

Millanote's built-in capture tools, and so on.

Then, O stands for "Organize."

If you can't temporarily place the note into the corresponding project,

or are still contemplating whether to "initiate a new project",

or "don't know how to define a new project",

you can temporarily save the note in an "inbox",

and organize it when you have the time.

So why did I put O in parentheses?

Because you should try to avoid this step.

In my experience, over time,

you might become lazy to categorize,

or forget why you initially found the information important,

rendering the note meaningless.

To avoid this,

simplify the structure of your capture tool and project management software,

reducing the steps.

If you have to go through multiple folders and interfaces to reach the target project,

it's too cumbersome,

and you won't want to capture it.

That's why projects I can complete in Apple Notes

won't be done in professional software.

Because Apple Notes is simple and fast.

That's my "Minimalist Note-Taking Rule."

Many viewers might say at this point,

Is it really that simple?

Shouldn't you share more software tricks in detail?

This brings me to my emphasis:

Principles are more important than tools.

Everyone has their unique needs and types of output.

You need to choose software and techniques that suit you.

That's why I want to remind everyone in the end,

to be cautious with recommendations from all YouTubers, including me.

In most cases,

the tools or methods we recommend best suit YouTubers.

You'll find that most computer reviews focus on video editing performance.

Most software use-cases are primarily for video content output.

Because making videos is the main output method for many of us YouTubers.

The more successful the YouTuber, the more this is the case.

Each video is our "box",

and we try to fit all useful information into these boxes.

But not everyone wants to be a YouTuber.

And not everyone is actively producing content.

Our "boxes" are likely different.

So,

the most important thing is to define your own "box",

become a "creator", and produce value.

When learning about tools and methods recommended by productivity experts,

you should take inspiration,

not merely imitate.

In closing, I want to say,

our obsession with note-taking software

is an external reflection of the difficulties in "creating."

Creation requires not only courage and execution,

and even if you have them,

creation remains full of uncertainties.

There's no simple formula to follow.

Only through long-term output and accumulation

can you possibly find your own way.

This is why I always say,

"Taking notes" and "creating" are two processes,

the former is easy, the latter is hard.

The reason we desire the devices and software used by "successful individuals"

is because these are the most certain aspects

and the easiest commonalities to attain between us and who we aspire to become.