The video above is a conversation between Nicole van der Hoeven who hosted it, Bob Doto who wrote the excellent A System for Writing, and Tris Oaten of the No Boilerplate YT-channel (that I did not know before).
Having watched this video where PKM systems are discussed and the different approaches the three participants have, a thought emerged. A thought that I have had previously at PKM events, or when I browse through e.g. the Obsidian forum. In a lot of PKM conversations people can talk past each other due to unspoken assumptions about what your system ‘should’ be.
Not necessarily in the video above, it’s just that watching this conversation made me think about it again.

One dimension is those that assume their system is for personal knowledge. Subjective and temporal as Bob at some point clearly says in the video. As opposed to a system to store references, facts and objective knowledge.

Another is using top-down and up-front created structures vs emerging structures that are earned over time and where noticing emergent structures is newly forming personal knowledge.

A third is whether your PKM system or your Zettelkasten is seen as the whole thing, a artefact-as-is (and thus perhaps transferable in its own right), or whether one’s interaction with it, your own thinking plus your PKM system / Zettelkasten is the whole thing and thus a fully personal tool. Do you see yourself as part of your PKM system, or not?

These three differences in attitude and resulting approach determine quite a bit it seems of what you choose to do and not do in practice (such as the Folgezettel part of the conversation in the video shows).

But it seems to me we hardly ever spell out our own starting assumptions (and thus design parameters) of one’s PKM system and where we see ourselves. We merely project our own ‘givens’ onto the outside world.

What Bob Doto says in the video for instance about his practices resonates well with my own, born from personal knowledge, emergent structures and personal interactive tool.
To me PKM is personal along three dimensions, a personal system, personal knowledge, and personal management, which map well on the three dimensions of assumptions just listed. But I sometimes get the sense that to others that sounds like not as PKM at all, just as making it up as you go along. Which isn’t a false description per se, except for the implied judgement that it won’t yield results and isn’t a deliberate design choice. While I see ratchets and compounding effects.

Maybe we need to more often precede our conversations about PKM system design choices with speaking our usually unspoken assumptions about what type of systems works for us.
Although paradoxically it may be the case that for some that isn’t perceived as a need, if they already assume there is a single cluster of ‘right’ ways of doing things. Then of course it is not needed to speak of assumptions, because what is right is external. Vice versa to me it is not PKM, is not P at all, if it’s assumed there’s a single right way of doing it for all. Then PKM is a method and productivity hack, but not a system for thinking and sensemaking.

For next year’s European PKM Summit I think I need to come up with a short way of describing that and put it on my name badge.

Imagine you have a recipe for a dish you like. You copied the ingredients and instructions from a magazine once, or your mother wrote it by hand decades ago. You decide to use the recipe, and from its list of ingredients you make a shopping list. Some things you already have at home, other items you need to get. You think of the one or two different shops you’d need to go to, and list the different items in a way that follows the order in which you will walk through the store. Would you describe the recipe as creative output? And the shopping list? Yes, no, neither, or both? Which one would you think qualifies for copyright?

The recipe (both the directions and the ingredient list) is seen as a mere statement of fact. Copyright is not applicable. That’s why cookbooks usually have a clear curated selection stated in their title (‘The 50 most cherished Indian recipes from around the UK diaspora’), photos (the dish with a sprig of herbs positioned just so), and anecdotal flourishes (‘Upon entering the village I saw an old grandmother make this in front of her house, and she shared the family secret of this incredible sauce with me’). Because those elements do carry copyright. Just not the recipe as such. Take 500 grams of chopped tomatoes and cook for 12 minutes on a low fire. Add half a tablespoon of powdered cayenne peppers and stir. Serve cold.

Your shopping list is a unique thing in comparison. It contains a curated list of ingredients (excluding the things you already have), and you ordered them to align with your actual physical path through one or more shops that you mentally selected to go to. Maybe you crossed something out, and added it in a different place after first making the list. Maybe you added one or two other things that you need, as you are going to the store anyway. This does clear the, deliberately very low, hurdle for creative effort recognised by copyright law. It’s just that you as author perhaps think of it as ephemeral, trivial, and something you may well leave at the bottom of the shopping cart as you exit the store.
Some lists are of course solely statements of fact, e.g. a list of all the heads of state and the years of their reign, the planets in our solar system in whichever order, a bibliography of an author. When you add a little bit of purpose to a list, moving it to an unique expression of an idea you had, then it quickly becomes something else.

A creative artefact.
A list that is the result of some internal process of yours with some internal logic, even if it eludes another person encountering the list, is more than the sum of its items. Curation, selection and exclusion, ordering, at one or more levels of hierarchy, are determined by and express the intention and purpose of the list maker.

