Another Logseq check-in

I’ve now been using Logseq for almost two full weeks and I wanted to give an update on how it’s going.

Overview

After attending a conference at the end of July and seeing my friend Eric Potter give a talk on knowledge management, I have been all-in on not just taking notes, but managing them in a way that’s organized and searchable. As much as I love my pens and paper, I really haven’t written any physical notes since maybe day 3 of using Logseq.

I did use my iPad and Pencil for a few days, but I’ve started writing my notes directly in Logseq. I’ve found it’s easier, especially if I take a few anchor notes during a meeting and then flesh them in after the meeting ends.

Daily Workflow

I start each day by pre-filling some things in for that day’s journal entry, things I know I’ll do:

The “my current project” page has details about the project; who the team members are, links to Jira and Confluence, etc.

The “standup” page has dated entries for each time we meet. Early on, I was creating a separate page per meeting, but that seemed like overkill, and besides, it’s good to look in one place to find all my notes taken during that particular meeting.

I do the same for the “dev meeting” and “client status meeting” pages.

For each meeting, I capture when the meeting starts and stops. I also capture who attended, and each attendee gets their own page so I can keep notes on the people I’m working with (hobbies, birthdays, the office they work from, etc.)

Of course, in my real graph, those have actual project, team, and client names.

You’ll notice “onboarding” isn’t a page. I simply take notes related to what I’m doing, sometimes creating specific pages for tasks I’m working on. I’m not convinced this is the best way to do it, BUT as I’ve mentioned before, I can easily change it in the future.

As my day progresses, I’ll add additional notes related to books I’m reading, talks I’m working on, or blog posts I’ve published:

The pages for the book and the talk have a lot of information. For the book I’ve created an outline of the chapters so when I take notes, I’ll do it under each chapter heading.

For the page related to my “Learning and Collaboration” talk, I have the abstract, the original slides attached, an outline of the original slides, and a new outline since I’m making some changes to it.

When I’m done with this post today, I’ll add it to the entry for August 8.

Oh, and I do several pushes to Github every day! This is really simple because with the git integration turned on, all I have to do is push since Logseq handles adding the new and changed files and committing them locally.

Current Graph

Here’s what my current graph looks like, zoomed out to avoid showing details:

On that graph, you’ll see one node off by itself, not connected to anything. I’m experimenting with Logseq templates, and that’s where they live. I hope to share some in another post.

Final Thoughts

I’m still finding a lot of value with Logseq, although there are some problems I still haven’t figured out with the biggest being mobile access of the data. I haven’t put in the work to figure it out, but it’ll have to happen soon.

My child-like excitement of the graph has faded a bit, but I still look at every now and then since I’m more focused on getting data in.

One of my friends at work still isn’t convinced, and I get it. It’s not a silver bullet by any stretch, BUT for someone who needed some organization and the ability to search notes, it’s been a positive addition to my toolkit.

---