Almost everyone starts with good intentions: a «Work» folder, a «Personal» one, a «Misc» one. A couple of years later «Misc» holds half the disk, there are three folders called «Invoices» in different places, and finding a contract means running a search and hoping you remember a word from its title. The problem is not a lack of order but a lack of criteria. A folder structure works when anyone, including you five years from now, knows where to put a new file without thinking about it.
The principle: few levels, stable categories
The most useful rule I know is this: top-level folders should rarely change. There can be five, seven, at most ten, and they should describe areas of your life or work that will stay valid for years. Beneath them you can create and close subfolders freely.
A second principle concerns depth. Beyond three or four levels the structure becomes a maze: every time you have to open five folders to reach a file, and the temptation to save it «for now» on the desktop becomes irresistible.
A concrete example
Here is a structure I often use as a starting point when I help someone tidy up a computer:
00_Inbox
10_Work
20_Home
30_Finances
40_Health
50_Learning
60_Personal-projects
90_Archive
The numbers in front of the names do two jobs. They force the display order, which would otherwise be alphabetical and arbitrary, and they leave room to insert new categories between existing ones without renumbering everything. If one day you need a «Car» folder, it can become 25_Car and sit between Home and Finances.
The Inbox folder
00_Inbox is the entry point for everything you have not yet classified. It is not a permanent store: it is a transit zone you empty periodically. Having it explicitly is better than pretending to file every document immediately, because in practice nobody does.
The Archive folder
90_Archive holds what is finished but must be kept: completed projects, closed tax years, documents from a house you no longer live in. Moving things to the archive keeps active folders light and quick to browse.
By topic or by year?
This is the question I hear most often. The practical answer is: topic on top, year below. Inside 30_Finances you can have Tax-returns, Bank, Insurance, and inside each of them subfolders by year:
30_Finances/
Tax-returns/
2024/
2025/
Bank/
Statements/
The opposite, years on top and topics beneath, only works for people who operate on very rigid annual cycles. For most people it means duplicating the same structure every year and makes it hard to see the full history of a topic.
Projects and areas: a useful distinction
It pays to separate two kinds of content:
- Areas: ongoing responsibilities with no planned end (home, health, finances).
- Projects: activities with a goal and a conclusion (a renovation, a house move, a website to deliver).
A project lives in its own folder while it is active; when it ends, it moves entirely to the archive. That way the projects folder always shows only what you are working on right now, and it becomes a small visual reminder.
Mistakes to avoid
- «Misc», «Other», «New folder» folders: they are the digital equivalent of the drawer where everything gets thrown. If a file has no home, a category is probably missing, or it belongs in the Inbox.
- Folders containing a single file: creating a subfolder for every document multiplies clicks without adding order. Wait until you have at least three or four similar files.
- Duplicating the structure in several places: if you have an invoices folder on the local disk, one in the cloud and one on a USB stick, you will have three versions of the truth. Choose one main location.
- Overly personal or jokey names: «Marta's stuff» or «Boring things» make sense today, much less in a few years or to whoever has to help you.
How to migrate without getting stuck
Reorganizing years of files in one afternoon is unrealistic. An approach that works:
- Create the new empty structure next to the old one.
- Move all the old content into a folder called
90_Archive/Old-mess. - From today, save new files only in the new structure.
- When you need an old file, look for it in the archive and, while you are there, move it to the right place.
After a few months the files you actually use will have migrated by themselves, and what remains in the old mess is material you rarely consult. You can tidy it up calmly or leave it where it is.
Document the structure
A small text file at the root, for example README.txt, listing the main folders with one line on what each contains, seems superfluous until you need it: when you share the computer with a family member, when someone has to find a document on your behalf, or when you yourself are unsure where a certain category of file belongs.
In short
- Use a few stable top-level folders, numbered to control their order.
- Limit depth to three or four levels and put topic above year.
- Keep an Inbox for unclassified items and an Archive for finished ones.
- Separate ongoing areas from projects that have an end.
- Migrate gradually instead of reorganizing everything at once.