@all
Thank you very much for all the rave about my contributions
Thank you very much for all the rave about my contributions
fapapa;57505 said:The problem to me is more that the writing style is too "stiff," if that makes any sense. One example that comes to mind is that "The Threefold Model for Evaluating Daily Work" (p. 196) is much harder to "get" than "Don't Let Urgent 'Stuff' Hijack your Day," for example. Of course this is just a heading and there are entire paragraphs (and chapters) that this can be done to.
Jeff K;57519 said:All the checklists, methods, software tweaks, etc., are just icing on the cake, but only once the cake is fully baked in terms of being founded on an internalized understanding of the core principles.
kewms;57447 said:... you may need to make sure that you've really captured *everything,* and that you've followed the GTD definition of a project... If you're only including, say, your currently assigned work deliverables, then you're probably missing the majority of the things that are actually going on in your life."
To move a project forward, all you need is the very next physical action. That goes on your NA list. Now, you may find that you'd rather plan things out in much more detail. That's fine, but those additional plans are project support, not Next Actions (unless they are immediately doable with no dependencies).
Katherine