If your task list has 200 items on it, it probably isn’t a task list problem. It’s almost certainly a structure problem. The missing layer is areas of responsibility — the standing commitments in your life that generate projects and tasks indefinitely. Without this layer, tasks pile into a single list with no context, no coverage check, and no way to see which parts of your life are being neglected.
In GTD, David Allen describes areas of focus as the ongoing commitments that exist whether or not you’re working on a project inside them. Business ownership. Health. Family. Finances. Learning. Professional development. These aren’t projects with an end date; they’re permanent areas of your life that need consistent attention. Every project you take on lives inside one of these areas, and every task lives inside a project.
That structure — area → project → task — is the backbone of the Nerd Productivity System and the layer that makes the weekly review useful rather than overwhelming. It’s also the layer most productivity systems skip entirely.
What an area of responsibility actually is
A project is something with an end date and a done state. “Launch the podcast” is a project — it ends when the first episode is live. An area of responsibility has no end date. Running the podcast after launch — the ongoing work of recording, editing, and publishing — is an area. You don’t complete it; you maintain it.
This distinction matters because most people treat areas as if they were projects. They add “health” to their task list, wonder why it sits there undone, and eventually stop trusting the list. Health is never done. It’s a standing commitment that generates different tasks every week — a GP appointment this week, a gym schedule next week, a diet adjustment the week after. Those are tasks. Health is the container that holds them.
When you separate the containers from the contents, your system tells you two things at once: what you’re committed to doing (projects) and what parts of your life you’re committed to maintaining (areas). Both matter. Only one of them gets tracked in most systems.
This distinction also appears in the GTD horizons of focus model, where areas of focus sit at the third horizon — above projects and next actions, below longer-term goals and purpose. That placement is deliberate: areas govern which projects you take on in the first place.
How to define your areas
Most business owners who run this exercise for the first time identify eight to twelve areas. Common ones for a business owner running a small team:
- Business — revenue, client delivery, operations, team
- Marketing — organic, paid, content, social channels
- Finance — cash flow, tax, personal accounts, investments
- Health — exercise, diet, sleep, medical and dental
- Family — relationship with partner, children, extended family
- Home — property, admin, maintenance, household
- Learning — books, courses, skills actively in development
- Personal development — coaching, reflection, long-term thinking
Some of these will merge or split depending on your situation. A sole founder with no team might combine Business and Marketing. Someone with a complex property portfolio might split Finance into two areas. The right number of areas is whichever number reflects your real commitments without being so granular that maintaining the list becomes its own task. Eight to twelve is a practical range.
A useful test: when a new project lands on your desk, can you immediately identify which area it belongs to? If yes, your areas are well-defined. If you find yourself hesitating, or creating a new area for every significant project, your definitions are too narrow. A miscellaneous area is a signal to review whether those items actually belong in existing areas or whether there’s a genuine standing commitment you haven’t named yet.
Organising projects and tasks under areas
Once your areas are named, every project in your system maps to one of them. “Redesign the website” sits under Marketing. “Book dentist appointment” sits under Health. “File Q3 accounts” sits under Finance. Nothing floats at the top level without a home.
This matters for two reasons. First, when you open your system on a Monday morning, you can see the full scope of what you’ve committed to across every area — not just whichever projects shouted loudest last week. Second, when something feels off — when the business is moving but home feels neglected, or when health has had no attention for three weeks — the area view surfaces it without you having to diagnose the feeling yourself.
In the Nerd Productivity System, areas are set up as top-level sections in Asana, with projects nested under each area. Each project carries a done-state sentence and at least one next action, following the principles in GTD project planning. Tasks flow from projects, not directly into the area — which keeps the structure clean and the weekly review scannable rather than exhausting.
The area layer also changes how you process incoming tasks. When something lands in your capture inbox, the first question during processing isn’t “what do I do with this?” It’s “which area does this belong to, and is there already a project for it?” That sequence stops you from creating one-off tasks that live nowhere and gradually drain trust in the system.
The weekly review by area
The most useful thing about organising by area is what it does to the weekly review. Instead of scanning a flat list of everything and trying to spot what’s being neglected, you move through each area in sequence.
The check for each area is simple: are the live projects current, does each project have a next action, and is this area getting appropriate attention relative to its importance this week? A project in the Business area that’s been stalled for three weeks with no next action is immediately visible. An area like Learning that’s had no active projects for a month is immediately visible. The coverage problem names itself; you don’t have to hunt for it.
This structured sweep takes fifteen to twenty minutes. It ends with weekly Rocks — two or three projects across all areas that get protected time this week. The area structure makes the Rock selection deliberate rather than reactive: you can see every area, every live project, and every stalled project at once, and choose from the full picture rather than from whatever is currently loudest.
Where this sits in the NP System
In the Nerd Productivity System, areas of responsibility are part of the Process phase — specifically Habit 5: organise by area and context. After you’ve captured your inputs (Habit 1), filtered noise (Habit 2), triaged with the 5Ds (Habit 3), and applied the 2-minute rule (Habit 4), you organise what remains into the right area and project. That’s the last processing step before planning begins.
The system builds from here. Once your areas are current and your projects have next actions, the Plan phase becomes straightforward: identify your opportunities versus problems across the week, apply the Eisenhower matrix to prioritise across areas, and set your Rocks for the week. Without the areas layer, the Plan phase is a scramble. With it, it’s a scan.
The change most business owners notice first when they add this layer isn’t a productivity gain — it’s a relief. The sense that the whole system is covering everything, not just the projects that are currently active and loud. Business owners who feel perpetually behind despite staying busy are almost always missing this layer. They have tasks and projects, but no structure that maps their full commitments and checks whether each part of their life is getting the attention it needs.
If you want to see how areas of responsibility fit into the complete Nerd Productivity System — including how they connect to capture, processing, and the weekly review — the free NP System course walks through each phase in sequence. You can also take the productivity quiz to find out which phase of your current system is causing the most friction before you start rebuilding.
