I have been interested in personal knowledge management (pkm) for a very long time. I have been an avid notes maker ever since I learned to write. Digital tools from the late 1980s onwards have been extremely useful. And a source of nerdy fascination, I confess. I am certain personal knowledge management (pkm) is of tremendous value for anyone who wants to keep learning and make sense of the world around them.

On March 14 and 15 the European PKM Summit is taking place for the second time in Utrecht, Netherlands. I assist with inviting speakers and workshop hosts for this event.

I am donating a ticket for a student in the Netherlands to attend this two day event. I did the same last year.

Are you a student at a university in the Netherlands with a strong interest in personal knowledge management (pkm)?
Is your interest in pkm to strengthen your personal learning and deepen your interests, rather than increasing (perceived) productivity?
Would you like to go to the PKM Summit on 14 and 15 March in Utrecht, but as a student can’t afford the 237 Euro ticket price?

Then I have one (1) conference ticket available! Let me know who you are and what fascinates you in pkm or attracts you to the event. If there are several people interested I will choose one. I will donate the ticket a month before the conference, by February 15th, so state your interest before then.

The single condition is that you attend the event on both days and participate actively in the event. It would be great if you would share some of your impressions of the event afterwards online on the open web, especially if that is something you’d normally do anyway.

Interested? Email or DM me (in Dutch, German or English)!

The past year I’ve had more conversations about personal knowledge management than for a long time before. Regularly questions come up along the lines of what structures should one use, what should one keep in their notes, what are the best tools? Most of my contributions to such conversations boil down to ‘there’s nothing you should do other than what fits you, and I could show you what I do and why that works for me’.
Ultimately I keep thinking people don’t take the P in PKM far enough. I think PKM is personal not just in one way, but in at least three ways.

  1. It is personal knowledge management in the sense that your system is yours only. You do it, build and extend it as you see fit. It can exist independently of whatever other working environments you have, it is fully personally yours. This enables and secures your professional and learning autonomy, allows you to be pro-active. You bring professionalism to its upkeep and tools. When you go someplace else, you take it along with you.
  2. It is management of your personal knowledge. Personal knowledge in the sense of your own networks of meaning, your insights, the expressed connections you made between pieces of it, your associations and verbiage that tie into your internal world. It exists to feed your agency, your combinatory creativity, and is aimed at your own mix of evolving personal interests. It’s there for just you to interact with. This allows you to steer the direction of your own learning intentionally, and enables an activist and artisanal stance towards your interests, professional or otherwise. Your personal knowledge doesn’t need to be understandable or be useful to others. Sharing in context is an act in itself, an output rather than a function.
  3. It is personal management of knowledge. You have your own methods and structures, that are geared to how you work, think, learn and create best, and which have emerged over time and you then reinforced because of their utility to you. You create your own mechanisms and algorithms working with your material, and reflect on them. Your system does not need to be understandable or workable for others. Your structures fit your internal world, have their logic and starting point in the fact that your behaviour is pretty predictable to yourself at least. Some of the structures in your system may well be just in your head rather than made tangible in your external system. Some structures may be intentionally omitted to ensure you can surprise yourself with your system, feeding discovery and wonder.

I can’t tell you how to do PKM, I can show you what does and doesn’t work for me and tell you why I think that is. I will tell you to take PKM very personally, and then some more.

Bookmarked Tools for Thought Library in Zotero (by Chris Aldrich)

This large and interesting collection of books, writings, quotes and other artefacts on note making and personal knowledge management, tools for thought in short, through the ages is something to explore at leisure. It seems to have been put together by Chris Aldrich some two years ago. Great stuff. Came across it in Chris’s Hypothes.is stream, and didn’t immediately realise it was a reference to his own collection.

Reading Bob Doto’s recent book on his note making and writing practices, he explained how he uses his Luhmann-style alphanumeric numbering of notes as a way to spot where a richer grouping is emerging as a possible starting point for his writing. It made me ask, how to spot similar patterns in my digital notes without that numbering system?

Alphanumeric numbering

The alphanumeric numbering basically works like this: When you start your notes collection, you number the notes from the very first one. Say you start with your first two notes on two different topics, A and B. For Topic A, the first note you give the number 1. Topic B’s first note 2. Then for each new note, you decide where to place it in the existing collection. If you think it’s connected to Topic A, it may become 1a. A few notes down the line on other topics you may make a note you place in 1b. Then some time later you have a note you want to place directly after 1a. but not after 1b, so you number it 1a1, etc. Key here is that the numbering system doesn’t give a premade structure where you need to slot a new note in an existing hole (unlike library numbering systems). The numbering system merely means you must choose a first place where you place a new note, intentionally making a first connection to an existing note and number it accordingly. For physical note making systems on index cards this is I think basically the only way to do it, if you don’t want to use a predefined structure (and you don’t because structure is emergent from working with your notes, a knowledge output, not an administrative tool), and do want a navigable and explorable system.

