Everybody talks about time management.

Very few people talk about information management.

But in knowledge work, information management is usually the real bottleneck. A bad calendar is annoying. A bad system for capturing and reconnecting ideas will quietly make you worse at learning, writing, and thinking.

That has become more obvious to me the more I work on technical problems. A lot of confusion at work is not really about intelligence or effort. It is about losing half-formed ideas before they mature. You read something useful, hear a good explanation in a meeting, or notice an edge case while building, and then it disappears because you did not give it a place to live.

That is one reason I started writing here in the first place. I do not want every useful thing I learn to stay trapped in a Slack thread, a half-remembered debugging session, or a note that only made sense for ten minutes. I wrote about the setup side when I first stood up this blog with Jekyll and GitHub Pages, but the real value is not the site. It is the habit of turning loose ideas into something reusable.

That is why I like bottom-up note taking more than rigid top-down organization.

Top-down systems feel neat at first. You make folders, categories, and hierarchies. But real ideas do not respect those boundaries. One note about testing might also be a note about architecture. A note about learning might also become a note about writing. If the system forces you to pick one bucket too early, you either duplicate notes or bury them.

Bottom-up note taking works better for how ideas actually grow.

You start with one clear note. Then you connect it to other notes when the relationship becomes obvious. Over time the structure emerges from the connections instead of being imposed up front. That is a much better match for how understanding develops in real life.

The habit that matters most is simple:

write down what you do not understand.

If I am in a meeting, reading docs, or building something and I hit confusion, that is usually the moment worth capturing. Not because the note is instantly brilliant, but because confusion is often the edge of learning. If I can explain even part of the issue in my own words, I have created a handle I can come back to later.

That is what turns random exposure into accumulated understanding.

It also changes how I work. When I wrote down the Vitest mocking patterns I keep forgetting, the point was not to sound like I had mastered testing. The point was the opposite. I was tired of solving the same small problems twice, so I wanted a place where the next version of me could start a little further ahead.

A good information system does a few things:

  • it captures ideas before they disappear
  • it forces you to restate things in your own words
  • it makes notes easy to reconnect later
  • it lets structure emerge from repeated use instead of premature organization

I think a lot of people try to fix knowledge-work problems with more productivity systems when what they really need is a better memory system.

Your calendar helps you decide when to work.

Your notes help you avoid starting from zero every time.

That second problem is the one that compounds.