I'm a "project manager," so "project" has a particular meaning for me. I'm trying to clarify the distinctions I need to make at different levels of organization; trying to keep the distinctions meaningful to the "workflow process."
A lot of tasks come to me, beyond the "projects" I am also responsible for; so clearly I need a category that is smaller than what is a "project" for me. As a place-filler I've been using "Projects" (e.g. "remodel community building") and "projects" (GTD-type).
The GTD template from M Lines uses the category "Outcomes" in a way that seems to me to be comparable to "projects" in the book. At one point in the book the term "deliverables" is used -- though there is nothing in the index, so it must not be a part, per se, of the system. Likewise "components" (as parts of a project.)
The long-and-short of it --
I'd appreciate a discussion of the concept of "project" especially in relation to "outcomes," "components (of projects), goals, objectives, deliverables, etc.
P.S. I'm surprised not to see "Define Outcome" in the workflow diagram, though other places in the book that is mentioned as an essential step. Isn't it always "define outcome --> what is the next.