Ask ten people how they organize their digital lives and you'll get ten different answers. One swears by Notion. Another lives in Evernote. Someone else insists everything belongs in Obsidian. And every productivity video seems to end the same way — with another app to install and another subscription to buy.
I wanted to see how far I could get without doing any of that.
I wasn't chasing the next great productivity app. I wanted a system I could trust, built on software I already owned: Apple Mail, Apple Calendar, Apple Notes, Things 3, and Obsidian. The only thing I added wasn't another application — it was Tiago Forte's PARA methodology.
Learning PARA wasn't the hard part. The hard part was mapping it across five different applications without creating five different versions of the same information.
That turned out to be a lot harder than I expected.
The wrong question
The first thing I realized was that PARA doesn't tell you where information belongs. It tells you what information is. That's a completely different way of thinking.
When most people adopt PARA, the first question they ask is, "How should I organize my folders?" I think that's the wrong question. The real question is, "What role should each application play?" Once I stopped organizing folders and started assigning responsibilities, the architecture finally started to make sense.
Email as the front door, not the filing cabinet
Apple Mail became the front door — but getting there wasn't obvious. I'm juggling six email accounts: three Microsoft, two Google, and iCloud. My main line of communication runs through Google Workspace, which should have made Outlook for Mac the natural choice. It didn't work out that way.
Recent changes mean Outlook for Mac won't let you create a Google Meet unless the calendar invite is going out through a Microsoft account. I tried switching to classic mode to route around it. That didn't work either. I looked at other clients, but at this point I'm done paying for another subscription just to fix one workflow problem. Forwarding everything into a single account was on the table too, but I'd already run into enough sync and threading issues with forwarding to know it wasn't a real fix — just a different set of headaches.
Apple Mail was the best bad decision available. It's native, it's free, and it handles six accounts without asking me to trust a third party with all of them. It also does the one thing no other client offered: it plugs directly into Things 3's Quick Entry with Autofill, so I can turn an email into a task in seconds without leaving Mail or copying anything by hand. That integration alone tipped the decision. It's not elegant. It's just the least broken option — and the one that actually connects to the rest of the system.
Once I landed there, the deeper question stopped being which client and became what is email actually for. Everything enters through it — meeting invitations, receipts, travel confirmations, newsletters, client requests, purchase confirmations, articles, conversations. When I tried to organize all of that inside the inbox itself, email ended up doing double duty as both my communication platform and my task manager.
I made that mistake for years. Important emails stayed in my inbox because I was afraid I'd forget about them. Less important ones got buried underneath. Eventually the inbox stopped representing today's work and became a museum of unfinished intentions.
The fix wasn't Inbox Zero. It was separating communication from commitment. If an email requires me to do something, the email stays exactly where it is — the commitment moves. That commitment becomes a Things 3 task. The email doesn't remind me anymore; Things does.
That one change reshaped my entire relationship with email. I no longer keep messages because they're important. I keep them because they're communication. The job of remembering moved somewhere else entirely.
Folders answer "where," tags answer "what"
That same principle carried over into Apple Notes — though getting there meant leaving Evernote behind first. I'd been an Evernote user for years, but when they raised the price, that was my cue to look for something else. I tried Joplin along the way; it fell short for the same reason everything else did — another tool asking for trust or money without giving me more than what I already had. Apple Notes turned out to be quick, it syncs cleanly across every device I own, and it isn't burdened by a subscription. It's not as flashy as Evernote. It doesn't need to be. I share notes with clients and with family, scan business cards straight into Smart Folders, scan documents that come out genuinely usable, and rely on voice recording with transcription more than I expected to. When I need an email saved for the record, I just print it straight into Apple Notes instead of archiving it in the inbox.
For years before that, though, I treated Notes like a filing cabinet — every note needed the right folder, every notebook needed a purpose. Then Smart Folders entered the picture and completely confused me.
At first I thought Smart Folders were just another place to organize notes. They're not. They're views. That sounds like a small distinction, but it changes everything once you're actually running PARA.
A podcast I want to listen to later doesn't belong inside a "Listen Later" folder — it belongs in Resources. The Smart Folder simply surfaces everything tagged #listen. Nothing moves. Nothing gets duplicated. The Smart Folder isn't another filing cabinet; it's another way of seeing the same information.
That realization changed how I use tags throughout the whole system. Folders answer one question: where does this belong? Tags answer another: what is it? Once I stopped expecting tags to replace folders, and folders to replace tags, both finally made sense.
Notes capture. Obsidian develops.
That brought me to the question I wrestled with longer than anything else: why keep Apple Notes if I already had Obsidian? Every article I read treated the two as competitors. After living with both, I don't think they compete at all.
Apple Notes wins the moment information arrives unexpectedly — a phone call, a hallway conversation, a receipt, a photo, a whiteboard, a scanned document, a quick thought before it disappears. None of those moments are about knowledge management. They're about capture.
Obsidian enters later. It's where research happens, where I do the deep thinking, and where actual writing gets built — not quick notes, but work that needs room to develop and connect to other ideas over time. Apple Notes captures; Obsidian develops. Once I accepted that distinction, I stopped trying to pick one over the other. I needed both, because they were solving different problems.
Things 3 doesn't store information — it stores commitments
Things 3 fits the same pattern. It doesn't store information; it stores commitments, and that distinction matters. A meeting note isn't a task. An article isn't a task. A receipt isn't a task. But replying to a client, submitting an expense report, scheduling a follow-up, reviewing a proposal, or prepping a presentation absolutely are — and those belong in Things 3. Not because Things is a better notebook, but because it isn't trying to be a notebook at all.
In practice, this is the part of the system I lean on most. When an email lands that needs action, I click into it and hit Ctrl+Option+Space. That single shortcut creates a Things 3 task with a direct link back to the original email — no retyping, no copying subject lines, no losing context. Once the task exists, I archive or move the email out of the inbox. It's no longer sitting there as a reminder; it's already actionable, sitting where actionable things belong.
That matters more than it sounds like, because I'm not managing one project — I'm managing several that don't overlap. Ministry work. My day job. A new platform I'm developing. Family. Teaching. Consulting. Each one generates its own stream of commitments, and none of them care about the others' deadlines. Things 3 is what keeps that from turning into chaos. Every area has its own space, every project lives inside the area it belongs to, and I can move through all of them without one bleeding into another — or forgetting which hat I'm wearing on a given task.
Where the architecture cracked
Email wasn't the only sore point. Apple Calendar was the other one — and ironically, scheduling itself wasn't the problem.
The problem is one Apple has never bothered to fix, even though Google, Microsoft, and Proton all solved it years ago. When you get a meeting invite in any of those systems, accepting or declining actually notifies the sender. Apple Calendar doesn't do that. Instead, it attaches an .ics file and leaves it there — the sender never finds out whether you accepted, declined, or ignored the invite entirely. It's not a new bug. It's been broken for years, and it's the kind of thing that should be trivial for a company Apple's size to fix.
Working across Apple, Google, Microsoft, universities, nonprofits, and clients exposed every weakness in calendar interoperability. I never questioned whether I'd accepted a meeting. I questioned whether every system agreed I had accepted it. That's a terrible question to have to keep asking.
Rather than rebuild the whole workflow, I isolated the problem. It wasn't PARA. It wasn't Apple Mail, Things, or Notes. It was calendar interoperability specifically. I went looking for something to fix it — tried Spark, tried Readdle's calendar app, looked at a few others. The pattern was the same every time: you'd start using one, get comfortable, and then hit the feature you actually needed sitting behind a paywall. I wasn't willing to add another subscription to solve a problem I was already working around for free. So the .ics issue is still there. I haven't fixed it — I've just built a system that doesn't fall apart because of it.
The real lesson
Looking back, that's probably the biggest thing this project taught me: software wasn't my problem. Architecture was.
Once every application had a clearly defined responsibility, the decisions became obvious. Email communicates. Things 3 manages commitments. Apple Notes captures. Obsidian preserves knowledge. The calendar manages time. PARA sits above all of it — not as another application, but as the framework that decides where information belongs before I ever choose which app should hold it.
None of this happened by finding the perfect app. It happened by assessing what I already had, being honest about what wasn't working, and refusing to pay my way out of a problem that architecture could solve instead. Between dropping Evernote and passing on every paid alternative I tested — for notes and for calendar — I'm not carrying a single new subscription from this whole project. Every tool in this system was one I already owned.
The surprising part of this whole journey wasn't discovering some revolutionary new productivity tool. It was realizing I already owned almost everything I needed. I just hadn't connected the pieces.
None of these tools are perfect. I just learned to work with what I had instead of waiting for something better.