3 ms·
I mainly use org as my daily agenda. Inside my agenda I keep my projects. I note when I've worked on them, what problems I encountered etc. Then I schedule task
by terminalcommand 9y ago
I mainly use org as my daily agenda. Inside my agenda I keep my projects. I note when I've worked on them, what problems I encountered etc. Then I schedule tasks to certain days. I always make sure that I leave enough free time inbetween and if I'm feeling tired I reschedule the items.
This workflow works for my side projects.
For more serious work I open up a seperate org file. I quickly note what parts need to be done, capture my thoughts on them, make a plan and start. If my plan doesn't work I note why it hasn't worked, my current thoughts then I alter the plan.
The most important thing IMHO is to be able to capture what you're thinking honestly. Over a time you can analyze the logs and make better decisions.
In the past I've tried GTD, no plan and just Pomodoro, kanban etc. and they all worked miraclously at the start but my productivity suffered as time passed by. Because with these constructs I was forcing myself to work all the time.
My new method is to treat my org-agenda as sacred, I try not to schedule many items for a day. I give an honest effort to make them happen, but if I can't or psychologically don't want to I reschedule/cancel them without feeling any guilt.
Org-mode is fairly simple if you stick to the basics. You need to devise something that will work for you. Be that a giant file where you keep everything with tags. Or be that a Readme.org for every project. What matters is that you plan ahead and actually stick to it.