<aside> <img src="/icons/light-bulb_gray.svg" alt="/icons/light-bulb_gray.svg" width="40px" /> Notes are atomic Each note should hold a single bit of information. It could be a paragraph or a couple of sentences. The point is to have, as nearly as possible, just one thought per note.
</aside>
<aside> <img src="/icons/home_gray.svg" alt="/icons/home_gray.svg" width="40px" /> Each Note Has a Home Every note has a distinct home in the filing system, so you can easily find it when needed. Luhmann didn’t believe in arranging his notes topically because that could limit a note’s usefulness. A guinea pig — is it a pet, an experiment or food? Once you start thinking of a guinea pig in one context, it’s hard to see it in any other.
</aside>
<aside> <img src="/icons/link_gray.svg" alt="/icons/link_gray.svg" width="40px" /> Notes Link to Other Notes For example, a note about a science experiment could link to a note about guinea pigs. In this respect, Luhmann’s note-taking system resembled. Relations to notes are one-way
</aside>
<aside> <img src="/icons/tag_gray.svg" alt="/icons/tag_gray.svg" width="40px" /> Cross Reference Keywords (tag) Luhmann kept a cross-reference guide to important keywords from each of his notes. This way, if he wanted to find information about “pets”, he could look at the reference sheet and find IDs for all his notes related to pets. And that’s about it. See for this
</aside>
This template combines an inspiration journal (or resonance calendar, commonplace book) and a zettelkasten note-taking approach. It is enriched with 6 additional dashboards that help you get the most out of it.
<aside> <img src="/icons/thought-alert_gray.svg" alt="/icons/thought-alert_gray.svg" width="40px" /> Tags should be easy to remember since there is a limited number of actions you take with your notes, you have only a small number of options to remember
</aside>
<aside> <img src="/icons/circle-arrows-horizontal_gray.svg" alt="/icons/circle-arrows-horizontal_gray.svg" width="40px" /> Tags should be easy to decide on it is usually easier to decide how a note is going to be used, rather than what it means or what it’s about
</aside>
<aside> <img src="/icons/wall_gray.svg" alt="/icons/wall_gray.svg" width="40px" /> Tags should be concrete tagging according what it is far more concrete than theoretical categories or what it means
</aside>
<aside> <img src="/icons/peace_gray.svg" alt="/icons/peace_gray.svg" width="40px" /> Tags should be forgiving by maintaining tags as a supplement to a hierarchical organisational system, we reap most of their benefits without having to adhere to them perfectly
</aside>
<aside> <img src="/icons/directions_gray.svg" alt="/icons/directions_gray.svg" width="40px" /> Tags should enable the right behaviors in this case, using tags to manage the stages of a workflow enables the productive use of knowledge, instead of mere cataloguing
</aside>
<aside> <img src="https://prod-files-secure.s3.us-west-2.amazonaws.com/904d01b0-6d90-42d1-b9d2-512549009d82/403fb160-e36d-4467-8645-51ac08f85c81/Rick_Mans_LinkedIn.jpeg" alt="https://prod-files-secure.s3.us-west-2.amazonaws.com/904d01b0-6d90-42d1-b9d2-512549009d82/403fb160-e36d-4467-8645-51ac08f85c81/Rick_Mans_LinkedIn.jpeg" width="40px" /> This template was made by Rick Mans.
If you want to have more templates, you can check out Gumroad or connect with me on LinkedIn.
</aside>
No Notion account yet? Sign up here, and it will also help me create more templates.
