How I Manage What I Learn: A Personal Knowledge Management System

How I Manage What I Learn: A Personal Knowledge Management System

At the heart of almost everything written here — work, leadership, creativity, communication — sits learning.

Not formal education alone. The deeper, quieter craft of becoming wiser over time: of encountering an idea, testing it against reality, and emerging with something that has actually changed how you think or work or behave.

That kind of learning does not happen by accident. It happens through systems.

Over the years, one of the most useful things I have built is a personal way of managing what I learn — not to hoard information, but to change how I think and act. This is not a perfect system. It is a lived one, iterated over years, and it continues to evolve.

What follows is how it works.

This essay can also be explored in video and audio form — or continue reading.

Why a personal system matters

The trap most people fall into is treating learning as collection.

Books accumulate. Bookmarks multiply. Tabs stay open. Courses sit unfinished. A vast and growing archive of things that were interesting enough to save, but never quite processed into anything useful.

I know this trap well because I spent years in it. My digital library was growing faster than my understanding. The act of capturing had become easier than the act of doing anything with what I had captured.

The shift came when I stopped thinking about information management and started thinking about knowledge cultivation.

A personal knowledge system is not a filing cabinet. It is a way of thinking — a set of habits that determine what you pay attention to, what you do with it, and whether it actually changes anything about how you work.

Knowledge is information in action. Anything else is storage.

The four movements

Over time my system settled into four movements, not steps — because they are not linear. They loop, overlap, and continue indefinitely.

Capture. Curate. Crunch. Contribute.

Capture: feeding the mind

Learning begins with paying attention.

Books, conversations, observations, talks, articles, ideas on a train platform — anything worth thinking about must first be caught. I capture widely, but not carelessly.

Where you gather from shapes what you become, and there is a great deal of noise available. I tend to stay close to a small number of sources I trust: a few blogs with real editorial standards, academic papers where they are accessible, and books.

Everything captured goes into a single inbox — currently a combination of digital notes and handwritten capture in a notebook. The specific tools matter less than the discipline of having a place for everything. I have tried many tools over the years; the ones that have lasted are the ones that reduced friction rather than added it.

What lands in the inbox is not knowledge yet. It is raw material.

Curate: choosing what deserves thought

Every week or so I go through what I have captured and make decisions.

Not everything deserves further attention. Curation is the first act of genuine thinking — a filter that separates the genuinely interesting from the momentarily appealing.

Three questions guide this:

Is this still interesting to me? Is this still useful? Is this worth carrying forward?

Much gets discarded here. This is not waste — it is clarity. The ideas that survive curation are the ones that deserve the more effortful work that comes next. This is also the moment for organising and tagging, making things findable when they become relevant later.

Crunch: where learning actually happens

This is the heart of the system, and the step most people skip.

Crunching is my term for turning information into understanding — and then into action. It means re-reading something slowly rather than once quickly. Comparing it with what I already know. Looking for where it confirms, extends, or contradicts my existing models. And then — critically — testing it in real situations.

Here is a concrete example. I once came across an article with a ten-step method for running more effective meetings. During curation, three of the steps seemed redundant against what I already knew — so I set those aside. Of the remaining seven, I tried them in a real meeting. Three turned out to be unnecessary in practice. One was, frankly, a small disaster that I recovered from through instinct and had no intention of repeating. That left three genuinely useful additions.

Those three got woven into my own approach to meetings. The original article's ten steps became three real improvements — tested, adapted, and absorbed. That is crunching.

I do not consider something learned until it has changed how I behave. An idea about meetings must improve an actual meeting. A model about leadership must shape how I actually lead. A new communication approach must become part of how I actually communicate. Otherwise it remains what I think of as intellectual furniture — elegant, visible, but not doing any work.

Learning that does not reach behaviour is entertainment.

Contribute: returning what is learned

Once something has been tested, adapted, and genuinely absorbed, it can be shared.

Sometimes that means writing about it here, or turning it into a talk or a course. Often it happens more quietly — through a better conversation, a sharper piece of feedback, a more useful coaching session, a decision made with more clarity.

Contribution completes the learning loop. It ensures that knowledge stays alive rather than private, and it tests your understanding in a different way — because explaining something to someone else quickly reveals the gaps in how well you actually know it.

What the system protects against

This approach is useful not just for what it produces but for what it prevents.

Three traps are common in knowledge work: collecting information instead of learning from it, mistaking memory for understanding, and confusing articulateness about a subject with actual capability in it.

I have met people who can speak fluently about meeting design, leadership, or communication — and run terrible meetings, lead poorly, and communicate badly. Information without crunching produces fluency without competence.

The system is a guard against becoming articulate but ineffective.

Keeping it useful over time

Two things determine whether a personal knowledge system stays genuinely useful or becomes another form of hoarding.

The first is pruning. Any system accumulates dross — information that seemed useful when captured but isn't, ideas that have been superseded, notes that have outlived their purpose. A regular pruning routine, removing what no longer serves, keeps the system lean enough to actually use.

The second is iteration. The specific tools I use have changed many times. The principles haven't. When something stops working, change it — but change the mechanics, not the underlying rhythm of capture, curation, crunching, and contribution. That rhythm is what makes the system work.

The system must stay simple enough to serve life, not replace it. Too many tools create friction. Clarity always beats complexity.

Learning as a lifelong practice

The more I learn, the more clearly I see how much remains. This is not discouraging — it is, on reflection, exactly right. A mind that stays genuinely curious stays genuinely open. The moment you believe you have arrived somewhere complete, growth stops.

We are always in draft form.

A personal knowledge system is not about control over information. It is about care — for how you think, how you grow, and how you might be useful to others with what you have learned.

Learning is not preparation for life. It is life itself, unfolding.

A good system helps you notice what it is teaching you.