Some things on your list end. Most of what you carry does not. Your health, your home, the money side of your life, the part of your work nobody assigned you but everybody counts on. None of that gets finished. It gets kept.
A list of projects tells you what is running. It does not tell you whether the right things are running. You can have a full, tidy, honest project list and still notice that an area you care about has been quiet for months, because nothing on a list ever raises its hand to say it is missing.
An area of focus is one responsibility you carry, held in one place: a short piece of prose saying what maintained looks like here, the projects filed under it, and the reference material you keep for it. Open an area, and the responsibility and the work sit in the same view.
A project has an end: you reach the outcome and close it. A context is where a step gets done, the place and the tools it needs. An area is neither. It is what you are responsible for, it never finishes, and it is what your projects are for.
What you get
- A read on every responsibility you carry, with its projects grouped by status on one card.
- Your own words for what maintained looks like in an area, kept somewhere you read them again.
- Projects filed under every area they serve, so a renovation can be a home matter and a money matter at once.
- A home for the reference material that belongs to a responsibility rather than to one project.
- Fast filing while you capture, using the
:prefix.
How it works
- Create an area, then type
:areanamein the next bar to open it, or to create it on the spot. - File a project into an area from the project's settings, and into a second area whenever the work serves both.
- Write the area's standard in its description, and file a note there with
:areawhile you capture it. Notes only: actions stay in projects and next actions. - Filter the projects page by area to look at one responsibility at a time. That filter is a view, so it is gone after a reload and cannot quietly hide your work.
Why it matters
- Projects are not the top of the system. They serve the responsibilities you carry, and those are worth writing down where you can look at them.
- Work that goes missing rarely announces itself. A project you never started sends no signal, and reading your own standard for an area is how you notice.
- Areas are optional structure. No next action disappears because its project has no area, so you can file the projects where the grouping earns its keep and leave the rest alone.
Asking what is missing
The areas review is a mode of its own, started when you want it rather than as a step you sit through. It walks your areas and asks one question: is anything missing here. You read the standard you wrote, you see the projects running under it, and if something is missing you can start a project right there, or file one that has been floating around unfiled. A second step offers the active projects that sit in no area, where leaving one unfiled is a real answer and not a gap to close.
The weekly review keeps the system trustworthy: inbox cleared, every project with a next action. The areas review keeps it aimed: is the work you have running still the work your responsibilities need. Different question, different rhythm, so the two stay separate, and an areas review never stands in for your weekly one.