implementing GTD
May. 30th, 2006 11:16 pmI'm thinking I should implementing the GTD workflow in a small laptop that I can take with me everywhere. An alternative would be to use an Internet application ...and always carry paper with me, which I can copy into the system later.
I would like a super-ToDo-list program that classified items inside projects, and allows you to process each item with GTD actions, namely:
* Do it (mark item as "DONE")
* Defer it (whether 30 minutes or 30 days): integrate with a Calendar/scheduling system
* Delegate it (mark item as "WAITING")
* Dump it (send item to trash)
Ideally, the system would automatically go through the Next Actions (projects) one by one, and, for each one, I would be presented with these 4 big buttons.
Any ideas?
I would also like a process for the unstructured InBasket stuff. It would go through the items there, and for each item, you can:
* Do it (send item to trash)
* Dump it (send item to trash)
* Move it to a project (or create its own project)
* emails to reply to
* research ideas to write down
* software ideas to write down
* blogs/news to read, blog entries to write
* unexpected work assignments
* bugs to fix
* homework (each homework should become a project in itself!)
* bills to pay (not exactly unexpected...)
* unexpected health symptom to visit a doctor about
* interesting people to talk to / hang out with
Research/Publication Projects:
* new ideas to think about
* worked out ideas to write down for publishing
* papers to read
* consult with experts
* present to peers / experts
Software Projects:
* software to design
* software to write
* bugs to fix
* techniques/patterns/commands to learn
Bureaucracy
* paperwork
Future Gigs (project)
* applications
* networking: go to conferences (subproject)
Health:
* exercise, stretch regularly
* regular check-ups: dentist, etc.
Social Life:
* go dancing
* invite people for activities
EMAIL
Emails about which I can act rightaway in less than "2 minutes" will not need to go into the system. The exception is when I need the reply. Given how easy it is, it is very tempting to use floating emails a replacement for entering the item into a project. But this way, you lose track of what needs to be done.
I would like a super-ToDo-list program that classified items inside projects, and allows you to process each item with GTD actions, namely:
* Do it (mark item as "DONE")
* Defer it (whether 30 minutes or 30 days): integrate with a Calendar/scheduling system
* Delegate it (mark item as "WAITING")
* Dump it (send item to trash)
Ideally, the system would automatically go through the Next Actions (projects) one by one, and, for each one, I would be presented with these 4 big buttons.
Any ideas?
I would also like a process for the unstructured InBasket stuff. It would go through the items there, and for each item, you can:
* Do it (send item to trash)
* Dump it (send item to trash)
* Move it to a project (or create its own project)
Some use cases:
STUFF GOING INTO MY IN-BASKET
(i.e. stuff that happens without being part of a project plan. Note that some of these correspond to the theme of a project, into which they should potentially be moved.):* emails to reply to
* research ideas to write down
* software ideas to write down
* blogs/news to read, blog entries to write
* unexpected work assignments
* bugs to fix
* homework (each homework should become a project in itself!)
* bills to pay (not exactly unexpected...)
* unexpected health symptom to visit a doctor about
* interesting people to talk to / hang out with
PROJECTS I COMMIT TO:
Research/Publication Projects:
* new ideas to think about
* worked out ideas to write down for publishing
* papers to read
* consult with experts
* present to peers / experts
Software Projects:
* software to design
* software to write
* bugs to fix
* techniques/patterns/commands to learn
Bureaucracy
* paperwork
Future Gigs (project)
* applications
* networking: go to conferences (subproject)
Health:
* exercise, stretch regularly
* regular check-ups: dentist, etc.
Social Life:
* go dancing
* invite people for activities
Emails about which I can act rightaway in less than "2 minutes" will not need to go into the system. The exception is when I need the reply. Given how easy it is, it is very tempting to use floating emails a replacement for entering the item into a project. But this way, you lose track of what needs to be done.
(no subject)
Date: 2006-05-31 08:40 am (UTC)For actual projects which warrant planning, I'd use something like this:
http://en.wikipedia.org/wiki/Open_workbench
Strangely enough, although I professionally work on several projects simultaneously, I haven't felt the need to schedule my work more precisely. Part of the reason for that is there's always more than plenty work to do. I charge hourly so there's no incentive for me to prioritize anything really, unless there is something really urgent and then I do it immediately.
For software development projects, I'd use something like CVS or subversion. There it's important that you can track a change you made 3 months ago for a spefici issue. Any project with a duration less than my short term memory span (which admittedly is getting shorter every day) I wouldn't even bother to track.