![]() I do agree with the person that wrote maybe I am the problem, not the tool. I started using DevOps however, it wasn’t working out.Īnyway, I don’t think there is a magic tool out there. I have projects at work and trying to use the Microsoft software is a nightmare (No, I do not have planner accessible to me). I am also that person that has used so many programs or tools to achieve the ultimate workflow however, I will not stay with one tool…I will use a bullet journal, then maybe a book to write notes, I will use Logseq (I use Obsidian to sync Logseq) and Obsidian. I have come to the conclusion that Logseq is good for some things and Obsidian is good for the rest. The Kanban plug-in doesn’t allow me to move items back and forth (no offense to the person that wrote it…and perhaps I may be missing something). For projects, I seem a little lost with Logseq. I use the journal pages to write thoughts, meeting notes, TODOs (I use deadline dates). I use queries in the journal (config file) to show my overdue and personal tasks. We watch shows/movies a few nights a week. The “Watch” is a reminder for some family time. (or (get h :block/scheduled) (get h :block/deadline))) result)) Here are my current query buckets: :default-queries It local-first software and Github friendly and that’s good enough for me. It does well enough in the business of getting things done that I am no longer trying alternatives. I determined that in almost every case the productivity issue was me or my system and not the tool. I’ve spent years trying different tools and I eventually settled on Logseq. By changing metadata I move things between buckets. If something gets bumped forward (avoided) too frequently I mark it as a Lemon and focus on getting it off the list.Īlso, and I think we may be on the same page, I don’t actually use parent level outline items as buckets. ![]() I don’t beat myself up for just bumping things forward. And I rarely completely everything listed for a given day. But, like you, I am in a constant state of flux, rejiggering priorities daily. My major takeaways were limit the amount of work (WIP limits), limit lead time (ship started things to get them off the list), and have a way to visually see all the work in progress at once. I read 2 books on Kanban and dozens of articles, but in the end, when used personally, there was no special sauce in the swim lanes, the boards, and the dragging and dropping between columns. I just keep chipping away a bit at a time until the thing is done. I would call what I do a systems approach (see James Clear’s Atomic Habits). Even if a task has a Deadline it almost always has a Schedule. I use the Schedule date repeater to designate the habit and the Deadline only for real world deadlines. When I put in the time (on any of the subitems) I check it off and it bumps itself into the future. In this way every project is itself a repeating task with subtasks. The Logseq feature I lean on most is repeating tasks. This reminds me that I’m just committed to about 25 minutes of work, what some call a pomodoro. Some of the tasks I mark with a #25m tag. Maybe a task is appropriately tagged, maybe not, but I know what I’m doing when I’m doing it. That #Writing tag will link to a page about that hat/activity. #Writing, #Publishing) to the task/subtask. If I need the reminder, I can just add a tag (e.g. I don’t generally wear two hats at once and I know which hat I’m wearing when I work on a task even if I’m not using buckets. That is, if you write a blog post you may wear a Writing, Editing, and Publishing cap. But I do have the concept of hats (or roles, what is ordinarily tied to a bucket or swim lane). I get done what I get done today and what doesn’t get done just gets bumped forward to tomorrow. My main page and its sections are included below. I don’t really model my work using swim lanes anymore.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |