Projects Are Not Areas
Distinguish current projects from ongoing areas so workload becomes visible.
If a folder never ends, it is probably an area; if it can be done, it is probably a project. Name the finish line A project needs a visible outcome: submit the budget, onboard the analyst, publish the FAQ, close the audit gap. Without that finish line, your system can only describe activity, not completion. Keep ongoing standards separate Areas hold recurring responsibilities: team health, hiring, finance hygiene, customer operations. They matter, but they do not close. Treating areas like projects creates permanent failure because there is always more to do. Let next actions attach to projects GTD makes projects…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in