For years I’ve used a system not dissimilar to PARA but with less rigid structure. Recently I’ve been rereading some of Forte’s material. One of the things that confuse me is why one would put AREAS of responsibility in a task manager separate from PROJECTS as shown in the screenshot below from one of the Forte Labs pages.
What do you put in AREAS in your project manager? If as defined by Forte "A project is “a series of tasks linked to a goal, with a deadline” whereas "An area of responsibility is “a sphere of activity with a standard to be maintained over time”, what would I put in AREAS in a task manager?
For example, in my situation an obvious project would be to “Hire Head of department x on the senior team.” The area would be either HR or Hiring or Personnel. But I don’t see the point of having an AREA completely distinct from projects in a task manager when by definition items in AREA has standards, which do not necessarily have measurable actions with deadlines associated with them.
My tendency, which Forte does not recommend, is to list projects under areas, something like this:
AREA: Personnel
-Project: Hire Head of department x on the senior team
-Project: Complete SLT evaluations
In fact, in Forte’s example he uses Things. In the Things app, it shows the following, where projects are to be grouped into AREAS.
What am I missing in all of this?