Working with folders only (and what it costs)

What matters here

• Folders answer where a thing lives, not when it matters
• Nesting deep enough makes items hard to find again
• A file can only be in one folder at a time
• Open work becomes invisible once it is filed
• Dates, owners and status have to be tracked somewhere else

Where folders genuinely win

Reference material behaves well in folders. Contracts, receipts, exported reports and finished documents rarely change, and a stable place to put them is what you want. The trouble starts when the same structure is used for work that is still moving.

The visibility problem

Once a task lives inside three nested folders, seeing it requires remembering the path. Anything you cannot see tends to be forgotten, which is why folder-only systems produce a long tail of half-finished work that nobody actively decided to postpone.

A workable split

Keep folders for things that are done and stable, and keep open work in a list with dates, status and tags. The two systems do different jobs, and mixing them is what makes a folder tree feel like a maze.

Frequently asked questions

Keep reading

• Running your life from a book of listsA notebook of lists is flexible, portable and forgiving. It is also the source of the classic problem: the same item written on four different pages.
• A to-do app with no recurring tasksWithout recurrence you either retype the same chores forever or stop tracking them. Both outcomes are common and both are avoidable.
• What is the difference between a list and a tag?A list is a container. A tag is a label. An item is in one list and can carry many tags, which is the whole reason both exist.