|
|
|
|
|
by whatever1
1778 days ago
|
|
Unfortunately all of the options are bad. I tried to map out the space of info that I need to track in my engineering job: 1) Tasks from emails
2) Meeting notes with details of people who participated
3) Project related tasks that can have a long format and can be tagged/ delegated
4) Scratchpad for unrefined ideas
5) Detailed documentation for completed technical tasks / ideas
6) FIFO list of high priority small daily tasks I try to fight the above battle of information organization with a combination of MS Outlook, Onenote, Github boards, MS Todo, physical Sticky notes, a physical notebook and scratchpad, but it is messy. I occasionally try to find alternatives (notion, bear, trello etc) but no luck so far |
|
In Outlook I mark emails that I want to respond to/deal with later as "unread" or else apply the "followup" flag depending on how much work responding will take. There are downsides but I have so far been able to keep the scheme manageable (single-digit quantities with the unread/followup tags at any given time).
I use a paper notebook, physical sticky notes, and scraps of paper for general notes depending on how ephemeral their importance is.
I use Onenote for meeting notes and a running to-do list, as well as a rough knowledge base, but it's far from perfect:
It strikes me that the central problem is that the tree structure is not the right one for notes. A wiki might be better. However, the portability and convenience of Onenote despite the shortcomings (for my needs) make me hesitant to try anything else.