Note XXIV - Why I Write These Notes

To stop carrying thoughts that should already be finished

If you enjoy observations like this from 150+ countries, you can subscribe here.

I didn’t start writing because I had something important to say. It came from the opposite direction, from the feeling that too many things were staying unfinished in my head, without ever becoming clear enough to leave. Not big ideas or clean insights, but fragments that kept returning in slightly different forms. A situation that felt off without knowing exactly why, a conversation that lingered longer than it should have, patterns that showed up repeatedly but were never followed all the way through. None of it urgent, none of it dramatic, but none of it gone either.

For a long time, I treated everything the same way I usually do. I built systems. Anything that requires action goes somewhere structured, visible, and external. Tasks sit in Trello, broken down far enough that I don’t have to think about them until they matter. There are more items on that board than most people would tolerate, but that’s the point - they don’t live in my head anymore. The same goes for reminders. Birthdays, recurring obligations, small things that would otherwise occupy attention just because I might forget them. They run quietly in the background, and I don’t have to carry them around.

That works well for actions. It removes pressure and creates a sense of control. But it doesn’t work for thoughts.

There’s no place where you can store something like this bothered me and I don’t fully understand why, or this keeps happening but I haven’t figured out what it means yet. Those things don’t have a next step, so they don’t fit into any system. They stay where they are, and over time they accumulate in a way that doesn’t feel heavy at first, but slowly fills the background until it becomes normal to carry them.

The default was simple. Something happens, I react, and I move on. The next thing replaces it, then the next one, and whatever wasn’t fully processed just gets pushed forward. It doesn’t disappear, it just loses visibility. After a while, that creates a constant, low-level movement in the background. Nothing is clearly unresolved, but nothing is properly finished either. It’s a kind of mental residue that doesn’t interrupt you directly, but never fully leaves.

Writing was the first thing that actually interrupted that pattern. Not as a habit or a discipline, and definitely not as something I planned to publish, but as a way to take one of those fragments and stay with it longer than I normally would. The rule is simple but uncomfortable in practice. You take one thought, one situation, one reaction, and you don’t move on. You follow it properly. What actually happened, what part of it matters, what part of it doesn’t, where it connects to something else, and whether it holds once you stop reacting to it and start looking at it more calmly.

That process takes longer than expected, mostly because there is always an easier way out. You can switch to something else, you can call it “good enough,” you can leave it slightly vague and move on. Writing removes that option. Either the thought becomes clear enough to stand on its own, or it collapses because it was never really solid. Both outcomes are useful, but they require staying with it longer than feels natural.

Once it’s written, something changes. It’s no longer something that needs to be carried around. It exists outside, in a form that doesn’t require constant revisiting.

You can come back to it if you want to, but you don’t have to keep it active in your head. That’s the part that matters. Not the act of writing itself, but the reduction that follows. Something that was previously moving in the background is now still.

Before this, almost everything stayed slightly open. Conversations, impressions, reactions, ideas - they all moved forward into the next thing without ever being properly closed. Over time, that created a kind of noise that I didn’t recognize as noise, because it was always there. Writing gave me a way to stop that. You take something that is still unclear, you stay with it longer than you usually would, you give it a form, and then you leave it there. It doesn’t come back in the same way.

There was another layer to this in the beginning that had less to do with clarity and more to do with perception. I had the feeling that a lot of what I was doing wasn’t really understood from the outside. Not in a dramatic sense, but in a very predictable one. People see one visible part and assume the rest doesn’t exist. If you’ve been successful in one area, they assume everything else is surface-level. If you travel a lot, they assume you don’t build anything. If you work in demanding environments, they assume you don’t cook, don’t fix things, don’t take care of details yourself.

At the same time, things that go well are often explained away as luck. As if consistency across different areas happens by coincidence, or as if it needs a single visible specialty to be taken seriously. Being broadly capable doesn’t have a clear category. It doesn’t get highlighted in the same way, and it doesn’t naturally attract attention. There is no obvious stage for it.

That used to bother me more than I would admit. Not because I needed validation, but because the picture felt incomplete in a way that I couldn’t correct directly.

The first instinct was to create something larger, something structured enough to show it properly. That’s where the idea for a book came from. A way to make it visible without relying on someone else to interpret it.

What changed over time is that this stopped being the main driver. Not because the observation was wrong, but because it doesn’t solve the underlying issue. Being seen differently doesn’t reduce internal noise. It doesn’t clarify anything on its own. It just shifts the perception from the outside.

Understanding does something else. It removes friction internally. And writing turned out to be the most direct way to get there. Not as a performance, not as a way to present something, but as a process you go through. You take something that isn’t finished, you stay with it, and you don’t leave until it holds. That’s the only requirement.

Everything else happens around it. If someone reads it and recognizes something in it, that’s useful. If it creates a connection, that’s even better. But none of that is necessary for it to work. The primary effect happens before that. It’s the moment where something that used to sit in your head without a clear shape becomes defined enough that it no longer needs to stay there.

Once you’ve done that often enough, you start to notice how much of what feels like thinking is actually just unfinished loops. Things that don’t need more input, more information, or more perspective, but simply an end. They need to be taken seriously once, followed properly, and then closed.

That’s what these notes are for.

---

If you want to receive future field reports
and notes from 150+ countries, you can subscribe below.