A big hello to all of you,
I am a big fan of order and structure and write down lots of things in Obsidian, both privately and at work. But what always been kinda messy was my directory structure. Fortunately, I discovered the Johnny Decimal system and successfully introduced it into my work environment. I have been using it for a good year now - but now I have to adapt my system due to restructuring in the company.
Our company likes to think in roles and teams and many of us employees have several roles in different teams. What first worked with areas and categories now needs to be adjusted 'cause I got more additional activities in the company.
My first and initial approach was like this:
10-19 Role1
11 Organisation
11.01 Correspondence
11.02 Planning
11.03 Notes
12 Projects
12.01 Project1
12.02 Project2
20-29 Role2
21 Organisation
21.01 Correspondence
21.02 Planning
21.03 Notes
22 Team1
22.01 Correspondence
22.02 Planning
22.03 Notes
23 Team2
22.01 Correspondence
22.02 Planning
I donāt know why I canāt format the part above (preformatted text) correctly?
Thoughts/Issues
As you can see I had several problems over time, which are:
- In Role1 I have several projects which is fine to map 'cause I have a lot of IDs available as sub-folders. Nevertheless, I can no longer divide any project into sub-folders like
Planning
etc., because I no longer have any levels available.
What I could do is to have sub-folders like- 01 Correspondence
- 02 Planning
- ā¦
- In Role2, in which I am responsible for different teams, I do not have the possibility to have the
Organisation
category, since the category is already used as team name .
So my next approach are systems:
T22 Role1 Team1
T22.10-19 Organisation
T22.11 Correspondence
T22.12 Planning
T22.13 Notes
T22.20-29 Team
T22.21 Meetings
T22.22.01 Meeting1
T22.30-49 Projects
T22.31 Project1
T22.31.10 --- Organisation
T22.31.11 Correspondence
T22.31.12 Planning
T22.31.13 Notes
T22.31.91 --- Knowledge
Specific Knowledge Item ???
T22.31.92 Tools ???
or
T22.31.92 --- Tools ???
T22.90-99 Resources
T22.91 Knowledge
T22.91.01 Item1
T22.91.02 Item2
T22.92 Tools
T22.93 Assets
T22.93.01 Icons
T22.93.02 Symbols
T22.92.03 Fonts
Thoughts/Issues
- I thought it would be a good idea to structure the ideas into separate groups. By that,
Correspondence
would always get an ID of 11 - I have expanded the project range from 30-39 to 30-49 to have enough room for upcoming projects.
- The main problem is the ID for Knowledge T22.31.91. I am not able subdivide the knowledge gained for a specific project into more sub-folders.
- Also I have no idea where I should put tools for a specific project.
In addition, there are roles that I perform for the entire company and not specifically for a team.
So I thought I make a separate system for all roles that have no connection to a specific team.
N22 Other roles
N22.11 Other role 1
N22.11.10 --- Organisation
N22.11.11 Correspondence
N22.11.12 Planning
N22.11.13 Notes
N22.12.30 --- Projects
N22.11.90 --- Resources
N22.12 Other role 2
N22.12.10 --- Organisation
N22.12.11 Correspondence
N22.12.12 Planning
N22.12.13 Notes
N22.12.30 --- Projects
N22.12.91 --- Knowledge
Thoughts/Issues
- I thought that I omit the areas in that case, since every role that I have or will have in the future is just a single category. No special sorting - if I get a new role that role will get the next free number/category. Thatās all.
- The IDs of each role are again structured in groups. So, for instance,
Correspondece
always gets an ID of 11 in every different role. - The Problem is once again that there is no room (IDs i.e. sub-folders) left for any of the IDs like
Correspondece
,Planning
, etc.
So, just to sum it up. No matter which direction I think I always come to a point where something does not feel right or is impractical.
I would love to hear your thoughts on my approach - your help is much appreciated!
A great day and weekend to all of you and many greetings,
Mike