Many users like to separate their work from their private affairs. One way to do that to some extent in Doit is to use the Goal feature.

Technically speaking, the Goal feature is just an additional hierarchical level above projects, allowing you to keep your projects grouped together in whatever way suits you, for example into a Work "area" and a Private "area".

The functionality surrounding Goals in Doit is not very impressive. All you get is a section of the left menu called Goals by which you can access your projects more easily than finding them in the long Projects list. But it is better than nothing. It allows me to keep the long Projects section of the left menu collapsed most of the time, and only the Goals section open.

I have split my "life" into 5 sectors (Goals), each one of them containing a bunch of projects, which in turn contain tasks. My "Goals" are:

- a private "area"
- a not-for-profit "area"
- a general business "area"
- a major business development venture
- a second major business development venture

Only the last two are true goals in the GTD sense - where a goal (30 k ft) is a major concrete objective, a "super-project" that will hopefully be completed and successful in a couple of years.

The first three "goals" are not true goals that will ever be completed. They are of a more permanent nature, but I have still chosen to use the Goal feature for it, because it gives me overview and structure and is perfectly in line with GTD (aside from the name "goal") . Each of these three "goals" of mine actually represents an entire group of what GTD calls Areas of Responsibility (AoR). I have defined 10 AoRs for myself. Typical numbers are 10-20.

Under each Goal I have a set of projects that belong to that Goal or will help bring it about. Most of my projects are true regular projects that will be finished sooner or later, but a few of them, 10 all in all, serve as more permanent AoR buckets where I collect small tasks that do not belong to the other projects and are too small to justify a project of their own.

All in all, I very much like and recommend this combined use of Goals and Projects for both "true" projects & objectives and for "areas" (single AoRs and entire groups of AoRs).