Tag: Thinking Systems

Most people organize their files and notes the same way they were taught to organize a school binder.

• Marketing stuff in the marketing folder.
• Health stuff in the health folder.
• Work stuff in the work folder.

It feels logical. It mirrors how a physical filing cabinet works.

The problem shows up the moment you need to actually use something.

You’re working on a product launch and the relevant information is scattered, some in a “marketing” folder, some in a “clients” folder, some in a “2024” folder.

You know it exists. Finding it takes longer than it should.

Tiago Forte’s PARA method fixes this by flipping the organizing question. Instead of asking what is this about, it asks how actionable is this right now.

That single shift is what the whole system is built on.

What PARA actually is

PARA is an organizational framework for your digital life. It stands for Projects, Areas, Resources, and Archives – four categories that, between them, can hold everything you’ll ever need to organize.

It works in any tool: Notion, Obsidian, Google Drive, Apple Notes, plain folders on your desktop.

The structure is the same regardless of where you implement it.

Here’s the short version:

• Projects – things you’re actively working on right now, with a clear finish line
• Areas – ongoing responsibilities you maintain over time, with no finish line
• Resources – topics you’re interested in and might reference later
• Archives – anything from the above three that’s no longer active

That’s the entire system. Four folders at the top level, and everything else lives inside them.

Breaking down each category

Projects

A project has two things: a goal and a deadline. When it’s done, it’s done.

Examples of actual projects:

• Launch the new pricing page by end of month
• Write and publish three blog posts this quarter
• Set up automated invoice reminders before Friday
• Renovate the spare bedroom

What makes something a project isn’t its size – it’s that you’re actively working on it right now and it has a finish line. Once it’s complete, it moves to Archives.

Areas

An area is an ongoing responsibility with no end date. You don’t complete it. You maintain it.

Examples of actual areas:

• Health (you’re never “done” with your health)
• Finances (ongoing, always)
• Team management (as long as you have a team)
• The Owl Logic (a blog you maintain indefinitely)

The distinction matters more than it sounds.

A lot of people set up PARA, feel good about it for two weeks, and then quietly stop using it.

The most common reason: they put areas inside projects. “Health” becomes a project. “Marketing” becomes a project.

But they have no finish line, so they never get archived, never feel done, and the whole system starts feeling cluttered and unresolved.

If something will still exist in your system a year from now, it’s an Area, not a Project.

Resources

Resources are things you find useful or interesting that don’t belong to a current project or area, but you want to keep for future reference.

Examples of actual resources:

• A collection of articles about copywriting frameworks
• Notes from a course on SQL you took six months ago
• A list of tools you evaluated but didn’t pick yet
• Bookmarks on automation patterns you want to try

Resources are organized by topic, not by actionability.

They’re the closest thing in PARA to a traditional folder structure, but they’re clearly separated from your active work, which keeps them from polluting your Projects and Areas views.

Archives

Archives is where things go when they stop being active – not when they stop being useful.

• A completed project gets archived.

• An area you’re no longer responsible for gets archived.

• A resource topic you’ve lost interest in gets archived.

The key is that archived doesn’t mean deleted. It means out of your active view until you need it again.

This is what makes PARA sustainable long-term.

Most organizational systems collapse because nothing ever leaves, everything just accumulates until the system becomes unnavigable.

In PARA, archiving is a first-class action, not an afterthought.

Organize by actionability is the core idea

The reason most folder systems fail isn’t laziness. It’s that organizing by topic creates the wrong mental model for knowledge work.

When you file something under “marketing,” you’ve described what it is. But you haven’t told yourself anything about what to do with it, or when.

PARA organizes by how active something is right now.

• Projects are the most active.
• Areas are always-on but lower urgency.
• Resources are background.
• Archives are dormant.

This maps directly to how your attention actually works – you need different things at different times, and the system makes that visible.

Forte describes it as organizing for action, not for storage. The folder structure is a reflection of your current priorities, not a filing cabinet for past decisions.

Where people get confused

Confusing Projects and Areas is by far the most common mistake. Here’s a quick test:

Ask yourself: can this be completed?

• “Fitness” – can’t be completed. That’s an Area.
• “Run a 5K in under 30 minutes by March” – has a finish line. That’s a Project.
• “The Owl Logic” – ongoing blog, no end date. That’s an Area.
• “Write and publish the PARA method article” – specific deliverable. That’s a Project.

If you can’t imagine what “done” looks like, it’s an Area. If done is obvious, it’s a Project.

Treating Resources as a junk drawer is the second common failure. Resources should be organized by topic with enough structure that you’d actually find things again. If you’re dumping everything loosely into Resources because you’re not sure where else it goes, the folder becomes useless fast.

Over-engineering the setup before you have anything to organize.

Forte’s own advice here is useful: don’t migrate everything at once. Start with what you’re working on right now, set up Projects and Areas for those things, and let the system fill in naturally over time.

The people who try to reorganize their entire digital life in a weekend almost always abandon it by week three.

A practical example: solo builder using PARA

Here’s what a realistic PARA setup might look like for someone building and running a small SaaS product alongside a blog:

Projects

• Ship v2.0 release before end of June
• Write 4 blog posts for Q2
• Set up email onboarding sequence

Areas

• Product (ongoing development and maintenance)
• Blog (content, SEO, growth)
• Finances (invoicing, subscriptions, taxes)
• Health

Resources

• SaaS pricing research
• Email marketing examples
• Automation tools I’m evaluating
• SEO frameworks and notes

Archives

• v1.0 launch materials
• Old client proposals
• The course notes from that SQL tutorial

Notice that “Blog” is an Area, not a Project. It’s ongoing. But “Write 4 blog posts for Q2” is a Project – specific, time-bound, completable. Both exist in the system, at different levels, which is exactly the point.

Is PARA worth setting up?

For most people, yes – with one caveat.

PARA is genuinely useful if you’re managing multiple responsibilities simultaneously and your current system (or lack of one) means things fall through the cracks or take too long to find.

The actionability-first structure works well for knowledge workers, solo builders, and anyone juggling more than two active projects at a time.

It’s less useful if your work is highly task-list-driven with little reference material, or if you’re already using a system that works for you.

PARA isn’t the only valid approach, and the best system is always the one you’ll actually maintain.

The friction of setting it up is low.

The real investment is the habit of deciding – every time something new comes in which of the four categories it belongs to.

That decision-making discipline is the actual skill PARA teaches. The folder structure is just the scaffolding.

If you’re building something independently and managing your own time, that discipline compounds fast.

It’s related to a broader problem most solo builders run into – why solo builders build forever and never launch.

Getting clear on what’s a Project versus what’s just an ongoing Area is part of what helps with that.

For how to think about organizing your working environment at the tool level, the Obsidian folder structure post covers how PARA maps specifically to a note-taking setup if that’s the direction you want to go.

Most people have a note-taking problem that looks like a storage problem.

They open Notion after three months and find 200 saved articles, 40 half-finished bullet lists, and a folder called “Ideas” with nothing actionable inside.

The notes are all there. They just don’t connect to anything.

They don’t generate new thinking. They sit.

The Zettelkasten method is a direct response to that.

It was built to solve exactly this, not to store information better, but to make stored information useful over time.

What Is the Zettelkasten Method?

The Zettelkasten method is a personal knowledge system where every note contains exactly one idea, written in your own words, and explicitly linked to related notes.

“Zettelkasten” is German for “slip box”

The method works because of two rules that most note-taking ignores: atomic notes (one idea per note, nothing more) and deliberate linking (every note connects to at least one other). Over time, these connections form a network of your own thinking – one that surfaces ideas you’d forgotten and generates new ones you hadn’t considered.

You don’t need index cards. The same principles work in Obsidian, Logseq, Notion, or a plain text folder.

The Three Types of Notes You Actually Need

There are three note types worth knowing before you get started.

• Fleeting notes (fast, throwaway captures)
• Literature notes (one source summarized in your own words)
• Permanent notes (one-fully formed idea, written clearly enough to make sense)