Alphanumeric numbering to detect growth in your system

At the other end of his PKM system, where Doto creates writings using the material he collected over time, the alphanumeric system helps him in finding potential things to write about. Topics where there are lots of notes, accumulated over some period of time, will show up as denser parts of his alphanumeric system. Say in Topic B’s number 2 branch above, a year later there are just 1 or 2 new notes. 2.1 and 2.2. That is a signal Topic B wasn’t an interest that gained any depth that year. But say that note number 1a is now a grouping of a dozen notes, 1a1-1 and a further forking set below it, and 1a2 has some, and there’s 1a3 with no further notes attached. Clearly something happened there in the intervening time. Your attention attached a range of notes to that first starting point 1a, and perhaps it means you have something to write there to bring those notes together. It’s like a grape bunch on a vine. Vine 2 hasn’t grown any grapes let alone any bunches of them, but Vine 1a has. And there may be other grape bunches, bigger, smaller, elsewhere. You choose a bunch to make some wine, i.e. inspecting and reflecting on that grouping of notes and then writing.

On not having alphanumeric numbering in my system

My notes are not numbered that way, although they do contain a timestamp. They’re not numbered because I have a digital notes collection, in which it is easy to make links between notes. I add the time stamp both for unique titles (‘Some good summarising title 20241018125808’ is different from ‘Some good summarising title 20020424125820’ despite the same title text) and to glance from the title from which period in my activities something comes. My notes always have a link to another already existing note, like the alphanumeric system, I always intentionally choose a first connection. Without it, it is not really a navigable and explorable system. However, over time or at the time of first writing, I may add additional links from that note to others. It is not always visible which link was the first link, the equivalent of choosing the first position in the alphanumeric system.

On the output side this means I cannot easily spot where the density of my notes has grown to a budding grape bunch. I can see which notes are most heavily connected, using the Obsidian graph, but that’s equivalent to pointing a lot to a main branch, and the more I point to a single note the less meaningful it is, as it becomes more of a generic category essentially.

So what are my options to detect emerging dense spots in my notes?

The alphanumeric grape bunch is basically a group of one or more short or longer lineages originating from a single point somewhere in the total.
Those lineages are present in my notes too, but not easy to spot. Sometimes I make deliberate chains (Note B linking to more abstract concept A, and to more tangible example C, making an A-B-C train of thought), but not often. Lineages would be easier to spot if links in notes had metadata, like the time of linking. This would both show in a note the first link (the first place it was put in), and allow across notes the exploration of the sequence in which notes x, y and z got connected by looking at note creation data and incoming linkages. Links are information objects in their own right, and have different aspects like direction(s), character, intensity, a time dimension and a versioning history, none of which is captured in my system (nor in those of others I saw). Links can also grow into new notes. A link between A and B over time and through reflection deepening in meaning, necessitating its own note to express it with enough atomicity.

Might local graphs help?

The local graph of a note in my Obsidian tool can provide a bit of lineage, by looking at the vicinity of a single note limited to incoming links and set to a depth of 2 or higher. It’s not visually obvious though, it doesn’t jump out. In the following graph (incoming links, depth 2, with ‘Links as information object’ as the branching off point) I colored the different branches. Note that the title for each node/note has a timestamp showing how much time there was between one note and the following added to the lineage. Some notes have the same date, meaning they were written in the more or less the same sitting. Also note that some older notes link to some newer notes, indicating I edited the note to include a new link to a newer note)

What also emerges from this image is that several ‘lineages’ connect further ‘down’. Essentially they create a loop, a circle of notes. There are many more, and I think they are a sign of density (one that alphanumeric numbering doesn’t have), yet like lineages not easy to spot. Two examples are shown below. One circle based on a depth of 2, another with depth 3.

While this type of visualisation isn’t useless, it’s also not obviously useful in this case. Would there be other ways to search for things like “lines longer than 3 notes, with more than 1 branching off point with at least 2 notes depth”.

Do you have ways to spot emerging clusters outside of alphanumeric numbering and graphs in your notes? As a suggestion for your potential next writing?

Bookmarked Latticework: Unifying annotation and freeform text editing for augmented sensemaking by Matthew Siu and Andy Matuschak

