Described in Building a Second Brain.

Summary

Chuck everything into one of a few active folders while it's useful, then archive each project along with its resources once it's done.

Theoretically, you'll later come back and harvest this ever-increasing archive for each new project.

Background

Tiago found that his existing methods of knowledge-management were too cumbersome, and noticed that he kept falling back to just chucking all resources for a project into a single folder for that project.

He later refined and formalised it a little; this is the result.

Methodology

Projects

Specific objectives you're working toward.

Areas

Broader, more general kind of thing that you work with on an ongoing basis, e.g. health, finance or knowledge-management.

There may be a standard of execution that you want to maintain and possibly improve over time.

Resources

Artifacts that may prove useful later. Or may even be useful now, in either of the above sections.

This is where a system such as Restagraph can mesh neatly with a methodology like this.

Archive

The dead-zone for projects, and all their associated resources.

My critique

Cons

It's a promising start, but limited by the old-school hierarchical thinking that an idea or resource can only ever belong in one box at a time.

Projects and Areas look like useful organisational elements, but their value could be multiplied by breaking out of the box-at-a-time mentality, and linking resources to as many of each as are applicable. Moving to a promiscuously-linked model, it becomes possible for Projects and Areas to enrich each other.

Now link those things to Topics and their ilk, and we can much more easily look up resources that have already proven useful in similar projects.

The Archive section reads more like a dead-zone to me, creating an ever-growing unsorted dumping-zone to grovel through for stuff that might be relevant. Increasing effort means decreasing likelihood of following through, so this progressively diminishes the value of any resources that were relegated there. If you instead just mark a project as done, cancelled or on-hold, the archiving function is implemented without removing resources from view.

Pros

If adopted as a system, it can translate neatly across technological implementations.