4 ms·

Is GTD a software or philosophy? Could you please provide a link ? I could only find the link to a book .

justadudeama 9y ago
Philosophy. Basically: * Write everything down that comes to your head. Review that information. * Categorize everything into actionable tasks, or waiting items within a project (Anything that takes more than one task) * Clear your inboxes (Physical and digital) often * Weekly review of how the system is working for you Coming along with that is a lot of software to try and make it really easy to follow. I personally use Todoist, a lot of people in the Apple ecosystem like omnifocus, but really any task-app and a calender can do (paper works as well). I suggest reading the book if you are someone who struggles with productivity or wants an imporoved system. I like the book because even if you don't fully adopt the system, just about everything in the book works independently (You don't have to do EVERYTHING in the book to get an improvement, as I see often with other similar books).
- gt_ 9y ago
  Do you use the Todoist Windows app? I like Todoist and have used it for a few years but the Windows app is crumbling! They moved to the Windows Store and the new app has tons of bugs. I keep losing tasks while trying to edit them. I will rearrange a task only to find now I have a duplicate. I try to delete one and I lose both. So, the whole ‘task list’ idea has been undermined by the app’s bugs. The legacy Windows app still works but is getting it’s own set of bugs as time goes by. Have you had these experiences? Just wondering. I’m currently shopping for another solution. I have e-mailed them and the customer service seems to be waning along with the software support.
  - justadudeama 9y ago
    No, I use the Chrome App.
    - gt_ 9y ago
      All Chrome apps are coming to an end in the next month or two :(.
stinkytaco 9y ago
The book is the best place to understand it, in my opinion. There's plenty of summaries, but the book is good. But if you take nothing else: next action. When planning a list put the next physical thing you need to do (call, draft, debug a specific routine, etc), not abstract concepts.

Philosophy. Basically: * Write everything down that comes to your head. Review that information. * Categorize everything into actionable tasks, or waiting items within a project (Anything that takes more than one task) * Clear your inboxes (Physical and digital) often * Weekly review of how the system is working for you Coming along with that is a lot of software to try and make it really easy to follow. I personally use Todoist, a lot of people in the Apple ecosystem like omnifocus, but really any task-app and a calender can do (paper works as well). I suggest reading the book if you are someone who struggles with productivity or wants an imporoved system. I like the book because even if you don't fully adopt the system, just about everything in the book works independently (You don't have to do EVERYTHING in the book to get an improvement, as I see often with other similar books).

gt_ 9y ago
Do you use the Todoist Windows app? I like Todoist and have used it for a few years but the Windows app is crumbling! They moved to the Windows Store and the new app has tons of bugs. I keep losing tasks while trying to edit them. I will rearrange a task only to find now I have a duplicate. I try to delete one and I lose both. So, the whole ‘task list’ idea has been undermined by the app’s bugs. The legacy Windows app still works but is getting it’s own set of bugs as time goes by. Have you had these experiences? Just wondering. I’m currently shopping for another solution. I have e-mailed them and the customer service seems to be waning along with the software support.
- justadudeama 9y ago
  No, I use the Chrome App.
  - gt_ 9y ago
    All Chrome apps are coming to an end in the next month or two :(.

stinkytaco 9y ago

The book is the best place to understand it, in my opinion. There's plenty of summaries, but the book is good. But if you take nothing else: next action. When planning a list put the next physical thing you need to do (call, draft, debug a specific routine, etc), not abstract concepts.