People spend months building the "perfect" PKM systems across platforms like Logseq and Obsidian. I once had nested namespaces, custom queries pulling tasks from five different hierarchies, and a graph so dense it looked like a neural network. Then I realized I'd stopped actually using it. I was maintaining a system instead of doing work.

So I nuked everything and started over with four components: daily pages, simple tags, one project page, and one archive page. This minimalist setup beats complex PKM systems for most people because it removes the friction between thinking and capturing, which is the whole point of these tools, anyway.

Daily pages are your only inbox

Everything starts here

Stop creating pages for every fleeting thought. Your daily page in Logseq is the only entry point you need. When you open the app, you're already there. No decisions, no "where should this go?" paralysis.

Write everything as bullets on today's page: meeting notes, random ideas, tasks, and links you want to read later. Don't worry about organization yet. The daily page is a chronological record of your thinking, and that temporal context is more valuable than you realize. When you're looking for "that thing I thought about last Tuesday," you know exactly where to find it.

The beauty of Logseq's outliner structure is that you can nest details under any bullet without creating a new page. Meeting notes? The main bullet is the meeting name; indent everything discussed beneath it. One bullet expands into ten sub-bullets without leaving your daily page.

Tags do one job: create context

No elaborate taxonomy needed

Here's where people overcomplicate things. They create tag hierarchies like #project/work/client/deliverable or build elaborate systems distinguishing #todo from #task from #action-item.

Use maybe five tags total. Mine are #project, #idea, #reference, #todo, and #waiting. That's it. The tag isn't filing your thought into a category — it's creating a lightweight thread you can pull later.

When you click a tag in Logseq, you see every bullet across all your daily pages that shares it. You don't need subcategories. If you tag something #project and include the project name in the bullet text, you can search for it. Logseq's search is fast enough that #project redesign finds what you need without needing #project/website/redesign.

The moment you build an elaborate tag taxonomy, you've created maintenance overhead. You'll spend time deciding which tag to use instead of capturing the thought.

One page per active project

Templates and hierarchies are overkill

When something graduates from "random thought" to "thing I'm actually doing," it gets one dedicated page in Logseq. Not a folder, not a namespace, just a page titled with the project name.

Create the page by typing [[Project Name]] on your daily page, clicking it, and you're there. That page becomes the anchor point. At the top, write a one-sentence description of what the project is. Below that, add bullets for key information: goals, deadlines, relevant people, whatever matters.

Here's the critical part: you don't maintain this page by copying information to it. You link from it. When you work on this project, you're still capturing thoughts on your daily pages, but you'll reference [[Project Name]] in those bullets. Logseq automatically shows all those references at the bottom of the project page in the Linked References section.

This means the project page stays clean and minimal at the top (your anchor information), while the bottom automatically aggregates every thought you've had about it across all your daily pages. You never manually organize. The organization happens through links.

Archive is just one page

Completed work deserves a resting place

When a project is done, I don't delete its page or create an elaborate archive taxonomy. I have one page called [[Archive]], and I link to finished projects from there with a bullet and completion date.

The project pages themselves stay intact. All their linked references are still there if I need to reference how I approached something. But moving it to the Archive page signals "this is complete" and gets it out of my active mental space. When I search for active projects or scan my graph, I'm not cluttered with finished work.

This works because Logseq doesn't delete information when you stop linking to something actively. That project page still exists, the links still work, and the references are still connected. The Archive page is just a visual signal to your future self about what's in the rearview mirror.

Why this beats complex systems

The simplest explanation: you'll actually use it

Every additional layer of structure (custom queries, elaborate namespaces, or automated workflows) adds friction. And friction kills consistency faster than anything else.

Logseq's power isn't in building elaborate systems. It's a fact that links and references to create structure automatically as you write. Be it for journaling or project management, this minimalist setup leverages that core strength while keeping the barrier to entry at "just write bullets on today's page." That's sustainable. That's the system that'll still be working six months from now.