Having described my overall system and how I use Obsidian in more detail for daily work, task management and networked note writing, in this posting I turn to how I arrange for low friction flow in Obsidian.

An important functionality of Obsidian is that you can arrange different panes in which you can show files or other things. This is useful in various basic ways, e.g. to have a note you are editing open twice, once to edit, once seeing the preview. Or, as in the image below, to have a note open, with search results, a graph of connected ideas, and an overview of backlinks.

Basic pane layout in Obsidian, search results, a file, a network graph and backlinks
Basic pane layout in Obsidian, search results, a file, a network graph and backlinks

Every pane can be split horizontally and/or vertically, and again, up to the point it fills your entire screen. This allows me to for instance in a client conversation have my task list for that project, notes from our previous conversation as well as in-depth notes about the work, all in one overview, next to the file in which I’m taking notes from the ongoing meeting itself. While in parallel to all that I still have the ability to pull all kinds of other information or conceptual description during the meeting. This allows me to quickly bring up things in high detail, and easily switch between high-level and low-level things, organisational aspects and the topic at hand etc.

Where this functionality comes into its own is where you can save specific pane / screen set-ups and switch between them as different workspaces. Since recently there is a workspaces plugin that does this. You can also do it by hand or scripted in the background. The current set-up is always stored in a file called workspace in the Obsidian folder in your vault. It’s a JSON file describing the screen lay-out. If you copy and rename that, you have saved your workspace. If you put it back and reload Obsidian you have reinstated that workspace. The plugin does the same thing but smoothly from within Obsidian itself.

