# Timeline System The main idea of the system is to use folders, or Containers of Information, as spaces that convey the status of the activities. From a structural standpoint, there are three parent folders, representing the three types of Containers. Within them, the sub-folders that hold all the information related to a particular topic are the ones that are moved from one parent folder to another when the activity status changes. ##### Action Containers This is where the work is happening. Anything in progress stays there in its specific sub-folder until it is done.  ##### Static Containers For resources like personal documents, a knowledge base, and anything that supports our activities, but not necessarily the work in progress inside the Action Containers. It can also be something random and unrelated. For example, having to provide your passport number when filling out a form during a trip. ##### Timeline To where all the sub-folders are moved to when the activity they represent is done. It ranges from clients to expired documents. In a way, it is an archive, but it also serves as a long-term resource. For example, if an old client needs more sessions, moving his container (sub-folder) to the Action Containers shows that the client is in progress again. But if all that is needed is to look at some historical information, just open the sub-folder inside the Timeline, take a look at the records, and that's it. #### What is the Timeline System and how to use it ![](https://youtu.be/RYCjrFFwvG8) #### How it came to be Remember the last time you spent hours searching for an important document or email? I've been there, too. I know how the frustration of 'not finding' can negatively impact our daily activities. Many years ago, motivated by a lifelong passion for organization, I embarked on a quest to create a system in line with what, I thought, would be enough to make the system straightforward to adopt and use. It should have as fewer ceremonies as possible to set up and use it, and it had to be as natural as possible to adopt and maintain. As you can probably imagine, that's easier said than done. The first reality shock I experienced happened when I started working for big corporations and realized how much of a problem it was not to have a good system for organizing information and activities. However, after trying many existing solutions, it quickly became clear to me that they often felt rigid and unnatural, forcing users to adapt to the system rather than the other way around. That frequently led to frustration, which in turn meant the team would slowly abandon the plan. But I didn’t give up. There had to be a better approach. Perhaps something more in tune with human behaviors. I chose that path, but it would still take several years to find the right solution. In reality, I spent so much energy trying to make this work that it became my job. Until these days, I still dedicate a fair amount of time listening to how the person does things before coming up with a solution. I then try to build a workflow and adopt software or any technologies that better match how the person does their work. Experience tells me that this approach means more time and effort put into building the system, but it also means it will be a long-term solution. Helping people resulted in a lot of feedback, which in turn led to the perfecting of the system. It was only over a decade of this feedback loop, that I begone to realize that basing the system principles and mechanisms on how people naturally think and do things was the correct decision. I don't claim to have found perfection because, in a way, it's physically impossible. As <a href="https://en.wikipedia.org/wiki/Rudolf_Clausius" target="_blank">Rudolf Clausius</a> puts it, “*The entropy of the universe tends to a maximum*”. To what I add, "*So does the entropy of your notes. It's okay to not obsess over a perfect system, as it may be a waste of your time. Remember that you cannot predict everything, and variables are forever changing.*" It now feels like all this journey has to be converted into a book. But although all these ideas have been in my head for so many years, it doesn't make it an easy task to organize everything in a comprehensible way. It will take a while to finish, but rest assured that the Timeline System is being documented. For now, you can read or watch me talking about it, filtering the posts with the #TLS tag. Or, if you wish to support me, you can do it on [Patreon](https://patreon.com/vladcampos) to take a closer look at the progress of this project and access many other exclusive content I share with members. #### Tasks and the Timeline System ![](https://youtu.be/3Q0aR7f98fQ) #### Using the Timeline System in Evernote ![](https://youtu.be/GNIpIxZzQMA) #### Using the Timeline System in Obsidian ![](https://youtu.be/SR8ZX7kkAXo) #### Using the Timeline System in the Supernote ![](https://youtu.be/ybr86fUCgqY)