Mind Mapping: visualizing a topic

Meta Info

Mind Mapping: visualizing a topic
Author: Stijn Dejongh
Published on: 2023-09-05 00:00:00 +0000 UTC
Ammerse Values :
A: Mi: M: E: R: S: Ex:

Problem Statement

You are learning a wealth of new information, but find it difficult to keep an overview of what you know or how certain things relate to other knowledge you have.


  • Organize your understanding of a certain topic
  • Force yourself to add structure to your thoughts
  • Allow for train-of-thought note-taking, while keeping track of the whole

Contextual forces

What is this? These describe factors at play that influence the outcome of the practice. They are not necessarily good or bad, but they are important to be aware of. Some contextual forces are enablers, giving the practice a higher chance of being useful. Others are deterrents, making the practice less useful in your given context.


  • You are comfortable being confronted with your own knowledge gaps
  • Having non-complete, non-final representation of your knowledge is okay
  • Modern technology makes it easy to create mind maps


  • Mind maps are relatively high effort
  • The resulting visual artefact of a mind mapping exercise rapidly becomes stale
  • Not knowing what concept to attach something to can lead to frustration or abandoning of the mind map


Create a mind map that structure the core ideas of a certain domain or piece of work. As a spiders web, the mind map starts by putting a central concept or question at the centre of the page. You then attach words to this central theme, as they appear in your head.

Make sure not to put too much effort into your mind map, the act of mapping is where the value lies. You will soon realize that as your understanding grows, your map will no longer be accurate. At this point, just create a new one. If you want to solidify your newfound knowledge, repeat this process until you are satisfied.

If you work digitally, you can keep your mind maps up to date a bit more easily as you will not run into spacing issues as fast. Though, if your sketch is not updated for a long time, consider ditching or revisiting it, as it likely lost most of its value.

tip: Do not focus on the result too much. The drawing you end up with is secondary to the process of creating it. Most mind maps are used as a temporary tool to organize your thoughts, or help you understand a concept in a broader way. The drawing is less important than the clarity of mind you gain by creating it.


  • Visualizations are a tremendous helps in remembering facts. Popular culture is filled with the idea of “mind palaces”, which is a technique used by people who display extraordinary capabilities or short-term memory storage.
  • We are good at thinking creatively, but our recollection is often times flawed. This leads us to forget about certain aspects
  • Not knowing what something relates to makes it harder to remember facts.
  • Humans prefer to think in structures, it has been shown that structuring a text or idea helps you refine the knowledge.


Mind-mapping the concepts and intent of this publication

While preparing to write this publication, I considered what knowledge a software developer should have so they are equipped to handle most challenges. With “handling most challenges”, I do not mean the developer will be able to draw upon a fixed list of existing solutions. Rather that they can combine the information they already have, and to come up with of a way of resolving the issue at hand. This is what I came up with as a general structure, which you can see reflected in how this work has been structured.

This map was made digitally by using PlantUml. This is a text-based graphing language, that you can play with on their online editor. The main advantage here is that you can move quickly (provided your typing speed is up to par). As the syntax is very simple, the brain-to-screen barrier is quite low. Having a digital copy of your mind map around can come in handy if you want to update it later on.

+ Dev knowledge
-- Learning
--- Knowledge vs Beliefs
--- Styles
--- Biases_mindmap-Software_developer_learning_path
--- Techniques
---- Empiricism
---- Exploration
--- Knowledge portfolio
---- Directed learning
---- Finding gaps