Combining work and personal workflows in Logseq
Based on CombiningMinds's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Keep one Logseq graph and separate work vs. personal at the block level using hashtags or links.
Briefing
A single, tag-driven Logseq graph can handle both work and personal life without forcing a rigid “one graph for work, one for personal” split. The core idea is to capture everything in one stream-of-consciousness database, then rely on consistent tags and Logseq queries to surface the right slice of information when it’s time to act.
Instead of maintaining separate work and personal graphs, the workflow keeps one graph and separates content at the block level. Notes get organized using either double square brackets or hashtags so items can be retrieved later. A typical day starts with “morning pages” in a dedicated area—gratitude, what the person is thinking about, and dreams—followed by random thoughts and to-dos as the workday begins. The system’s structure comes from three main classifications for any block: (1) feedback, for professional conversations; (2) inbox, for brief discussion items; and (3) work vs. personal, applied via hashtags when something arises mid-day.
To-dos are handled through Logseq’s control-enter workflow. Typing “to do” and pressing Ctrl+Enter cycles the block through states like “to do,” “doing,” and “done,” letting tasks move forward without leaving the page. The guiding principle is that retrieval doesn’t require a top-down hierarchy. With good tagging, information can be found later even if it was added casually in the moment.
When it’s time to switch into work mode, the workflow uses a “home page map” as a landing page. From there, the person checks to-dos filtered by tags: work to-dos, personal to-dos, and general to-dos for anything missed or not tagged. Meetings are managed through page-level organization tied to tags and queries. For a specific person—like “John”—the system can show an inbox of meeting notes via a query such as “where it’s and John” combined with “inbox,” pulling up items like “Notes April 12th John inbox: what are we going to do about the project.”
After the meeting, the inbox items can be cleaned up by deleting the tag so they don’t linger. Feedback is tracked differently: there’s a dedicated “feedback for [person]” page that aggregates feedback blocks. During a conversation, the person can cut and move relevant blocks into that feedback page, optionally nesting them under dates (using a “backslash today” query) to create a time-stamped record. The result is a lightweight stack for capturing, processing, and later retrieving context—without losing the ability to find what matters quickly during the day.
Cornell Notes
The workflow keeps everything in one Logseq graph and separates work vs. personal content using hashtags and links, rather than maintaining separate graphs. Blocks are classified with tags like “feedback” and “inbox,” plus “work” or “personal,” so the right information can be surfaced later through queries. To-dos are created and progressed using Ctrl+Enter, cycling through states such as “to do,” “doing,” and “done.” A home page map provides quick filtered views for work, personal, and general tasks. Meetings are handled by querying inbox notes for a specific person, then moving completed items into a dedicated feedback page to build a track record over time.
Why keep one Logseq graph instead of separate work and personal graphs?
How does the system classify information so it can be retrieved later?
What’s the practical method for turning raw thoughts into actionable tasks?
How are meeting notes organized for a specific person like “John”?
How does the workflow track feedback differently from meeting notes?
Review Questions
- How does tagging replace the need for a separate work graph in this workflow?
- What combination of tags and queries is used to pull up meeting items for a specific person?
- How does the Ctrl+Enter to-do state cycle support daily task management?
Key Points
- 1
Keep one Logseq graph and separate work vs. personal at the block level using hashtags or links.
- 2
Tag blocks consistently with categories like “feedback” and “inbox” so queries can retrieve the right context.
- 3
Use Ctrl+Enter to create and advance to-dos through “to do,” “doing,” and “done” states without leaving the page.
- 4
Use a home page map as a landing page to quickly view work to-dos, personal to-dos, and general to-dos.
- 5
Manage meetings by querying inbox notes for a specific person, then clean up by removing the inbox tag after the meeting.
- 6
Store professional feedback in dedicated per-person pages (e.g., “feedback for John”) and optionally nest entries under dates for a searchable track record.