This is a methodology for managing business procedures and factual references for a company.
Business Reference
├── complex checklists
│ ├── aComplexChecklist.md
│ ├── anotherComplexChecklist.md
│ └── complicated checklists
│ ├── aComplicatedChecklist.md
│ ├── anotherComplicatedChecklist.md
│ └── simple checklists
│ ├── aSimpleChecklist.md
│ ├── anotherSimpleChecklist.md
│ └── atomic references
│ ├── anAtomicReference.md
│ └── anotherAtomicReference.md
└── README.md #this file- An Atomic Reference: This is the lowest level file. It contains a factual reference, that is also atomic 1.
- A Simple Checklist: A simple checklist is the simplest type of checklist. Can only reference atomic references.
- A Complicated Checklist: A complicated checklist is the second level of checklists. These checklists can reference both atomic references and simple checklists. Simple checklists can be steps themselves in a complicated checklist.
- A Complex Checklist: A complex checklist is the highest level of checklists. These checklist can reference atomic references, simple checklists, and complicated checklists.
- You can link down, not up. (e.g. a complicated checklist can have links within to simple checklists and atomic references but not to complex checklists)
- All checklists must only be have a number of steps equivalent to human working memory (5-7 steps)
- If this lives in the same vault as your own PARA or Zettelkasten, never link to actual links in your PARA or Zettelkasten unless they’re publicly available on the web. Otherwise, it is no longer a delgatable, stand alone system. I see no reason why your PARA or Zettelkasten can’t link to notes in this though.
How tagging is done should be based on your organizational structure. But in most organizations, tagging would be done by departments. #finance, #sales, #marketing, #operations, etc.