Not sure if this is the correct forum for this question, but I am deeply entrenched in helping people learn and apply knowledge quickly. So I have created a breezy course on Zettelkasten (Pardon me for the plug ).
Since the users here are experts in note-taking. I was wondering what were your thoughts on Zettelkasten note-taking method? Is Tinderbox inspired by the same?
Do you prescribe to other frameworks like PARA, LYT (Linking your thinking) etc?
Hey @exist2018, if you search the forum, youāll find a lot on this topic.
As many in the community know Iāve developed a framework I call the 5Cs of Knowledge Management method (collect, curate, create, collaborate, contribute) that was initially inspired by The Tinderbox Way and Zettlekasten.
Since Iāve started my work Iāve found other methods (here is a complete list of what Iāve discovered):
The Tinderbox Way
Zettlekasten
The Outline Method
The Cornell Method (1950s)
Mind Mapping Method
Flow Notes Method
The Sentence Method
Charting Method
Writing on Slides
Zettlekasten
Dialectics of Seeing
Adbudtive Analysis
GTD - getting things done
PARA - projects, areas, resources, archives
LYT - Linking Your Thinking-
MOC - Map of Content
BASB - Build a Second Brain
PKM - Personal Knowledge Management
OODA loop - Observe, Orient, Decide, Act
Iāve also learned that may of these methods can be tracke by ack to: Conrad Gessner (1515-1565), Thomas Harrison (c. 1650), Vincent Placcius (1689), Carl Linnaeus (1767), Johann Jacob Moser (1701-1785), Jan Paul (1794), Hans blumenberg, Georg Chrstoph Lichtenberg, and Arno Schmidt, Walter Kempowski, Friedrich Kitter, Any Warbur.
Iāve also learned, like Wallace vs. Darwin (Wallace and Darwin were working on theories of evolution at the same time, they even collaborated, but Darwin was better funded, more politically aligned, and published first) Walter Benjamin and Niklas Luhmann were both working on similar methods, Walter about 10 years before Luhmann. Walter tragically died.
My take on all of this is that we often confate tools/technology, process, and principles. For example, my daughter is getting ready to go to college. During our college tours, I spoke to a few of her would-be professors. The Design professors lamented how every student wanted to focus on learning the latest software design package and not spend time on the fundamentals of design, i.e. how color, tone, layout, medium, storytelling influence feelings and emotion, or how the digital vs. physical divide (e.g. RGB vs CMYK color management), are universal and independent of process and tools. I think weāre struggling with the same here. We want to find the magic tool, to jump to the end, when it is really principles and processes that matter most, at least in a foundational sense. If you understand the principles and processes you can attempt the available tool at the moment to your needs to get the job done. For example, while a screw driver is not the ideal tool to get the job done, in a pinch you can use it to do just that.
There are a lot of tools out there that people have been toating as the best- roam, obsidian, OmniGraffle, OmniOutliner, Evernote, devonthink, zotero, bookends, Tinderboxā¦the list goes on.
The more and more I learn about personal knowledge management (PKM) the more Iām convinced of one thingāitās personal. There is no one size fits all set of tools, processes, preferences, principles, taxonomies, ontologies, folksonomy,s standards, and protocols that will work for everyone. It is like apple pie. Apple Pie is NOT everyoneās favorite apple pie, but it is the one that researchers say the majority can generally agree on as a āfavoriteā if options are limited. It is also like Yoga, you need to be patient with yourself in any given moment. You may not be able to touch your toes today, you may not ever be able to, but that does not matter. What matters is that youāre doing it, trying it and pushing yourself enough to th edges for growth without pushing yourself to the point of injury.
As Iāve watched people try to implement the Zettlekasten or any number of different methods in Tinderbox, and Iām no different, we try to implement what we think in the moment is the key step to unlock the value. For example, with Zettlekasten many think it is the ZettileID and the creation on the note identification scheme. I too thought this for a while and have since dropped it simply to fall back on $ID and use that in my action code.
Anyway, I can go only. This is a huge topic and worthy of much discussion. In then we will all find our path forward. Iām just thankful that I have this community, that the community has welcomed me in and graced me with the opportunity participate.
Lots of people write about solutions to the problem that Note-writing practices are generally ineffective. The vast majority of that writing fixates on a myopic, ālifehackingā-type frame, focused on answering questions like: āhow should I organize my notes?ā, āwhat kind of journal should I use?ā, āhow can I make it easy to capture snippets of things I read?ā, etc.
Answers to these questions are unsatisfying because the questions are focused on the wrong thing. The goal is not to take notesāthe goal is to think effectively. Better questions are āwhat practices can help me reliably develop insights over time?ā, āhow can I shepherd my attention effectively?ā etc.
Love this Paul. Itās like a lot marketers, If you ask them what theyāre job is theyāll their answer will often resolve around the function they manage - email marketing, SMS marketing, database marketing, rather than ābeing of service and helping those we serve sove X or Y problem or achieve Z goalā.
The quotation from Andy Matuschak vaguely reminds me of what Argyris and Schƶn said about single-loop and double-loop learning. It might be crudely said that single-loop learning is trying to answer the question āAre we doing it right?ā whereas double-loop learning is asking āAre we doing the right thing?ā I think Argyris and Schƶn compared this to a thermostat that shuts off at 24 degrees C, as against a thermostat that asks āIs 24 degrees C the right temperature at which to shut off?ā
@satikusala, given your interests, you might find it interesting to look in particular at the 1982 article listed below, if you donāt already know it.
Cheers, Martin BB.
Argyris, C., & Schƶn, D. A. (1978). Organizational Learning: A Theory of Action Perspective. Addison-Wesley.
Argyris, C. (1982). The Executive Mind and Double-Loop Learning. Oganizational Dynamics, Autumn. https://doi.org/10.1016/0090-2616(82)90002-X
Argyris, C. (1999). On Organizational Learning (2nd ed.). Blackwell Business.
@satikusala Youāre welcome. I also managed to dredge from my unreliable memory the fact that Chapter 6 of the 1999 book was entitled āTeaching smart people how to learnā, which is more pertinent to the original post in this thread than it might appear. I also managed to find a pdf from the article that seems to have been the precursor of that chapter: https://www.safepilots.org/wp-content/uploads/Teaching-Smart-People-How-to-Learn.pdf. I think it would probably be worth your time.
Thanks @satikusala for these interesting comments. They immediately made me reflect on my own note-taking practices, and the reasons for my initial attraction to Tinderbox.
I have to confess that I didnāt know of the Zettelkasten system, but after reading about it I realised that it encompasses much of what I already do, or have done in the past. What I take from your posting, though, and want to comment on are (1) the importance of fundamental principles, as distinct from particular systems and software packages and (2) the myth of a āone size fits allā solution.
Given the second point one might ask if thereās any value in outlining oneās own approach, if itās so individual that itās unlikely to be applicable to anyone elseās situation. That said, if such an account contains even only some elements that others may be able to adapt to their own purposes, then the exercise is justified.
Iāll mention first one method used for my PhD, a study of the literature of the Beat Generation and its social contexts. My aim in this instance was to create databases of fictional and critical references to the concepts and topics I was discussing in my dissertation. Each fictional record, for example, contained the fields Theme, Details, Text and Page Number, Character(s), Location and Comments. At the time I used Bento for the database software, and when that became obsolete I transferred the information to Tap Forms. While reading a book I would insert a sticky note in the appropriate place (so as not to interrupt the reading unduly), then complete the Bento entry at a later stage. This method worked very well for its intended purpose. For example, if I needed to locate all the fictional references to ājazzā, I would enter it into the search box and all the relevant records would be selected.
Of course, for other purposes, a different approach is needed. For complex theoretical texts Iāve found that there is no substitute for detailed, sequential notes. I use Apple Pages for this. I would disagree that this method is ineffective, but it all depends on how the task is approached. Some level of analysis is required before anything is written down, that is, a block of text or section of a chapter needs to be read and thought about and the main point(s) clearly identified and summarised. In my experience this leads to a much more thorough understanding of the text than can be obtained simply by reading it. Another benefit is that after a lapse of time the notes can refresh oneās sense of the text without the need to reread the entire book. Itās an easy matter, too, if one wants to quote a particular passage or discuss a particular point to locate the precise reference.
Neither of the above systems copes adequately with a constant problem that is often mentioned: how to manage the countless pieces of information relating to a research project that one comes across in the course of reading. Iāve discovered Iām not alone in trying to remember an elusive detail that suddenly seems pertinent to what Iām writing, and spending hours trawling through websites, PDFs and my print library in a vain effort to track it down. It was this that led me to try Tinderbox.
In recent years my interests have revolved around early modern philosophy, and in particular the translation from Latin into English of various hitherto untranslated texts. The references to concepts, historical events, academic and theological institutions, and the works and views of many often obscure writing can be bewilderingly complex. Tinderbox provides a means of mapping all this material and its interconnections that is not only effective but enjoyable. By this I mean that, rather than just jotting a new piece of information down somewhere, one can always find a suitable Tinderbox note, or if none exists create one within an appropriate container to accommodate it. Being a sucker for nice visuals, I take great pleasure in organising colour schemes and attractive layouts in map view. And while this is not strictly necessary, it helps to keep one motivated in a way that other approaches may not. As a relative noviceāI have to say Iām completely out of my depth with most of the technical discussion that occurs in the forumāIām still using Tinderbox at a fairly basic level, but itās certainly proved its value. If itās of any interest, Iām happy to post an outline of the way Iāve set it up, and Iād certainly welcome suggestions as to where to take it next.
Iāve probably strayed a little far from the topic, so Iāll conclude by saying yes, I completely agree that the most important aspect of any method of note taking or organisation of research data is the quality of thought and analysis that goes into assembling and recording the material. No software is a substitute for this vital step, however much it may contribute to its subsequent usefulness. And there are certainly programs I wouldnāt want to be without, not because they are necessarily the best in any absolute sense, but because they complement effectively my particular way of working: apart from Tinderbox, these include Scrivener, Yep, Keep It, Bookends and Mellel.
Yes, there absolutely is. Think the scientific method: Hyptoehses, test/document, review. Lather, repeat, rinse. Even if youāre only doing this work for yourself, writing down the process is critical, else youāll find yourself repeating work, reproducing mistakes, etc. And, as you point you, you may find a hidden gem that you can contribute. Again, this is what the whole knowledge-making and publishing process is about.
You are not. this is universal. As I note, youāll want to develop a process that helps you re-discover your insights when you need them, not necessarily to retain them in your RAM memory.
I agree. Another reason, if nothing else, is to remind your future self either/both why you used that approach in this context or the steps needed to reproduce it. Unless one is fortunate enough to study/work in one homogenous niche or are very dogmatic about process, remembering the nuances of the structure of past note-taking is value easily lost in time.
It seems to me that a significant motivating factor for Luhmann was to create a method that enabled him to trace theoretical ideas relating to his views on systems theory. He was a sociologist, but he was also a systems theorist, writing volumes on the topic including:
1993 - Law as a social system
1998 - The economy as a social system
1999 - Science as a social system
2000 - Art as a social system
Anyone of these topics would take me a least a few lifetimes to cover:-).
Please please, post your outline (with pictures ) when you get the chance. I always find learning how others do research, how they wield the tools they use, and how they adapt over time is one of the more fascinating aspects of this forum. The technical depths of Tinderbox are interesting, but the real world uses of this or other techniques is really the point of participating here, IMO.
Thanks for your interest and encouragement. Iām about to reorganise my Tinderbox projects as Iāve reached a point where, rather than have everything related to the very broad field of Early Modern Philosophy in one document, I think it may work better to create separate Tinderbox files for particular projects within this field. Iāll see how this goes before documenting the whole process. One thing Iāve taken away from the knowledge management article you mentioned, @satikusala, is in addition to any external interest, the value for oneself of reflecting on and formally documenting the details of oneās approach.
Before you embark on this, Iād recommend you take a look a the last few weeks of meetups. Youāll see the positive results that others are having with the linking and indexing (terms, categories, themes, contacts, location, etc.) strategies that Iāve been developing. I have a feeling youāll experience great efficiencies by centralizing and linking your knowledge.
Thanks for this advice. It may turn out to be a case of restructuring the existing document, starting with a clearer sense of its overall purpose and parameters. When I began using Tinderbox mid-2021 I started with a few notes that progressively became multi-generational containers on a rather ad-hoc basis. I ended up with notes on the same author or topic in different places, and it took a lot of drilling up and down to get from one to the other. Re-visioning the field, and adopting either a flatter structure or more use of aliases (or both) may be a more productive approach.
Donāt be afraid of re-structuring. Yes, it is work you donāt āhaveā to do, but I find enlightened self-interest wins out. Tinderbox is very forgiving in this respect. Generally some re-structuring improves messy old document as I go back and, for instance, apply prototypes my old self would not have thought to use. If I need to export, e.g. for a report, I might review the docās structure (the docās outline) to make it easier to generate a better linear output of info.
I recommend @satikusalaās suggestion. Even if you donāt want to fully embrace the sort of modularity he shows, Iām sure some of the techniques can easily be borrowed into your own work. I think the pattern of auto-generating notes about specific subjects (terms, keywords, tags - whatever noun you use) is very powerful. Not least there is a single note in your doc explaining that thing. It might be to explain to others (e.g. as an endnote or appendix in a report) or simply a note to self to remind you what that thing is and/or why you are taking the trouble to note it.
Indeed, extracting terms to a canonical (single source reference) note seems very much in the spirit of Luhmann. Itās too easy to follow his āsystemā rather than the ideas driving it. for instance, Luhmann didnāt have digital links.
Agreed. amplifying that I presume you mean organisational/decompositional hierarchies rather than where a note lives within your TBX.
I make the latter point as you generally donāt want a map (i.e. an outline view container) with 00s or 000s of notes. As long as they are linkedāor have attribute values allowing for easy queryingāwhere they live in the TBX stored structure (hint: it is the outline view) matters less. It is worth noting as some people are uncomfortable with things being stored where they canāt āseeā them. The problem with that it scales badly, even with a very big screen.