This means I can switch between workspaces at will, such as:

  • The daily start workspace (which includes today’s daylog, yesterday’s daylog, the root task list and month map, the quarterly goals and an #urgent search)
  • The weekly review workspace (quarterly goal list, weeklog, review template, root tasklist, monthmap)
  • The month map workspace (#urgent, root tasklist, last month map, this month map, quarterly goals)
  • The conference call workspace (Project main note, project task list, last call’s notes, new notes, project details)
  • Note writing (search, graph, pane with relevant other note(s), note being written)


The workspace I use at the start of the day: #urgent things on the left, today’s log and yesterday’s log in the middle, full taks list, quarterly goals, and month map on the right.

This list of handy workspaces may still grow over time I suspect for different aspects of my work.

There’s one more posting on my use of Obsidian left. It will be more of a summary, on what makes Obsidian work well for me, and why it fits my preferences.

3 annotations of "100 Days in Obsidian Pt 5: Flow and Workspaces"


This blogpost has 3 annotations in Hypothes.is! See annotations

3 reactions on “100 Days in Obsidian Pt 5: Flow and Workspaces

  1. I’ve been using Obsidian a little over 100 days now. So, with over three months of daily use it’s good to review the experience. I will do this in some detail, and it will span several blogposts. To explain both the evolution over time, as well as how I currently work with Obsidian in practice in a more detailed way, as Frank (rightly!) requested.
    My system leads the use of tools
    First off, a key point to make. I am using a system for myself to plan and do my work, maintain lots of things in parallel, and keep notes. That system consists of several interlocking methods, and those methods are supported by various tools. What I describe in my review of 100 days of using Obsidian, is not about Obsidian’s functionality per se, but more about how the functionality and affordances of Obsidian fit with my system and the methods in that system. With a better fit with my system and methods, I can reduce friction in my methods, and reduce the number of tools I need to use in support of those methods. At the same time, the use of a new tool like Obsidian influences the practical application of methods, it creates a different daily practice. Those shifts are of interest as well.
    What I started with
    The image below shows you how my overall system of work and taking in information looks. It’s a personal knowledge management system, that both takes care of the networked nature of making sense of new information and evolving interests, as well as the more hierarchical nature of working on projects and executing tasks. Both start with my general notion of where I want to be headed (‘goals’).

    I used different tools for different parts of that image:

    Excel (orange) for: listing goals (3-10 yrs out), the 3 month planning cycle I keep (along the lines of ’12 week year’), the habits I want to maintain or introduce, and tracking of those habits and project progress/fulfillment.
    Things (red) for: areas of my life I’m active in, projects within those areas, and tasks in those projects.
    WordPress (darkblue) for: daily logs (which I started keeping end of April this year, on an internal WP instance), week logs (internal draft blogposting), and of course for public blogging itself.
    Evernote (blue) for: a list of all my current interests/favourite topics, all types of note taking, related to my work/projects and my information diet.
    Other tools (grey) come into play for feedreading (Readkit), blocking time (Nextcloud calendar in Thunderbird), book reading (Kindle, Nova2), keeping references (Zotero since June, Evernote before that)
    While evaluating my system, I tried Obsidian
    In the spring I had started evaluating my system. I found I was not keeping up several parts of it, had fallen out of practice with a number of elements, and had changed some of my practices without adapting the flow in my tools. It had therefore suffered in its usefulness. Being at home because of the pandemic allowed me to allocate some time to take a better look, and to start testing some changes. On the tool side of that evaluation, I want to get rid of Evernote (as a silo and single point of failure) since some years.
    One change in my system I was experimenting with, was keeping better atomic notes about the core concepts and key elements in how I work. Late last year I thought a bit about atomic notes, i.e. cards with individual snippets, and bringing those collections of snippets and the process of curating them and threading them into e.g. a blogpost or a line of argumentation. In January I came across Zettelkasten and took a closer look, in the spring I read a book about Zettelkasten and knew I wanted to adopt parts of it into my system (linking notes first and foremost, and storing references in a better way). That’s when I started using Zotero to keep references, and stopped doing that in Evernote (Zotero can take website snapshots and store them locally, something I used Evernote for a lot. On top of it if you give Zotero a reference it will find and store a PDF of a scientific article, very useful to read more deeply).
    I started to keep atomic notes, sometimes called ‘evergreen notes’ which I to myself now call Notions, capturing concepts from my work (so not work related notes, but conceptual notes) first in both WordPress and Evernote simultaneously. WordPress (a local instance on my laptop, not online) because I already used it for day logs since April, and it allows relatively easy linking, and Evernote because it is much easier to keep notes there than WP, but linking in Evernote is much harder. I also played with some note taking tools, and that’s when I came across Obsidian. It immediately felt comfortable to use it.
    How after 100 days Obsidian has covered my system
    After over 100 days of Obsidian my use of it has expanded to include a much larger part of my system. Along the way it made my use within that system of Things, Evernote and almost Excel obsolete. It also means I sharpened my system and practice of using it again. This is how the tool use within my system, with the use of Obsidian in green, now looks

    Obsidian now contains some 1200 mark down files. 500 are Notions, atomic notes almost exclusively about my own concepts and other core concepts in my work, in my own words. Mostly taken from my own blogposts, reports, and presentations over the years. The other 700 are some 115 day log / week log / month maps, about 100 proto-notions and notes that contain conceptual info to keep from other sources, and some 500 work and project related notes from conversations and work in progress. This sounds as a very quantitative take, and it is. I have in the past months definitely focused on the volume of ‘production’, to ensure I could quickly experience whether the tool helped me as intended. I think that monitoring the pace of production, which I’ve done in the past months, will no longer be relevant by the end of this year. I used the quantity as a lead indicator basically, but have been on the lookout for the lag indicators: is building a collection of linked notes leading to new connections, to more easily creating output like blogposts and presentations, having concepts concisely worded at hand in conversations to re-use? And it did. One very important thing, central to the Zettelkasten method, I haven’t really tried yet however, which is to use the current collection as a thinking tool. Because I was more focused on creating notions first.
    On Obsidian as a tool
    There are four things in Obsidian that are to me key affordances:

    it is a viewer/editor, a fancy viewer/editor, on top of plain markdown text files on my laptop. It builds its own local database to keep track of links between notes. Whatever happens to Obsidian, my data is always available.It being ‘just’ a viewer is important because Obsidian is not open source and won’t be. There is a potential open source alternative, Foam, but that tool is not yet developed enough.
    being ‘just’ an editor means using regular text files, it feels like coming full circle, as I have for the most part been note taking in simple text files since the late ’80s. Textfiles always had my preference, as they’re fast and easy to create, but it needed a way to connect them, add tags etc., and that was always the sticking point. It means text files are available outside of Obsidian. This allows me to access and manipulate notes from outside Obsidian without issue, and I do (e.g. on mobile, but also with other software on my laptop such as Tinderbox that I used for the images in this post).
    it makes linking between notes (or future links) as simple as writing their filenames, which is supported by forward search while you’re typing.
    it shows graphs of your note network, which to me is useful especially for 2 steps around a note you’re working on.
    I use Obsidian as simple as possible; I do not use plugins that are supposed to help you create notes (e.g. the existing Zettelkasten and Day log plugin), because they make assumptions about how to create notes (how to name them, which links to create in them). I created my own workflow for creating notes to avoid functionality lock-in in Obsidian: day logs are created manually by keyboard shortcuts using Alfred (previously TextExpander), as are the timestamps I use to create unique file names for notes.
    Timeline of three months of Obsidian use
    Below is a timeline of steps taken in the past months, which gives you an impression of how my use of Obsidian in support of my system has evolved.
    November 2019 I discuss the concept of cards (i.e. atomic notes), curation and writing output
    January 2020 I first looked at the Zettelkasten method and some tools suggested for it. I mention the value of linking notes (possible in Evernote, but high friction to do)
    May 2020, read the book about Zettelkasten by Sönke Ahrens, adopted Zotero as a consequence.
    7 July started with deliberately making Zettelkasten style atomic notes in WordPres en Evernote in parallel, to move away from collecting as dumping stuff in your back yard. Atomic notes only concerning my concepts in my work.
    8 July started using Obsidian, after having just started creating ‘evergreen’ notes
    15 July having made 35 atomic notes, I make a new association between two of them for the first time.
    28 July I’m at 140 conceptual notes. I named the collection Garden of the Forking Paths. I switched my digital tickler files (a part of the GTD method) from Evernote to Obsidian. I had stopped using them, but now it felt normal again to use them. The post I wrote about this, was made from atomic notes I already had made beforehand.
    5 August I find I haven’t used WordPress anymore for my day logs ever since starting with Obsidian, and that I also added week logs (an automatic collation of day logs), and monthmaps (a mindmap at the start of the month listing key upcoming things and potential barriers). My Evernote use dropped to 4 notes in 4 weeks, whereas it was 47 the 4 weeks before it. After almost a month of Obsidian, I am getting more convinced that I am on a path of ditching Evernote.
    12 August I renamed my ‘evergreen’ notes, that contain my concepts mostly, to Notions, as the generic word notes doesn’t make a distinction in the character of some the things I’m putting into notes.
    12 August I write a first long form blogpost made from Notions
    13 August Added Nextcloud synchronisation of the note files, allowing mobile viewing and editing of notes
    31 August I keep track of tasks in Obsidian and drop Things. There was a time I always did such things in straightforward text files. Being able to do so again but now with a much better way of viewing and navigating such text files and the connections between them, makes it easy to ‘revert’ to my old ways so to speak.
    13 September I am at 300 Notions. These first 300 notions are mostly my notions, the things that are core to my thinking about my own work, and the things I internalised over the past 25 years or so, of doing that work. I expect that going forward other people’s ideas and notions will become more important in my collection.
    13 September I describe how I make notions and notes
    September / October I increasingly use my conceptual Notions as reference while in (online) conversations.
    5 October I gave a client presentation (about the Dutch system of base registers) pulled together completely from existing Notions.
    7 October added a ‘decision log’ to my note keeping.
    16 October 100 days in Obsidian, 500 Notions and about 700 other types of notes.
    16 October reinstated a thorough Weekly Review (a component of GTD) into my system.
    21 October I gave a brief presentation Ethics as a Practice, the second this month pulled together from existing notes.
    This all as a first post looking back on 100 days of Obsidian.
    Part 2: Hierarchy and Logs
    Part 3: Task management
    Part 4: Writing connected Notions, Ideas, and Notes
    Part 5: Flow using workspaces
    Part 6: Obsidian development vs my usage

  2. Over the past few weeks I have described how my usage of Obsidian has evolved since I first used in early July. This is the final post in the series. Where the previous posts described my personal knowledge management system, and how I use it for daily project work, task management, note taking, and flow using workspaces in this final post I want to mention a few more general points.
    These points concern first my overall attitude towards using Obsidian as a tool, second its current functionality and third its future development of functionality.
    First, what is most important to me is that Obsidian is a capable viewer on my filesystem. It lets me work in plain text files. That is my ‘natural’ environment as I was used to doing everything in text files ever since I started using computers. It’s a return of sorts. What Obsidian as a viewer views is the top folder you point it to. The data I create in that folder remains independent from Obsidian. I can interact with that data (mark down text files) through other means than just Obsidian. And I do, I use the filesystem directly to see what are the most recent notes I made. I add images by downloading or copying them directly into a folder within the Obsidian vault. I use Applescript to create new notes and write content to them, without Obsidian playing any role.
    Next is that Obsidian allows me to rearrange how I see notes in different workspaces and lets me save both workspaces and searches, which means it can represent different queries on my files. In short Obsidian at this moment satisfies 3 important conditions for decentralised software: I own my own data, the app is a view, interfaces are queries. Had any one of those 3 but especially the first been missing, I would be exchanging one silo (Evernote) for the next. Obsidian after all is not open source. A similar tool Foam is. Foam is currently not far enough along their path of development to my taste, but will get there, and I will certainly explore making the switch.
    When it comes to current functionality I am ensuring that I use Obsidian only in the ways that fit with those three conditions. There is some functionality I therefore refuse to use, some I likely won’t use, and some I intend to start using.
    I refuse to use any functionality that creates functionality lock-in, and makes me dependent on that particular feature while compromising the 3 key conditions mentioned above. Basically this covers any functionality that determines what my data looks like, and how it is created (naming conventions, automatic lay-outs etc). Functionality that doesn’t stick to being a viewer, but actively shapes the way data looks is a no go.
    There are other functions I won’t use because they do not fit my system. For instance it is possible to publish your Obsidian vault publicly online (at publish.obsidian.md, here’s a random example), and some do. To me that is unthinkable: my notes are an extension of my thinking and a personal tool. They are part of my inner space. Publishing is a very different thing, meant for a different audience (you, not me), more product than internal process. At most I can imagine having separate public versions of internal notes, but really anything I publish in a public digital garden is an output of my internal digital garden. Obviously I’d want to publish those through my own site, not through an Obsidian controlled domain.
    Other functionality I am interested in exploring to use. For instance Obsidian supports using Mermaid diagrams, a mark-down style language. This is a way to use diagrams that can port to another viewer as well, and doesn’t get in the way if a viewer does not support them.

    Mermaid is a way to describe a diagram, and then render it. Seen here both from within Obsidian.
    Future functionality I will explore is functionality that increases the capabilities of Obsidian as a viewer. Anything to more intelligently deal with search results for instance, or showing notes on a time line or some other aspect. Being able to store graph settings in a workspace (graphs now all revert to the default when reloading a workspace). And using the API that is forthcoming, which presumably means I can have my scripts talk directly to Obsidian as well as the filesystem.
    I’ve now been using Obsidian for 122 days, and it will likely stay that way for some time.

  3. There are hundreds of resources on note-taking systems so don’t take this post as anything more than a collection that caught my attention. Once you go down the ‘zettelkasten’ or ‘digital garden’ rabbit holes, you may find that it takes a while to get out again.

    If you already have a sense of what the domain of ‘personal knowledge management’ includes, the list below might serve as a useful introduction to a systematic approach to how you think about knowledge work. If you haven’t yet come across what the fuss is about, you could find a reviews of Sonke Ahrens’ 2017 book, How to take smart notes.

    100 days in Obsidian – Workflow and system100 days in Obsidian – Hierarchy and logs100 days in Obsidian – Tracking tasks100 days in Obsidian – Writing notes (this post had the most areas of overlap for me; here are my Hypothes.is annotations)100 days in Obsidian – Flow and workspaces100 days in Obsidian – Final observations

    An interview with Ton Zijlstra by Andy Sylvester, where they discuss some of the posts listed above (you can see the page annotation I made while listening to this podcast).

    An example of my Hypothes.is notes on the Writing notes post in the list above.
    Share this:TwitterLinkedInFacebookWhatsAppEmail

Comments are closed.

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Find out more about Webmentions.)

Mentions