Why I no longer use LOGseq for taskmanagement (but somehow still do)

Thanks for pointing out the plugins again. Yes, both the Agenda plugin and the Kanban plugin are the right step to make LOGseq fit for task management.

However, in order to manage really extensive and complex tasks, I definitely miss the possibility to work in these views. This means more than just being able to create new tasks in the Kanban/Agenda view. I am talking about searching and filtering within these views - by text, date, tags etc… I am talking about an appealing visual highlighting of overdue tasks. Drag-and-drop support for the columns. And there is still a long way to go for Logseq and the plugins.

One question that surely arises for the developers is the core question: What is my main target group in LOGseq? LOGseq is extremely flexible and can therefore be used for many different scenarios. The danger, however, is that when trying to do justice to all these possibilities, none of them are well supported (“Jack of all trades, master of none”).

On the other hand, there are tools that are specialised for a particular use case. “Stacks” and “Tick Tick” are just a few of the hundreds of tools available here, that specialise in task management. And even among these specialised tools, there is no one best.

So the question arises in which areas and thus for which target group LOGseq should try to become really “good”. My personal choice wouldn’t be task management :wink: but I would be pleased to see LOGseq evolve in this area.

I myself still use LOGseq for the “small, daily tasks”. Whether LOGseq is suitable for task management depends very much on your own “task situation” and task complexity.

1 Like