kimpa.work

Data Organization Skills

Those who have the ability to arrange and organize Data files neatly and methodically often achieve greater results than others. Quite simply, when everything is structured and kept in order, you don't burn precious energy and time hunting down what you need, allowing you to focus deeply on what truly matters.

It is safe to say that one of the single habits that accelerates our career success is organizing and structuring our work-related files. As our work landscape advances, the volume of data generated for each project keeps expanding. If we don't know how to organize and arrange files sensibly, finding the right document at the critical moment becomes a major headache.

crazy-dog-finding-his-file-in-messy-folder

In this post, I will share the exact way I organize my daily Data.

1. Group all project files into dedicated folders

I have seen countless people carelessly scatter files across any accessible corner of their computer. Whenever they create (or download) a new file, they habitually dump it in the quickest place they can find—especially the Desktop or Downloads folder.

messy-desktop

Many people leave their entire Desktop completely covered in icons

Sure, this shortcut might help them quickly spot what they need early on when there are only a few files. However, as projects expand and more files accumulate, they end up wasting enormous amounts of time searching for the file they need.

Therefore, to avoid wasting time later digging through endless documents, all files belonging to a single project go into their own folder, named following this convention:

📂 YYYY-MM-project-name

Where:

For example:

If data is organized this way, you immediately know where to look for the "ABC system user guide" , right?

2. Manage files within project folders

Once related data files are consolidated into one folder, I structure the contents further according to the nature of the project.

a. Create a project overview note (Summary File)

To avoid wasting time when reviewing a project later—especially long after it has wrapped up and details have faded from memory—I always create an overview note (Summary File) inside each project folder. This records essentials such as what the project is, how long it runs, what tasks it involves, etc.

My Summary File has 3 key characteristics:

For example:

b. Create subfolders to organize data by project traits

A single project contains a wide variety of files. To streamline search and workflow, I group these files into subfolders tailored to how the project unfolds.

Typically, I split project data in one of two ways:

c. Name files following a standard convention

Naturally, each person and profession has their own file-naming style that fits how they work. Nevertheless, I believe that across every industry, adopting a systematic naming convention makes retrieving files much easier when needed.

Personally, I name my data files adopting the Semantic Versioning principles from software engineering, as follows:

📄 YYYY-MM-DD-author-filename_vMajor.Minor.Patch

Where:


For example, instead of naming a file like 📄 partner-contract.docx , I name it as follows:


However, when full semantic versioning isn't necessary, I also use this simplified shorthand convention:

📄 YYYY-MM-DD-author-filename-version

For example:

Naming files and folders like this keeps context crystal clear while making version management effortless.

3. Separate completed and active projects into two main folders

For ongoing work (active projects), I place them in a folder that is quick to access (usually Documents). For finished work (completed projects), I store them in a dedicated archive folder (Archive).

Thus, whenever a project finishes, I simply move its folder from Documents to Archive to mark it as complete (preventing clutter among ongoing projects in Documents). Later on, if I need to look up details about a past project, I can easily find it inside the Archive folder.

Additionally, for those who juggle projects across multiple clients or companies like me, create subfolders for each company. For instance, if I work with Capybara and Hamster, I create Capybara and Hamster subfolders under both Documents and Archive to organize current and concluded projects separately.

Bottom lines

After restructuring my personal Data, my computer is no longer littered with files strewn all over the place. Instead, everything is organized neatly like this ( click on the icons below to explore details ):

That is the entire system I use on a daily basis to organize my Data.

I believe everyone should design an organization system that suits them best. In the short term, structuring your files requires deliberate effort, but in the long run, it saves you huge amounts of time—especially when handling multiple projects simultaneously.

crazy-dog-finding-his-file

"Tidy files, tidy mind!"

Thank you for reading my article!

Kim,