Back in early February I got a chance to work with a beta tool for sense making in my notes. See my impressions at the time. Matthew Siu and Andy Matuschak watched me for an hour as I used their prototype tool to start shaping a workshop design from various inputs. I was intrigued and enthusiastic, but a few weeks later due to some tech glitches I stopped using it. Today Maarten den Braber in an e-mail pointed me to Latticework from last June, describing the project as it stood at the end. It’s an interesting read, which I annotated (if you read those annotations, start at bottom of the page to read them from the top of the article (or use Hypothes.is to see them in context,there’s no way to link to the overview directly for non-users I think).

I re-installed the plugin in Obsidian, and will work with it some more. Here’s hoping some of the original glitches no longer occur.

We had a strong personal motivation for this project: we often find ourselves stuck in our own creative work. Latticework’s links might make you think of citations and primary sources—tools for finding the truth in a rigorous research process. But our work on Latticework was mostly driven by the problems of getting emotionally stuck, of feeling disconnected from our framing of the project or our work on it.

Matthew Siu and Andy Matuschak

Gisteravond was de 6e meet-up van Nederlandstalige Obsidian gebruikers. Net als de editie van afgelopen december vond deze meet-up plaats onder de vlag van de Digitale Fitheid community en de KNVI (Koninklijke Nederlandse Vereniging van Informatieprofessionals).
De vorige keer was ik een van de facilitators, dit keer was de begeleiding in handen van Martijn Aslander en Lykle de Vries. Dat gaf mij gelegenheid meer inhoudelijk mee te doen, en dat was prettig.

Het recept was hetzelfde als wat Marieke van Vliet en ik de vorige keer improviseerden: aanwezigen droegen aan het begin een onderwerp aan, en vervolgens mocht iemand telkens iets kiezen uit de lijst (maar niet het eigen onderwerp). Zo komt een divers lijstje onderwerpen tot stand, en zorg je ervoor dat een bredere groep aan het woord komt.

Iemand vroeg of je Obsidian ook op een USB stick kunt draaien. Dat je je vault op een stick hebt, en dan op systemen waar Obsidian staat die kunt openen inclusief alle plugins etc. Ik stelde voor dat ter plekke te proberen, en het antwoord lijkt ja te zijn. Deed me denken aan de wiki-on-a-stick experimenten die ik lang geleden deed rondom het ‘patchwork portal‘, waarbij wiki’s met een lokale kleine webserver op een stick werden uitgedeeld waar anno 2005 nog geen of heel weinig internet verbinding was.

Ik was zelf benieuwd of mensen n.a.v. de PKM Summit in maart meer zijn gaan doen met de visuele technieken die Zsolt Viczián met zijn Excalidraw plugin toen liet zien. Met name was ik geïnteresseerd in of mensen bestanden tegelijkertijd als tekst en als visueel element gebruiken (hier uitgelegd door Nicole van der Hoeven). Twee deelnemers lieten het e.e.a. zien. Zelf heb ik een sneltoets voor het schakelen tussen tekst en visueel ingesteld, maar dat zag ik hen niet doen. Dat zegt me dat ze die switch weinig maken. Ik zal er zelf eens iets over schrijven in meer detail, met twee recente voorbeelden hoe dat waardevol voor me was en heel prettig en wrijvingsloos voelde.

Maarten den Braber was een van de aanwezigen die liet zien hoe hij bepaalde zaken in zijn workflow automatiseert, vanuit hetzelfde principe dat ik hanteer: geen dingen doen die uniek zijn voor Obsidian, je moet altijd ook met je platte tekst bestanden uit de voeten kunnen. Hij liet de PDF++ plugin zien, en die moet ik zeker eens onderzoeken en vergelijken met hoe ik momenteel Zotero gebruik.

Muhammed Kilic liet zien hoe hij over meerdere apps heen dezelfde tags, links en indexes gebruikt. Hij noemde daarbij hoe ik dat ook doe in mijn hypothes.is annotaties (links naar bestaande notes, taken, tags opnemen waardoor het in Obsidian meteen in context staat), maar liet zien dat hij dat ook in Zotero doet. Dat doe ik niet in mijn annotaties daar, en toen hij het liet zien vroeg ik me af waarom eigenlijk. Ik link wel vanuit Obsidian naar Zotero, maar in mijn annotaties verweef ik in Zotero mijn notes en tags veel minder. Eens over nadenken, en uitproberen.

Tot slot merkte ik dat het in een groepsgesprek als dit lastig is om min of meer standaard ook te laten zien wat je beschrijft. Je moet je dan maar voorstellen wat iemand daadwerkelijk doet, ipv het te zien. Voelen we ons kwetsbaar in het tonen van onze tools en werkwijzen? Het aantal malen dat ‘tell’ ook met ‘show’ werd ondersteund was daardoor beperkt, en dat is jammer vind ik. Voor een volgende keer zou het ook leuk zijn om in plaats van over aspecten te praten eens iets van ieders gehele implementatie te zien, en daar vragen over te stellen.