The ratio matters – you’ll have lots of fleeting notes, fewer literature notes, and even fewer permanent notes.

That bottleneck is intentional.

If you want the full breakdown of what each type looks like in practice, read How to Take Smart Notes (That You Actually Revisit)

How to Write Your First Permanent Note (With a Real Example)

This is the step every beginner’s guide describes but none actually shows.

Here’s what a real permanent note looks like.

Say you read a chapter on decision-making under uncertainty and one idea stuck: that most bad decisions come from confusing the quality of a decision with the outcome of a decision.

A decision made with bad information can get a lucky outcome.

A decision made with solid reasoning can still go wrong.

Here’s what a permanent note for that idea looks like:

Notice what’s in there: the idea in your own words, why it matters, and where it connects.

Notice what’s not there: bullet points copied from the book, vague summaries, or quotes you highlighted but didn’t think about.

Writing a permanent note like this takes 5–10 minutes.

That’s the friction. It’s also the point, the thinking happens during the writing.

How to Link Notes (and Why That’s the Whole Point)

The links in a Zettelkasten are not tags or categories.

They’re specific connections between two ideas, with a reason for the connection.

In Obsidian, you write [[Note title]] to create a link. In Logseq, it’s the same syntax.

In a paper system, Luhmann wrote the ID of the related card directly on the current one.

The tool doesn’t matter – the thinking behind the link does.

When you write a new permanent note, ask: what else in my system does this connect to? Not “what folder does this belong in?” but “what other specific idea does this relate to, and why?” If you can’t name another note, that’s fine – but look.

The habit of searching your existing notes before filing a new one is what keeps the system from becoming another graveyard.

Over time, notes with many incoming links naturally become your most developed thinking – the ideas you’ve returned to, built on, and connected widely.

Those clusters become starting points for writing, for projects, for decisions.

If you’re using Obsidian and want to see how folder structure interacts with this kind of linking, the post on Obsidian folder structure covers how to set that up without overcomplicating it.

What Tool Should You Use?

The honest answer: it mostly doesn’t matter, and picking the wrong one is less costly than not starting.

• Obsidian is the most popular choice for Zettelkasten right now. It stores everything as plain text files on your own computer, supports bidirectional linking natively, and has a graph view that shows your note connections visually. Free for personal use.

• Logseq is similar but built around a daily journal structure. Good if you prefer a more linear capture flow before processing into permanent notes.

• Notion works, but the linking is clunkier and the structure pushes you toward databases rather than connected ideas. Fine if you’re already there.

• Paper index cards still work exactly as Luhmann used them. Slower, but the physical act of writing forces you to think before you write.

Start with Obsidian if you have no preference. If you’re already in Obsidian and want to see how it handles visual note-mapping, the post on Obsidian + Excalidraw shows a useful extension for that.

The One Mistake That Kills Most Zettelkastens

Collecting instead of connecting.

Most people set up Obsidian, start clipping articles, saving highlights, and bookmarking pages, and call that their Zettelkasten.

It isn’t. That’s a well-organized reading list.

The Zettelkasten only becomes useful when you process what you capture: when you take a fleeting note and ask “what do I actually think about this?” and then write a permanent note that answers that question.

And then link it to something else you’ve already written.

If your system has 200 notes and you’ve never written a permanent note from scratch, you have a collection.

The method starts when you begin converting that collection into connected thinking – one note at a time.

The fix is simple: cap your capture. For every five articles you save, write one permanent note. That ratio forces processing.

It also makes you pickier about what you save in the first place.

How to Actually Start Today

You don’t need to understand the full system before writing your first note. Here’s the shortest path:

1. Open whatever app you have – Obsidian, Notion, even a text file.
2. Think of one idea you’ve read or thought about recently that actually stuck with you.
3. Write it out in your own words. One idea. Two to four sentences. No quotes.
4. Add one link or question: what does this connect to, or what does it make you want to think about next?
5. Save it. That’s your first permanent note.

Do that three times this week. Not thirty. Three. The system builds from real notes, not from a perfect setup.