Cal Newport’s Time-block planner in Logseq
Вставка
- Опубліковано 27 лип 2024
- 0:00 Daily metrics
4:51 Engineer's Daybook
6:50 Time-block planner
11:00 Create a template
14:24 Weekly planning
16:35 Stage your work
19:53 Collections of notes & tasks
21:00 Filter collections
22:00 Meeting notes
Email-list:
knowledgeworker.blog/ - Навчання та стиль
Just a small tip that you or viewers might like to know: for your cut-and-paste use cases, you can also drag-and-drop the bullet points if you find that faster/easier, even from the linked references footer into the daily journal page.
You can even Option-drag / Alt-drag to create a reference instead of moving the block-this can be useful if you want to keep tasks in their original place while still seeing them and checking them off on the daily note (say you’d like to read through your Week Ahead page at the end of the week in a weekly review process, to quickly scan how you did on your week’s plans).
A caveat to be aware of with the references: only Logseq will understand them, at the plain text level they are not very pretty if you work with your Markdown files in other tools. If you never do that, it might not concern you.
Note: the use case I gave for references would be more appropriate for someone who makes a new weekly plan page every week, e.g. numbered with 2023-W12 or similar-Josh has said his workflow is to clear the one page and re-use it, in that case you’d lose the record in your daily notes of the tasks you completed. Probably undesirable!
Thanks Josh. This is so helpful. I've been using LogSeq for a couple of weeks to keep on top of things. I'd discovered templates, but hadn't started using them for my Journal. This could be a game-changer!🔥
cool Presentation!! Thank's for your time to produce that!
You're most welcome, I'm glad you enjoyed the video. :)
So interesting to see different people's approach to things. Personally I prefer to "blend" todos into my notes (and often define them in project pages not the daily journals themselves), especially since Logseq handles that so well - e.g. to show notes back onto journal pages via queries or using the calendar plugin to plan the tasks of the day seems a bit smoother. But sometimes "low tech" can work beautifully too. The templated daily metrics especially seems to make sense.
Loved your tips at 17:50 and 22:10 to "pre-stage" items that you can cut-paste from one page onto another through the reference. That's really smooth.
Hi Josh, really informative video.
I've been using this as a starter template with some of my own modifications for the last few days, and it's really helped me to get started with Logseq, so thank you!
I have set up my environment to use Logseq and Obsidian, and I've just stumbled across the time-blocking video that you created for Obsidian not long before this one.
One thing that really stood out was how your time-blocked agenda showed up in a day calendar widget. Do you prefer your daily journaling / time-blocking in Logseq or Obsidian? Or do you use a combination of both, and if so, how?
I’ve never heard of Logseq until this video. It’s very interesting to see how you work and how you digitalized your work. I was wondering why you didn’t use another tool until closer to the end of the video when you began showcasing all the cool features like linking The Week Ahead to certain days, tags, and future meeting notes. Those really highlighted the benefit of Logseq. I’ve kept my workflow entirely in Outlook, OneNote and Outlook tasks/Microsoft To Do since nearly every organization has those available.
Outlook integration is something I’d love to write myself someday. Having that populate my time block grid would be amazing. What all other tools have lacked aside from the bullet journal is the fluid migration of tasks which is why I love logseq.
Very helpful thanks! What's your workflow for once you've finished a week in the Week Ahead, just re-tagging each day with a new date? Or do you make a totally new week ahead each week?
I reuse the same week ahead page and retag the days. Since the video, I’ve also added a future log to track tasks that are further out. 😁
I enjoy your video very much Joshua and plan to implement your ideas. A question about "The week ahead" page - if I understand you correctly, you overwrite your week ahead page every week; you don't keep an archive of those pages. Am I correct?
Yes, exactly. Each week I overwrite and migrate tasks that remain, but I don't keep a record of the weekly page.
@@joshuaduffney Thanks
@@johnl1160 You're most welcome
Thanks for this great walkthrough of your system Joshua! Very insightful.
How do you keep track of the todo's that you added during the day on your "Tasks" section? These might be tasks that you will address at a later time. During my week ahead session, I find myself scrolling through my journal pages of the past week for any open item. Do you consolidate these back into your week ahead page during your daily shutdown? Thx!
Hey Johan, great question and you're spot on. During my daily shutdown, I either find a slot for those tasks in my week ahead page or I use the /tomorrow command to "migrate" it in bullet journal terms to the next day and find a slot for it. It's not uncommon for shallow tasks like scheduling a haircut to be pushed off a few days but at least the task is never forgotten. :)
Worth noting also, in case it starts to get away from you: Logseq gives you a built-in “TODO” page where you can find every open task from anywhere in your notes database (“graph”), grouped by their source pages including daily journals. Just Cmd-K / Ctrl-K and type “todo” to find it.
That can get out of hand too, but you can use the filter icon on the linked references section like Josh showed in the video, to narrow them down.
The same is true for all the task statuses, by the way (WAITING, DONE, etc.)-the task statuses are basically a special kind of link. You can build a sophisticated task manager tool by using Logseq’s query features, but those built-in status pages can take you pretty far.
Have you found a way to incorporate Logseq's Agenda plugin into your workflow?
Do you take notes when you read? Do you use Logseq for note-taking?
Thanks for the video by the way, very helpful.
Hey Thomas, I haven't as of yet. Although Dario from OneStutteringMind showed it to me during our conversation and seems like it was be an excellent plugin for time-blocking.
I don't normally take notes while I read, but I do write in the margins and mark up the book which I revisit and take notes at a later date. Logseq was the place I was taking notes, but I'm experimenting now with apple notes and Scrivener for my writing project notes.
Sorry for the delay in replying, and I'm glad you found the video helpful. :)
What theme is this?
It looks like you are using Obsidian for PKM (Personal Knowledge Management) and Logseq for more day-to-day like activities.
Is there anything in particular stopping you from using Logseq for PKM also? I ask because I like the open source characteristic of Logseq over Obsidian. Thanks
Hey Paul,
That's a great question. I haven't found a great way to replicate what I love about Obsidian in Logseq. Obsidian lets me retain some of the look and feel of a physical slip-box and the file-level organizations of notes help orient me in the space. So far I haven't been able to accomplish that in logseq. Not saying it isn't possible just that I haven't spent the cycles to make it happen. :)
@@joshuaduffney Good point. I prefer a physical feel and folders as well, yet open source software is important to me too. Maybe a workflow using tags as a replacements for folders will suffice. Or maybe I will be using Obsidian with folders and Logseq for further note processing. Will need some experimenting. Thanks for the response
the daily metrics concept, is that from cal newport ideas or something else? trying to read more about what kind of things you put in there.
is there a way to make a list of TODO without writing "TODO" or "/TODO" on every single line?
Cntrl+enter on windows cmd+enter on make i believe does that.
You moved from Obsidian? Why the change?
I've found the dynamic and browser-like nature of Logseq to be a better tool for my task management, planner, and journal, which is why I've moved the time-blocker into Logseq, but my knowledge management has remained in Obsidian. :) The main reason is the fluidness that logseq offers by being blocked-based vs file-based.
Hi Josh, how are the Todos in Daily Metrics different than those under Daily Overview? Sorry I can't send an attachment in this comment dialog box
Hey John, you can think of the daily metrics as goals I've set and the tasks in the time-block as ToDos. For example write 1 hour is the goal, but a task in the time-blocker might be write chapter 1 from 8 am to 9 am, which would then fulfill the daily metric I set for myself. Lmk if that helps or not happy to dive further into it. :)
@@joshuaduffney thanks for the clarification.
@@joshuaduffney You have beautifully combined the concepts/strengths of BuJo and Time Blocking using Logseq. I am foolishly trying to learn all 3 at the same time :). I assume I can view Daily Overview as equivalent to the Daily Log. Is the Daily Metrics and related ToDos tabulating the items that will make your day to be considered as successful? Otherwise pardon me for thinking that that item is not necessary :)
@@johnl1160 You are correct. Daily metrics set the criteria for what I consider a "productive" day. :)
Love that you caught on to my integration of all those wonderful ideas!
Not sure, maybe it was meant *only* to present the structure and discipline of your way of note taking. However, from the lack of data linking and tagging, it seems this method sways away from the point of LogSeq and the strength of data structures available in it. Id go as far as saying, that too much visual structuring like this will degrade the true data structure. In simple words, one shouldn't focus on what's visible on a page (especially journal), but on the important invisible links created by links and tags, possibly ame spaces and properties, etc. There are some rules of thumb, like every ToDo should have at least one tag, every tip-idea bullet at least one link and/or tag, etc., but that's all beyong a scope of YT coment. Do as much formatting and structuring as you like, but don't let it interfere with the main LogSeq principles. iMHO.
0.00 What I love and hate (and love to hate) about logseq, is that what you just said is completely false. Think about it.