• Our deepest thanks to the many GTD enthusiasts who have posted in and read this forum over the years. Because use has been steadily declining in recent years, we have reluctantly decided to make this forum a read-only reference archive. There is an active GTD discussion community on the new GTD Connect. Copy/paste this link to get a free trial: https://bit.ly/4hYicYV We still offer a range of other free resources for GTD enthusiasts at: https://gettingthingsdone.com/resources/

Project Support Material on Next Action List ?

So in my NA list (Focused on single project view) should I be placing reference/project support material in this list ? I use OmniFocus and have a context called "Reference". So when i view my list i can see a greyed out area, letting me know its a reference item. But should i have another project or subproject with a collection of project support material ? current workflow example:

Project: Create Learn French iBook
NA x
NA z
Reference: a
 
Tado;101444 said:
So in my NA list (Focused on single project view) should I be placing reference/project support material in this list ? I use OmniFocus and have a context called "Reference". So when i view my list i can see a greyed out area, letting me know its a reference item. But should i have another project or subproject with a collection of project support material ? current workflow example:

Project: Create Learn French iBook
NA x
NA z
Reference: a

Is it working for you, or are you finding it a problem? If it's working for you, great.

I work in much the same way - my Reference context is an 'on hold' context and excluded from my Contexts perspective, so I don't see them in my action lists, but it's available in my project view. If I get too much reference, then I might drop them into a separate reference project on hold or separate it into a Dropbox folder instead, but for odd bits of information, OmniFocus is great.
 
Like you mentioned when its only small amounts of reference materials, then its fine.
Thanks for the advice !
 
I leave small bits of reference material in the project as an action as well. Large amounts of electronic reference go into DEVONThink and paper gets a file folder.
 
I do the same thing.

When I pile up more than two or three of these, I also have single-action lists for most of my work projects (as opposed to GTD projects; a single work project will usually generate many GTD projects), named "Agenda" as in "Widget Project Agenda". Agenda is entirely the wrong word to use for this, but I use it anyway.

That's where I put things that (1) I don't want to forget, that (2) aren't actionable, that (3) I want out of my Inbox, that (4) are associated with the work project in question. I guess it's essentially a someday/maybe list for the project.
 
Top