List maker.
It’s something E calls me every now and then, list maker. Because quite often my first response to anything that requires planning, thinking, or writing is ‘I’ll make a little list’. Because sitting down and making a first list is beginning the work. Writing a list is not the result of thinking, but part of the process of thinking itself.
An Outliner tool is a key digital list making aid (even if they all have their limitations). A good Outliner allows you to put making lists ‘on rails’ as Dave Winer put it.
Moving an item up or down, to the top or the bottom. Nesting a thing under another, or deeper still. Moving a nested item up a level of hierarchy. Hide the subitems under a thing, or revealing them. Make a connection with an element elsewhere in an outline or with/in a different outline. Turn lines into bullets into numberings and back. Switch between different types of visualisation, one of which is the outline. All made seamless with keyboard shortcuts.

In the 1968 Mother of All Demoes Doug Engelbart, showing his vision of what computers should and can do, impresses the audience when he moves things in a list around in an outliner and switches between visualisations of the list, before using another outline for a presentation. The list he makes is of course a shopping list.

Many of the lists I use emerged over time from my notes and work, a type of emergent and earned structure. Some have both an outline structure and a more visualised networked one (a tool like Tinderbox allows you to switch between views, so does Obsidian with Excalidraw). Some have a bit more complicated inner structure or are partly dynamic or help with decision making, making them small knowledge machines.

There are many types of lists I regularly make and use.

  • Checklists for various processes and events (like travel), and periodic reviews
  • Dashboards, which are (check)lists in two dimensions, that ensure I take into account all aspects of something.
  • Daylogs with links to appointment notes, listing events, links to things I found and interstitial journaling.
  • Maps of Content (or elephant paths as I call them)
  • Memory palace overviews (listing loci) of places I might use as mnemonic device
  • Card decks for spaced repetition.
  • Outlines of texts I’m writing, outlines of presentations, both with links to underlying notes and references.
  • Interests I currently have (questions, examples) and how I might see them as elements of practice, knowledge fundament etc.
  • Tasks lists, selected on context (train, home office, company office etc), effort, energy level and time needed.
  • A spreadsheet that provides, yes, my shopping list for larger parties, based on the list of participants, their dietary requests etc., based on previous parties and amounts consumed.
  • Book lists

Book lists are like any list in that they involve selection and ordering too. They are also a bit more than a creative artefact.

Book lists are libraries.
Any list of books you create is a library, even if it’s a library of the mind that you make tangible in a list.
The list of books that are in my home office book case for instance is a simple example describing that part of the actual collection of physical books in our home. But there are more book lists I work with.
All the books, whether I (still) own them or not, that I have read in a given year.
All the physical and electronic non-fiction books I own and have not read yet, by topic. Or don’t have yet but thought interesting enough to note. They form a reservoir of preselected books I thought might be of interest at some point, that can serve as a research tool. That list I call my anti-library.
Or a similar list for unread fiction books I have, to use when selecting a new book to start in.
A list of books I may want to acquire at some point (generated from what I come across online and in shops that looks interesting or fun, without buying it), a library of wishes of sorts.
A list of books I definitely do not want to own or read, which contains books I have regularly come across thinking they looked interesting, and then realising I had rejected them a few times in the past already, and also contains authors I want to avoid.

These lists overlap, interlink and morph. Most of my daily note making is in the shape of lists, where items may get extended into paragraphs. Using outliner functionality I move them around, extend, link and change them. Parts get shunted into their own notes, some becoming a note in my core personal knowledge notes, others ending up in more mundane notes. Most will remain where I wrote them. Some will become lists I use more frequently or have a structure that is a piece of personal knowledge in itself, such as the ones listed above.

Making lists is not a chore or something predefined, but key to the work of eliciting meaning from all the disparate things I encounter in a day. It allows manipulation of all the small bits of information, from which meaning and structure may emerge. It’s a way to locally reduce entropy in my notes where useful.

Make lists. As your creative artefacts, as your libraries.

left part of screen shows an outlined list, right part shows Doug Engelbart during the 1968 Mother of All Demoes.
State of the art list making, 1968. (Screenshot of the 1968 demo by Doug Engelbart of an outlining tool)

At the start of the year I stopped buying books at Amazon and shortly after stopped using my Kindle. I have a BOOX Nova 2 e-ink device that I can use to read and annotate material. Since May I also have a Kobo ereader that E gave me as a gift.

While reading I make notes and highlights in the books I read. I had my Kindle set-up in such a way that any Amazon annotations I made would automatically end up in my personal knowledge management notes. For the BOOX device I have a similar set-up although it requires a manual step (connecting the device to my laptop and transferring files).

