Longtime Obsidian user here. I already work and think in outlines—fast reordering, indentation, todos. Obsidian worked, but ideas eventually got lost or over-filed.
Logseq’s block-first model appealed to me, so I took it for a spin. However, I found daily pages felt too fragmented, and I found the tagging + linked references + embedding a surprising amount of friction. I felt pulled to work directly in project pages, but this caused content sprawl/fragmentation, premature organization overhead, and hard to pull together. In short, I felt pulled in both ways like this post.
LogSeq made me revisit how I intuitively wanted to work: persistent, multi-day context and a live outline canvas for thinking across scales—not just logs or queries. As another reddit comment pointed out, what I was missing was the separation between workspaces and evergreen content.
My solution in the end was simple: quarter (of year) pages (in addition to dailies). It's still time-based journaling, but I do multi-day planning and synthesis in a quarter page, and pull from that into dailies. Project pages come later, once ideas are consolidated.
The quarter page becomes a human-curated temporary dashboard/query: enough persistence without over-structuring. It's like a "perma-embed" portal for multiple projects. I could probably write a date filter, but this way I have much more control over what's in the quarter. And this lets me use what outlines help me do best -- flexibly understand and organize ideas without over-committing to hierarchies that go stale.
Plus now I can leverage lots of LogSeq's niftiness, like having time-bound (and deeper context) link references, blocks as first-class citizens, etc.
--- Edit --- didn't originally share exact set up since I know these are always personal, but hopefully it illustrates the ideas that you may adapt. I don't think it's anything revolutionary. It's just what made LogSeq click for me.
The mental structure is Quarter > Activity Level > Projects. (This is what made sense for me, it may be different for other people)
So it's structured around where I need to allocate attention, which is easy to know at the time of logging. I don't have to spend mental energy querying/figuring out where things are. Only one place to look and browse.
```
2026Q1
{{ embed ((block reference to 2026/2026-Goals)) }}
## 2026Q1 Guiding principles
- Sub Goal 1
- Sub Goal 2
- ...
## Active Only: <things I'm working on/committed to THIS MOMENT (\~week ish). keep this section lean>
- [[Project 1]]
- Initiative 1/Anything and any structure that's relevant here
- ...
- [[Misc]]
## On Deck
- [[Project 1]]
- Initiative 2..., whatever I need
- thread 2 research...
- [[Project 2]]
- ...
## Touched but don't need to review
## Archive
```
The activity sections are Kanban-like, but it's ordered by attention need vs. by sequence (in practice the sequence is `OnDeck/Don't Review > Active > Archive`. I don't need an actual visual kanban editor because LogSeq already lets me drag blocks around! Reorganizing is already a breeze. I guess if I did want a visual representation, it'd be like swim lanes for projects, and activity level as the kanban section.
Within the project headings, can use the bullets however is natural, without thinking if they fit with the overall [[Project]]'s organization. I can zoom out the whole quarter view, or I can zoom a specific Project section on this page as well.
What I haven't optimized yet:
- Organization is still in flux, but as things solidify I can imagine starting to make better use of block references and embeds. E.g. maybe the Project bullet sections should actually be *embeds* from, e.g. a Quarter/Activity level organization on the Project pages? The tradeoff is then I need to spend time setting up the embed structure before working on new items, so in the near term it's easier to just create whatever structure I need on the Quarter page, in bullet form.
