How do you guys implement Task Management system? Alternative to logseq

Questions & Help
1

I have been using these categories for tasks to build advance query to fetch TODO –>

  1. OVERDUE - tasks that is way over due ( tasks have been in due for 7 days )
  2. DUE - tasks whose due date has passed ( tasks stays here for 7 days )
  3. TODAY - tasks which are due today
  4. NEXT - upcomming tasks in next 7 days
  5. FUTURE - upcoming tasks b/w next 7th day and 14th day

Now i am having hard time how to come up with system in which task should fall under one of these categories, when a taks can have these properties ‘Schedule date’ ‘Deadline date’ ‘Repeater’.

it’s hard to come up with system that deals with all the combination of properties.

Few questions:

  1. Does this commutity have very well implemented system already? Or does each and everyone come up with there own?
  2. Does logseq plan to implement this natively?
  3. Do you guys seprate your tasks management from notes? If yes can you guys recommed me one. ( I liked the idea of having my notes and tasks in same system. )
  4. Can you suggest me diffrent logseq alternative if they have task management system native.
1 Like
2

Too complicated. My opinion about task management system: simpler is better.
The essential thing is to review the list of activities periodically.
Your memory is an indispensable part of your task management system. You need it to choose the activities to work on.

3

As my username implies, you should check out the Getting Things Done (GTD) methodology for task management. It’s a universal system that can be done in any app, including Logseq, or even on paper.

But to answer your question more directly, I only use the TODO and DOING tasks in Logseq. In addition, I always add a context tag to a task. The context label is tell me what real, physical things must be true for me to do the task. i.e. Tasks with the #@home tag mean that I’m required to be at home to do them. There’s also #@desk, #@errands, etc.

With this simple setup, things get real easy. Just go to the context page you are in at the moment and you’ll see that Logseq automatically will show you which tasks link back to that page. Better yet, build a simple query on that task page so you only see active tasks with that tag.

For things with due dates or start dates, I use my Calendar. Logseq has “scheduled” and “deadline” capabilities for tasks, which can also be used, but because I already need to use my calendar anyway for appointments, it’s simpler to just tether are time-bound things there, IMO. Otherwise you’ll end up repeating yourself and trying to make sure dates in Logseq align with dates on the calendar, etc. No reason for this.

If a task is only bound by a single day (not a time of day), then put it on that day’s journal page in Logseq. Each day, check that day’s journal page to see any notes and tasks you left for yourself. It’s very easy and quick to do things this way and it’s very nice to always have a way to park things for a future date.

I will be writing up a Reddit post at some point here that goes over the details of how to get GTD running smoothly and easily in Logseq. There’s a lot more to cover than what I’ve written here but at least start with some of these suggestions and you’ll be on your way.

2 Likes