For the Kobo device I am now trying to figure out how to get annotations into my notes.
The basic path is similar to the BOOX device.

Kobo should have an option to access annotations from your Kobo account online, but I could not find it.
Using Greg Morris’ description (archive link) I edited the hidden config file on the Kobo device, activating the export option locally. That creates a menu option for each book on the device to export annotations and highlights to a text file. Similar to the BOOX device that text file can then be retrieved from the device.

There are three types of books on my device.

  • Books bought through a Kobo affiliated platform and downloaded to the device,
  • Books side loaded from my Calibre library,
  • Books accessed through the Kobo Plus subscription our household has.

It seems to me like the annotations of all three are treated separately and differently by Kobo. Kobo itself states that annotations from side-loaded books will not be synced to your Kobo account (although as stated I don’t see any option to access any other annotations through the account either).

Looking at the exported annotations of a Kobo Plus book, I noticed that the location of an annotation is shown when looking at the overview of annotations on the device, but is not listed inside the exported text file of annotations. The location also isn’t exact, but ordered by book chapter. Having the location of an annotation to me seems a key piece of information, and it’s odd that it isn’t in the exported file.

I will have to explore more how to bring my Kobo device annotations into my notes in a usable way.

Favorited Genoeg te ontdekken by Frank Meeuwsen

Frank schrijft over de lol en het waarom van bloggen, in referentie aan een posting van Elja en mijzelf langs die lijnen. En demonstreert zo waarom hij al 25 jaar blogt deze zomer (en ik in november 23 jaar). Bloggen gaat niet om anderen iets te zeggen te hebben, maar wel over het achterlaten van langere sporen die anderen tegen kunnen komen. Om zo in gesprek te komen of elkaar te inspireren Omdat je zelf enthousiast bent over wat je deelt, is wat je schrijft altijd goed genoeg. En leidt het tot authentieke interactie, in die gevallen waarin er reacties komen. Want geen reacties maakt ook niet uit. Goed genoeg, het is iets om je elke keer opnieuw weer te realiseren. Dank voor het oppikken van het conversatie- en exploratiedraadje Frank.

Wat ik lees bij Ton resoneert enorm bij mij op dit moment. […] Ik haal enorm veel plezier uit de ontdekkingstochten die ik nu doe. […] lezen over creativiteit, eigen oude interesses opnieuw ontdekken. Het zijn allemaal bezigheden [..] waar ik enorm veel voldoening uit haal. En ik vind het leuk om dat met anderen te delen. Want dat doet er toe.

Frank Meeuwsen

Obsidian has added a functionality called ‘Bases’. An interface driven way to make overviews like you already could make with Dataview queries. Where Dataview is a plugin, Bases is a core functionality. Bases use properties for filters, and I don’t really use properties, at least not as frontmatter like Bases assumes. Such frontmatter properties suggest the need for structure and consistency that can only feel like a burden more than an aid. I do have inline data fields (inline works better for me, because I can turn any part of a note into a piece of data that way).

Perhaps it helps make overviews of ongoing projects somewhat easier to make. Let’s see.
I’m hesitant as it seems a step towards Obsidian trying to be everything to everyone, bloating functions, whereas for me having plain text notes that I can approach with any other tool besides Obsidian is the key thing to ensure works.

I’ve been long fascinated by memory palaces. As a primary school kid and again as a teenager when I encountered the concept, I concluded that, while fascinating, they were more effort than what I would gain. My memory was fine, and first conjuring up a set of locations and then visualising evocative things in them to remember something seemed an awful lot of upfront trouble.

In recent months I’ve looked at memory palaces and other mnemonic techniques again. Reading Wayfinding by Michael Bond gave me insights into the role of the spatial brain in remembering, but also mental health and ageing. Reading Lynne Kelly’s Memory Craft gave me lots of insights both in various memory methods, as well as the effort and repetition that goes into them and which thus supports learning. Both were fun reads.

I decided to create a memory palace in my home office, which now has 45 loci.
Which leaves me with the question, what do I want to remember in it? And, I don’t know!

I find it quite hilarious that I can’t come up with something worthwhile to put in a memory palace! 😀
However I suspect that it might be the same for others. Searching forums for memory techniques, most applications are focused on showing off how well the methods work. Memory competitions to remember a random deck of cards in sequence in a few minutes.

Not a whole lot examples of memory palaces used for something ‘real’ and significant to its user.

Do use memory palaces? What do you remember with them for the long term? Why that? Would a note to link to be enough too?