Mind-mapping is a powerful tool. In this post I will show you how and when I mindmap with Excalidraw in Obsidian and why mindmapping is such a good tool for Personal Knowledge Management. Like this post? Show your support.

You can spice up your daily journaling practice by using random prompts. The good news is that it is very easy to implement it in your Obsidian vault. In this article, I will share my approach. My solution is inspired by Journal Prompts in Roam Research by Daniel Wirtz. The list of journal prompts I share is based on the 1000 Daily Prompts recommended in Daniel's article. If you are interested in my collection of journaling approaches check out my Evergreen Note on Note-taking Strategies and Their Practical Implementations . This is where I am collecting a growing list of different personal journaling strategies.

Yesterday I completed my first "Book on a Page" sketchnote for Storyworthy  by Matthew Dicks. This article will summarize the workflow I followed.  My approach borrows heavily from Tiago Forte's Progressive Summarization method and Doug Neil's wonderful video How to Sketchnote a Book .

Storyworthy  is a book by Matthew Dicks about the craft of telling stories. This post is an experiment created over the course of three days. My ultimate goal was to create a single-page sketch note summary of Storyworthy. To achieve this, I first wrote a summary of the book using Tiago Forte's  Progressive Summarization  approach. I then created three one-page sketches for each of the main sections in the book. I finally distilled the three one-pagers into a single summary sketch - you'll find the single-page overview at the very end. Introduction Stories are personal narratives of change that others can relate to, and are shared with the purpose of connecting to other people. The book covers three topics: Finding stories to share. Crafting these to be engaging and entertaining with a long-lasting impact. Telling them to family, friends, or larger audiences.

I'm exploring ways to take Personal Knowledge Management to the next level. I'm learning to think more visually, integrating Excalidraw into my Obsidian knowledge graph. My drawings have become more than just illustrations. They are self-standing documents, interlinked with everything else in my PKM system.

Imagine a database containing the full text of all the books and publications you have ever read, plus all your reading notes with links to the source paragraphs and your text highlights in the source. It also has everything you have ever written: your journal, all the articles, books, documents, and reports. Such a database would be a powerful source of knowledge. With persistence, it is possible to build this in Obsidian . But can Obsidian handle this volume of information? This post is about my attempt to understand Obsidian's performance limits. I will present my approach and findings.

Setting the stage I am leading a project to review my company’s business strategy. I want to identify projects for next year’s business plan and to create a strong link between the strategy and our projects. This will help in storytelling with the people delivering these projects and to the executives governing the strategy. This exercise has put the gap between information and knowledge management tools I use in private and available at work in the spotlight. There are four capabilities I miss most at work: backlinks, block references, tags, and a query language to work with the information.

Over the past few weeks I have spent many hours thinking about my personal information security requirements and discussing pros and cons with others. My goal with this article is to clarify few concepts that have surfaced in these discussions. I want to help you find your way in the jungle of information security.

It has been roughly a year since I first came across Obsidian. After careful consideration trying out Tiddly Wiki, Obsidian, Roam and TheBrain, I opted for Roam. I chose Roam because of its friction-free, browser-based user interface, its product vision and the vibrant community which I was sure will drive significant innovation - and it has! After one year, I was curious to see how Obsidian has evolved. This post will walk you through my second first-impressions comparing Obsidian to Roam.

SEX IS GOOD. But as with all things, sex also has its "dark side". If you are not careful, you can get hurt. ROAM IS GOOD. I am a firm believer in Roam's vision. But as with all things... This article is about information security. While I will focus my discussion on roamresearch.com , my points are broadly relevant in today's online/digital world.

This post is about the "intrauterine" phase of project development, about that ambiguous period between the inception of an idea and the birth of a project. It is easy to overlook the importance of early project framing because problems tend to be more noticeable during project delivery and post-go-live. However, the difference between hugely successful projects and disappointments is determined by early framing. I will show you tools to improve how you frame opportunities into projects.

  I am releasing the MVP version of the Roam-Excalidraw Plugin. Over the past two weeks, I have been super focused on getting to this point. As a consequence, this post is going to be shorter and more utilitarian than usual. I had to make a choice whether to release the plugin this weekend or to write a detailed blog post. I opted for the first.

Conor ( @Conaw ) pointed me to Excalidraw last week, and I was blown away by the tool and especially about the opportunities it opens up for  Roam Research ! It is a full-featured, embeddable sketching component ready for web integration. This post will showcase key Excalidraw features and discusses some of the issues I still need to solve to complete its integration into Roam. I spent most of my free time during the week integrating Excalidraw into Roam. This article will introduce Excalidraw by showcasing its features.

Roam is like a good swiss army knife, it even has a ClojureScript development environment. I spent the past 14 days getting acquainted with {{roam/render}} . This post serves as a note-to-self, to summarize and organize what I have learned.  This post is targeted at developers and Roam hackers. If you are not in one of these camps, you will likely struggle with the content.

Taking notes is very simple. You take a piece of paper and jot down a few thoughts. That's it. But if it is this simple, why all the fuss? What makes quality note-taking so difficult?

This post is about my note-taking journey. I cover two applications in detail, TheBrain , and Roam Research . I compare the strengths and weaknesses of these with each other and with my own note-taking needs.

This post summarizes my learnings from the Roam Agile project. I present the Minimum Viable Product (MVP) version of the Agile Development Template. Here you will find the link to the Roam EDN archive containing the template, instructions for how you can get started, YouTube videos showcasing the solution, and a link to the graph I used for my project with my backlog, user stories, sprints, daily standups, customer feedback, etc.

I spent the last week working on a Roam template for Agile Product Management. My goal is to create a step by step how-to guide and a full-featured template database, that a product development team can pick up to kick-start their process using Roam. I assume that Roam will be the only task and user story management tool used by this team, and I am developing a fully self-sustained solution built 100% around Roam's capabilities.

Which are the longest paragraphs in your graph? Which pages did you edit or create last week? How many paragraphs of text do you have in your database in total? Which pages do you have under a given namesapece (e.g. meetings/)?

You are keeping your notes tidy to help your future self find relevant information. Note-taking systems offer many ways to organize information. One common feature of these is how easily they get out of hand.