Project or Folder?
 

Suppose I have tasks that look like this:

Administer Web Server
- install security patch #123
- add pages for marketing
Adminster Database
- run backups every night
- weekly review of queries
Administer App Server
- write new credit card interface
- test database performance

Of course the subitems are nicely categorized into projects or single actions.

Originally I set the high level items ("Adminster...") as projects. But since these are ongoing task (hopefully forever, or we'll be out of a job!), it doesn't seem they are tasks that will ever end.

So, I'm thinking that maybe these Adminster lines might be better off as folders?

I'm a bit of a GTD newbie, and not really understanding (obviously!) how the folders fit in with the concept of projects and subprojects.

Any clues appreciated, many TIA!!
Mark

--
Mark Harrison
Pixar Animation Studios

I make the decision about projects vs. folders pragmatically. If an area of responsibility has a lot of substantial projects under it, I make it a folder. If it tends to have very simple single actions, I create a single-action project for it. Given your examples, I would choose folders. (You can nest folders, so all of yours could be in a "Work" or "Sysadmin" folder, for ease of organizing and focusing.)