A place for "communication structures"

Hi,

we have a document describing our company communication structures. It lists all the stuff we use, how and where to login, touching email, chat and other resources. Furthermore it contains notes and pointers on how to get things going on a desktop (operating system a, b, c) or on a smartphone like apps to install, configuration settings to make and so on.

It is structured like this (a bit trimmed down):

1. Authentication / Authorization
  1. 2FA etc.
  2. SSO
  3. resources not working via SSO
2. Chat
  1. ...
3. E-Mail
  1. Recommended clients
  2. Smartphone clients and setup
  3. Encryption of E-Mail
4. Adresses
  1. Setting up sync (CardDAV) and software
5. Calendar
  1. Setting up sync (CalDAV) and software
6. GnuPG
  1. Configuration
  2. Key handling
  3. Guidelines

My first impulse was to file it to 14.31 but serveral things we use (email provider et.al.) would belong at 14.32 as I understand. However general feedback and also my thoughts are that it provides a thorough overview and getting started, therefore I’m hesitating to split it apart. I also thought of ā€œ14.02 ops manualsā€ but likely I’m just overthinking things?

Any thoughts on that?

Kind regards,

This does feel like an internal ops manual. If it didn’t yet exist and you wanted to put it together, I might be telling you to put those things in places where they ā€˜belong’. But it does exist, and splitting it up would be confusing.

I would say, 14.02+OPSx <Title> but then it also feels worthwhile leaving yourself breadcrumbs in the ā€˜other’ places that you might look for this knowledge.

Here’s a thought about JDex notes that I’ll formalise shortly. I’m starting to feel – especially in the pre-built systems – that the main note should never contain ā€˜content’. It should serve purely as an index note. And if you need to write ā€˜a note’, make that a + note and link to it from the main note. This link being mandatory. That make sense?

Thanks for your thoughts. I’m currently also on the ā€œ14.02 trackā€

Regarding the + notation: we use it [too] seldom. In most cases if we have ā€œ.02 ops manualsā€ for example, we create properly named notes / documents directly in that folder.
But I do see the appeal of having that one ā€œcleanā€ and + ones for quicker access / finding via browsing. I’ll monitor how this is evolving and bring feedback.

Kind regards,

1 Like