If I look honestly at where all of this started, not just Amethyst Mapper, not just this new phase of building tools for other people, but the whole way I learned to work with my own brain instead of constantly fighting it, then it starts with mind mapping.
I do not think in straight lines. I never did, and I do not think I ever will. My thoughts do not come one after another like soldiers in a queue, nice and organized, waiting politely for their turn. They come as fragments, side roads, associations, unfinished tasks, images, fears, ideas, memories, patterns, things I forgot, things I suddenly remember, things that seem urgent for no reason, and things that actually are urgent but are buried under ten other signals screaming just as loudly. For a long time I called that chaos, because what else are you supposed to call it when your own head feels louder than the world around you. But with time I understood that it is not always chaos in the simple sense. Very often it is just too much structure trying to exist at once without a place to land.
That difference changed a lot for me, because if the problem is not that my brain produces bad material, but that it produces too much material at the same time, then the answer is not to suppress it, shame it, or force it into somebody else’s linear system. The answer is to catch it, spread it out, look at it, and give it shape.
That is what mind mapping did for me.
It started on paper
I started more than a decade ago, with pen and paper, not software, and I think that matters more than it may seem. A blank sheet and a pen do not try to impress you. They do not ask you to create an account, they do not wave ten premium plans in your face, they do not bury you under templates, hundreds of themes and productivity fantasies. They simply allow you to put something in the middle and begin. One word. One idea. One task. One fear. One project. Then the second thing comes, then the third, then a branch appears, then another one, then suddenly two things that felt disconnected start looking like they belong to the same system. Paper lets you think with your hands, and for someone like me that is not some romantic metaphor, it is practical. When my hands participate, my mind starts trusting the process more.
Over the years I tried digital tools too, of course I did, because in theory mind mapping software should have been perfect for me. Infinite space, easy editing, moving things around, saving, exporting, improving, all of that should have made digital mapping even better than paper. But most of those tools lost me very quickly, and almost always for the same reason. They had too much noise. Too many features, too many settings, too many views, too many decisions before I could even begin doing the one thing I came there to do, which was to take the mess from my head and turn it into structure. A lot of those apps felt like they were built by people who loved product complexity more than they loved the human being trying to think.
The process is the point
This is where my philosophy really begins, because I think most people misunderstand what mind mapping actually is. They look at the final map and treat it like the product, like the visual artifact is the point. A nice diagram, a summary, something polished, something finished, something you export, print, maybe show someone. I think that is backwards. The final map matters, yes, but not nearly as much as the process of making it. The value of mind mapping is not mainly in what you end up with, but in what your brain has to do while you are building it.
That is the whole thing for me.
What matters, happens in between an empty canvas and a ready mind map.
When you create a node, then add a child node, then connect one branch with another, then decide this part belongs in a group, then change a word because the label was too vague, then move an idea because now you understand it belongs somewhere else, then assign color to create hierarchy, then realize two branches are actually parts of the same pattern, all of that is not decoration. That is cognition happening outside the skull in a form you can see and work with. You are not making a pretty poster. You are participating in the organization of your own mind, and that participation is exactly why the method works.
AI should help you begin
This is also why I think many AI approaches to productivity completely miss the point. They assume the highest form of help is to take your input and give you a finished output, something polished and complete, so you can skip the work and move straight to the result. Sometimes that is useful, I am not against AI, not at all, obviously, but in mind mapping it can become a trap. If AI takes your mental mess and hands you a perfect, finished structure that you never had to shape, then maybe you got a neat output, but you lost the most important part of the exercise. You lost the friction that creates understanding. You lost the interaction that makes the structure stay in memory. You lost the small decisions that turn "a generated map" into "my map."
That is why I do not want AI to replace the mapping process. I want it to support the process.
This difference is not cosmetic. It is the whole philosophy behind Mapper Plus.
Take Text To Map, for example. On the surface it looks like a feature that generates a map from a block of text, and yes, technically that is true. But the purpose is not, and never was, to let somebody vomit text into a machine and receive back a final artifact so they can say "great, done" and move on. The purpose is to help when the brain is too overloaded to even enter the process. When everything comes out as one massive dump, notes, transcript, thoughts, fragments, panic, ideas, plans, there is often no obvious first step. That is where people freeze, not because they are lazy or incapable, but because the amount of mental material is too dense to manually shape from the first second. Text To Map is there to open the door. It gives you a first structure, a draft, a way into the canvas. Then the real work begins, because then you start deleting, renaming, regrouping, moving, elaborating, and turning that rough AI-assisted starting point into something that actually reflects the way your mind understands the problem.
So yes, AI helps, but the help is not "here is your final map, goodbye." The help is "here, now you can begin."
The same goes for Expand Selected Node, which for me is one of those small features that sounds minor until you actually know what it is like to sit inside a process and suddenly hit a wall. That wall is familiar to me. You are working on a branch, you know there is more there, you feel that the thought is alive, but the next step does not come. The branch stalls. Your brain freezes on that one point, and once that happens the whole session is in danger, because one blocked branch can be enough to kick you out of the process completely. Expand Selected Node exists for that exact moment. It is not there to think for you, and it is definitely not there to dictate what the map should become. It is there to offer a few possible next child nodes so your mind gets traction again. Sometimes that is all you need, one suggestion, one angle, one nudge, and suddenly the machine starts moving again. That is not replacing cognition. That is protecting it.
Another thing people underestimate is how much the physical interaction with a map matters. Moving nodes matters. Choosing colors matters. Grouping concepts matters. Renaming things matters. Reshaping hierarchy matters. Even the act of dragging something from one side of the canvas to another matters. These are not little cosmetic extras for people who like visuals. These actions are part of how the brain digests what it is looking at. They create memory. They create ownership. They make the structure feel lived in instead of imposed from outside. When you participate in making the map, the map starts participating in the way you think back.
That is why I always come back to the same point: a useful mind map is not one that looks impressive, it is one that helps you think, decide, remember, explain, plan, or act. That is enough. More than enough, actually. We have too many tools already that look impressive and do not help anybody survive a real Tuesday.
Why simplicity matters
This is also why simplicity became so important to me. A lot of software people seem to think simplicity means a lack of ambition, as if the more features you add, the more serious your product becomes. I think the opposite is often true. If you really understand the problem, you start cutting. You remove noise. You stop making the user manage your product and you start making the product carry its own weight. For someone with AuDHD, that difference is not luxury, it is the line between a helpful tool and another thing that drains cognitive energy before the work even starts. So when I say Amethyst Mapper is intentionally simple, I do not mean it is small because I ran out of ideas. I mean it is focused because I know exactly what too much complexity costs.
From personal method to product
Mind mapping started more than an app for me. It started a method, and that method slowly turned into a way of designing other methods. Once I saw how much of my own cognition could be supported by systems that respected how I actually think, I could not unsee it. That is part of what this new blog is going to be about. Not neurodiversity as a fashionable topic, not generic self-help, and definitely not polished wisdom written from a distance, but practical things I am inventing, testing, breaking, rebuilding, and using on myself to function better with my AuDHD brain. Some of those things may stay private methods. Some of them will become products. Amethyst Mapper is the first clear example of that, because it did not begin as a business concept. It began as a need.
And honestly, that is probably the best place a useful tool can begin.
Mind mapping gave me a way to take what felt like mental chaos and reveal the structure hidden inside it. It gave me a way to participate in my own thinking instead of drowning in it. It gave me a method that did not ask me to become someone else first. And because of that, it did not just help me organize projects. It helped me understand that many of the things I thought were just strange personal coping mechanisms were actually methods with real value, methods that might help other people too if they were shaped properly.
This is why this article had to be the first one.
Because before there was Amethyst Mapper, before there were beta testers, before there were new applications in my head waiting to be built, there was a map, and before there was a map, there was the simple need to take what was happening inside me and make it visible enough to work with.
Everything else came later.