I feel ya, my friend. I also have read the org manual a few times, and it feels so big you can't hold a mental model for long enough to make sense while incorp

I feel ya, my friend. I also have read the org manual a few times, and it feels so big you can't hold a mental model for long enough to make sense while incorporating all its features. As you know, org mode has too many features to use them all at once (like emacs itself). What (kinda) worked for me was, after knowing "I've read it all", to purposefully "downgrade" to a very very basic workflow. I thought then I would start adding features on a need basis, because I had the perimeter of what it can do. But it turns out I haven't added anything else to the trivial workflow. There's a bit more info here ( https://puntoblogspot.blogspot.com/2018/12/3-basic-org-agenda-tips-for.html https://puntoblogspot.blogspot.com/2018/12/3-basic-org-agend...), but essentially the trick was to use just one capture template for everything that just schedules the current task for today (so it appears in agendas until I mark it as done), and one single file, without different subtrees. ("t" "Todo" entry (file+headline "~/org/tasks.org" "Tasks") "* %^{title} \n SCHEDULED:%t\n %?\n %i\n %a\nAdded: %U") I feel safe because in that file, down means "later", so I still can rely on my basic common sense.