Hi all!
I’m new to the forum and to creating my JD system, and have a question I’d love help with before I dive in too deep!
I am a consultant who works with a few, very large clients at a time. Each client has project areas, and within these areas are multiple projects and workstreams.
The only way I can get a reasonably shallow structure, is by having the client at the highest level.
Client A
----Area 1
--------Project 1
--------Project 2
----Area 2
--------Project 1
--------Project 2
Using JD would be something like
00-09 System
10-19 Client A
----11 Area 1
--------11.01 Project 1
------------File 1
------------File 2
--------11.02 Project 2
------------File 1
------------File 2
This gives me 99 projects for each client, which I think is sufficient.
BUT I want this system to last a long time, and over the years, I will have different clients. With the above system, I would archive 10-19 Client A, and then create a new group called 10-19 Client H.
Is this sensible?
Over a longer time, my archive will have 10-19 Client A, 10-19 Client H, etc.
Is this a problem? I’m unlikely to need to access the files from that area often (if I solve a problem for Client H that is similar to Client A, then I’d need to find it).
How would you recommend I organise myself to navigate this, or if the same as me, some reassurance would be wonderful! I don’t want to find out in 6 months that my system is a nightmare because of setup mistakes!
@johnnydecimal’s example on his site uses this as the current system, but once you have more than 10 clients (which you might over your career), what do you do?