John Wiegley: re: https://sachachua.com/blog/2024/11/excerpts-from-a-conversation-with-john-wiegley-johnw-and-adam-porter-alphapapa-about-personal-information-management/

On reviews: I do something similar when I have to follow up on Org mailing list threads (say, things waiting for a reply). My approach is somewhat different:

1. when I delegate tasks, I first put them into WAITING state to appear during weekly review where I decide what I need to do about a given task - follow up next week, re-review after a month (I use schedule here), defer to next weekly review, or something else
2. When some non-standard follow up action is necessary, I configured agenda to display the last note taken to remind me about it
3. If the task makes sense in certain context only, or when I am working on certain project, I use tags: @place for places, or SOMEDAY/HOLD for projects I indefinitely/temporarily suspend. All the agendas are respecting these tags
4. Certain tasks are annoying in a sense that I cannot act on them, but would like to remember until an opportunity arises. For that, I set up a spaced repetition: the tasks appears in my agenda regularly, but every time I can choose to reschedule it either some time "soon" or "later" - things I remember are pushed back further this way and do not clutter my agendas unnecessarily.

PS. I also use daily reviews and also not trying to handle all the tasks (there is a time cutoff), but those are more for technical things like tagging, adding schedules, efforts, categories, refiling, etc

In reply to @jwwiegley:matrix.org
I love that idea of incorporating spaced repetition into this!!! Right now I look at the reviewed task and decide to push 1 week, 2 weeks, 1 month, 2 months, etc. But for several kinds of tasks I could do better by keeping track of how many times I've pushed it like this, and to dynamically extend the next review date accordingly.

In reply to @jwwiegley:matrix.org
Another thing I did which was helpful is that I changed my effort estimates to roughly follow the Fibonacci sequence, due to https://www.mountaingoatsoftware.com/blog/why-the-fibonacci-sequence-works-well-for-estimating

In reply to @jwwiegley:matrix.org
Today I'm going to implement a KEYWORDS system and an org-ql keyword predicate, because I'm realizing that I want tags that aren't always visible, that behave like categories but without represent any kind of hierarchy. Then I'll make some keyword agenda queries.

In reply to @jwwiegley:matrix.org
Sometimes I just need custom lists, like "org-mode stuff I want to do on a rainy day" that might be scattered in lots of places

keywords, topics, categories, tags ... they are all a bit fungible. I've decided to define their meaning as follows:

• categories are hierarchical
• tags are for "resources required to address the task", like people, places and situations
• topics and keywords are attributes of any task and act as tags normally do in other systems