JD in a team: IDs in filenames instead of a mirrored folder tree?

Hey there!

JD works beautifully for one person: one tree, one owner, one mental model. I’m trying to make it work for a small team, and the tidy tree keeps running into three realities:

  1. Several storage platforms (Google Drive shared drives, a Nextcloud, local folders and a wiki).
  2. Permissions. Access is granted per shared drive/folder, not per area or category. A mirrored JD tree has to serve two masters: meaning and access.
  3. Personal systems. Everyone already has their own folder logic and won’t reorganise it.

Our first approach was a JD index in a wiki plus an identical tree in Drive. It stalled on point 2.

The idea now: decouple classification from location. People keep their folders. The ID becomes mandatory at the start of every filename. The wiki turns into a file plan: it defines what each ID means, and each ID page carries a search link instead of a folder link. The ID travels with the file across platforms, downloads and email attachments.

Trade-offs I see:

  • No browsable structure in storage. Lookup becomes a separate step.
  • Search precision: MM.YY at the beginning of a filename will make it harder to separate it. E.g. 09.23 Tax evation
  • Erosion: a missing ID is invisible. An empty folder at least shows the gap.
  • Granularity: JD IDs are collections, not single files. Per-file IDs add friction.
  • Standard zeros: .01 still works as a prefix (“category clear, ID open”), but archive is a status, not a class.

Questions:

  1. Has anyone run JD with IDs in filenames instead of, or alongside, a mirrored tree in a team? How did it hold up over time?
  2. How do you align JD with the permission boundaries of your storage?
  3. Which ID format searches reliably across Drive, Nextcloud, Explorer and Finder?
  4. Colleagues’ personal systems: integrate, tolerate or replace?
  5. Is losing the browsable tree a dealbreaker, or can a good index make up for it?

Curious about your experiences, including “don’t do this”.

With best regards

Bruno

An interesting challenge.

I definitely endorse ID-in-filename in some situations. This one feels sensible. But a lot else makes me uncomfortable.

Unless you have individuals working on a closed set of files, how are you going to prevent conflicts/clashes? If Alice and Bob don’t share a filesystem but they both need to work on A01.11.11 Important.doc, how do you ensure they don’t update it simultaneously? Where is the master version?

And then how are you working together? Don’t tell me you’re emailing files?

So on the surface, my instinct says “just get a Dropbox and tell everyone to use it”. But presumably there are good reasons you’re not doing that.

Otherwise I’d say ID-at-start, yeah.

Would love more info! A curious problem.


Update: one of the guys on Discord told us about their situation at work, where in a company of ~700 people, management refuse to make a decision on whether everyone uses Google or Microsoft for document storage. Because they don’t want to offend some people who prefer one or the other.

The result is this mish-mash that everyone hates! My contact said that they “just wish management would have the guts to make a decision”.

Maybe someone here just needs to make a decision. The team needs to be told: team files are here.