Textfiles/Markdownfiles I use the following filestructure: tasks/ done/ lowprio/ blocked/ task1.txt in the file: - [ ] subtask1 - [x] subtask2 ... other subtasks, x marks them as done other info...
Textfiles/Markdownfiles
I use the following filestructure:
tasks/
done/
lowprio/
blocked/
task1.txt
in the file:
- [ ] subtask1
- [x] subtask2
... other subtasks, x marks them as done
other info
task2.txt
task3.txt
whenever I get a new task I create a new txt file, when a task is completed I move it to the done directory.
As tool I use pycharm because I already use it for programming, if you most of the time you already have something open that handles textfiles I would use this, otherwise I would recommend obsidian.
Pros:
low complexity
lots of choices for tools, you can use anything that handles textfiles
easy to search, just use textsearch to search all files
low clutter, in jira for example there are often a lot of fields I dont care about
fast
for tagging just use #work and then search for it
you have file timestamps for modified date
easy to put into git
Cons
what was really nice in onenote is that it had the win+n shortcut for new notes, you can create this for textfiles but that is at least some effort
no email integration, in outlook 2016 you can flag emails and then you have a list with emails where you have to do something
General thing I learned about managing tasks
you want a single place where all your tasks are, else it is easy to overlook something you have to do( I often forgot about emails because I didnt create a task for each email where i have to do something)
you want creating/ editing/ viewing tasks as low overhead as it can be so you actually do it
dont overthink what you write, often email_from_x.txt with no content is enough, the more you do it the more you know how much exactly you have to write, also it only has to be understandable for you, so dont worry about grammar, again you want low overhead of creating the task
you only want max 5 tasks or so active at a time, so move the remainder into lowprio and if you need more get them from there, the problem with too many tasks there is you spend too much time deciding which task to do instead of doing the task
in meetings/phonecalls write down what you have to do with a few bulletpoints and at the end possibly repeat them and ask if you missed anything
sometimes the task is small enough to just do it without recording it.
when interrupted it can be useful to note down what you are currently doing so you can easier continue later
if you have to undo something later, e.g. you commented something out in the code, it can be helpful to make this a subtask so you dont forget it.
Textfiles/Markdownfiles
I use the following filestructure:
whenever I get a new task I create a new txt file, when a task is completed I move it to the done directory.
As tool I use pycharm because I already use it for programming, if you most of the time you already have something open that handles textfiles I would use this, otherwise I would recommend obsidian.
Pros:
Cons
General thing I learned about managing tasks