Stop reorganizing your apps. Build a system instead.

Stop reorganizing your apps. Build a system instead.

Recognize this scenario?

You know you saved it. You can even picture it, a link, a PDF, a note you made after a call with the exact number you now need. And you’ve just burned ten minutes hunting through Notes, Drive, your email, Slack, and two apps you forgot you were paying for. So you give up and google it again, and land on a worse version of something you already had. You just can’t find it, and no new app fixes that, because the app was never where the mess was.

The app graveyard

I love a new app. Especially the ones that promise me I’ll finally be productive and effective and for the love of God finally have some calm. To-do apps, note apps, micro-note apps, bookmarks, three cloud drives. I collect them like other people collect gym memberships in January, and with the same results.

The trap is always the same and I’m stupid enough to keep falling for it. Every app promises to be the one place everything lives. But you do different kinds of work in different phases, and no single app handles all of it well. So you spread your stuff across ten of them, and six months later you have no idea what you were using each one for. The mess just moved into nicer software.

What actually fixes it is a system that sits on top of all your apps, the same shape everywhere, so it stops mattering which one you open.

That system is PARA.

PARA, in plain terms

Tiago Forte built PARA as the backbone of his “second brain” idea. Four buckets, and the whole thing works because there are only four:

  • Projects — things with a deadline and an end. Launch the website. Write the talk. Paint the shed. A project finishes, so its folder changes constantly.
  • Areas — things you’re responsible for with no end date. Your health. Your finances. Your team. You don’t “finish” your health. You just keep the standard up.
  • Resources — stuff you’re keeping because it’s useful across projects: articles, book notes, PDFs, references. Not tied to one deadline.
  • Archive — anything from the first three that’s gone quiet. Project done, area no longer relevant, interest faded. Out of sight, still there if you need it.

The one distinction people get wrong is Projects versus Areas, and it’s worth getting right because everything else hangs off it. A deadline makes it a project. “Run a marathon in October” is a project. “Stay fit enough to grow old” is an area. It’s the same topic in two different buckets, and if you file them together the whole system turns to mush.

The point is you use it everywhere

PARA works because you run the same four buckets in every place you keep information. Your note app, your cloud drive, your email, all the same structure. So your brain only ever learns one filing system, and finding something stops being a treasure hunt.

You don’t have to do it all at once. Start in one app. I ran PARA in my notes first, saw it hold up, then rebuilt it in Dropbox, then moved to Obsidian and now have a powerful Exo-Brain.

How to actually start

I’ve gone a long way since I got in touch with the personal knowledge management sphere in 2019. But if I were to start all over again, this is what I would do.

1. Brain dump. Everything you’re carrying: things to do, things to learn, responsibilities, half-ideas. Get it out of your head and onto a page. You can’t organize what you can’t see.

2. Name the projects. Go through the dump and pull out anything with a deadline and an end. “Lose 5 kilos by summer” is a project. “Eat like an adult” is an area. Be honest about which is which.

3. Build the Projects folder first. One folder, a subfolder per project, and drop in the files you already have for each. Mirror the exact same list in your to-do app (Things, Asana, whatever you use) with the subtasks and deadlines.

4. Go do the work, then test it. The whole promise of PARA is that you find what you need for a project faster and without friction. So use it on a real project and see if that’s true. If it is, roll it into the next app. If it isn’t, your buckets are probably mislabeled, go back to step two.

PRO-TIP! If you can ensure your information won’t be locked in by a vendor (for example, if you are going to use Microsoft tools for this), it will be very hard to pivot to Google. Last year, I switched to Obsidian and now have all my information in the markdown format. Markdown is readable by every computer no matter the operating system you use and is very easy to read and write for any AI

Why this matters more now than it used to

A tidy second brain used to just save you time. But if your boss pays you eight hours a day, you don’t give a crap about that. But since the adoption of AI in almost every company, it is more essential than ever. AI is only as good as the context you hand it, and most people hand it nothing, so they get the same generic answer everyone else gets. The person who’s kept their own notes and client context in a system they can actually pull from feeds the machine something nobody else has. Your organised knowledge becomes the thing that makes your AI output yours instead of everybody’s.

Start with one app. Brain dump first, structure second. And the next time you know you saved something, you’ll find it.

← All articles

Want this applied to your situation?

Reading about it is a start. Tell me what’s going on at your end, and I’ll tell you straight if I can help, and how.