I'm a web dev implementing GTD in Omnifocus. I have some customers that have very neat lines around their work. A single website, a single project, with a defined "complete" state. I have at least one customer, however, where the lines are very muddy around the whole project. I mean, technically the project is "build CRM system", but every time we finish one section of it another pops up. And sometimes there are, literally, dozens of individual tasks related to this project. So categorizing those as @Computer results in a *HUGE* list of tasks, and it drowns out the other stuff that might actually be more important at any given time. Although it's important to know that they *ARE* all @Computer actions. Almost nothing for this customer would ever be on any other list. Each of these items *are* atomic next actions (and not short next-actions - usually they're 30-120 minutes each), so they need to be tracked as such *somewhere*. And marking them off when done gives me some measure of satisfaction. So I'm thinking one of two things.... (1) Use different tracking software for the projects, and use GTD to just hold placeholders reminding me that the entire *project* is @Computer. This adds additional complexity that I'm not a fan of, but I'd be interested if anybody has a positive experience and/or recommendations for going this route. (2) Keep all the tasks/actions in GTD, and just have a @Computer item that links to the internal OmniFocus project list. Thoughts?