Lucas Brenner » Articles » How to Create an Efficient File System



There are an infinite number of different formats online for naming your files. However, most of these systems are complex and time-consuming. That doesn't have to be the case!

Naming and saving files should be as simple and quick as possible so that you can get on with the really important tasks. After asking myself some basic questions, I was able to develop a simple system that I will present in this article.[1]

Why Do We Name Files?

This fundamental question puts its finger on the goal of all file systems: We name files and create folders so that we can easily find our files later.

In the age of AIs and search algorithms, it may seem tempting to simply save the files without a system and find them again later using the search function. This may work, but this approach has two disadvantages. Firstly, you lose the opportunity to find cross-references (for example, between files in the same folder or context that remind you of other tasks or ideas) and secondly, the organization of your own files in folders reflects to some extent the organization of your own thoughts and ideas in your head.

On the other hand, no one wants to spend hours categorizing files. It's not worth the time and the mental energy would be better invested elsewhere.

In summary, the goal is to find your files quickly without having to invest too much effort in organizing them. In economic terms, we want to invest a little time in the file structure and save a lot of time searching later.

Basic Principles of File Organization

Before I introduce my file system, there are three basic principles that you need to follow in order for file organization to have any effect at all. If you apply anything from this article in your life, it should be these three basic rules.

  1. You must name files and folders correctly immediately. It is okay to rename something later, of course, but you should never put off the correct naming.
  2. You must save files immediately in the correct folder, not on the desktop or in the Downloads folder. Anything else will slowly undermine your file organization.
  3. Your file system should not have too many folders or layers, otherwise it will become too complicated. I usually limit myself to three folder levels.

My File System

The First Folder Level

There are only five folders on the first level of my file system, which are based on Tiago Forte's PARA Method:

Limiting the number of folders on each level helps to keep things clear and forces me to limit myself to the really important projects etc. These restrictions can be extended or removed as required.

Further Folder Levels

The five folders on the first level are structured differently, but the names of the nested folders are always the same:

Limiting the folders to one level helps to keep things clear and forces me to limit myself to the really important projects etc. These restrictions can be extended or removed as required.

The advantage of naming folders is that you can see where you are in the file tree at each level. If you remember the numbers of the projects or areas, you can also navigate between them more quickly and name them as a reference in other areas, for example in emails. This is particularly useful when sharing a cloud file system with other people.

My File Naming

The naming of the files themselves is not so strictly regulated in my case. The advantage of strict folder naming is that I will probably be able to find the files quickly. Nonetheless, I still have a file naming convention so that I don't have to open all the files in a folder to find something specific, and so that I can use the search function, if necessary. I name my files with a title that is as concise as possible and that contains important keywords. For example, a project report should have the phrase “project report” in the title.

I also prefix some files with a date. This applies in particular to invoices and time-sensitive files, of which there are several in a given project. Depending on the file, the date prefix may look like this:


With this simple system, you should be able to find all your files quickly and efficiently. The initial setup of the system also doesn't take long with a simple trick: Move all your current files to a folder in the archive and only sort the files into the new folder structure that you are currently actively working on. There's a good chance that you will only rarely need the old files and can sort them later or simply not at all. You also don't have to create a complete file system with lots of empty folders straight away, but can let the system grow dynamically as you work.

In addition to the naming conventions, it is important to adhere to the three basic rules of file organization so that your system does not require too much maintenance. If you follow these rules, you will always have a clean and functional file system that you can work with efficiently.



Footnotes

[1] The system is based on Tiago Forte's PARA Method and the Johnny.Decimal technique and combines the advantages of these two approaches.