Reading a book is not the same as owning it

For most of my life I read the way most busy people read. A book would change how I thought for about a week. Then work would fill the space again, and a month later I could tell you the title and one idea, maybe two.

That is not a reading problem. It is a systems problem. Reading puts ideas in front of you. Nothing in the act of reading moves them into the place where your decisions are made.

So I stopped treating reading as an activity and started treating it as a production line. The output is not “books finished.” The output is decision rules I use on Monday morning.

The line has four stations

Selection. I keep a numbered list of the books I want to work through, currently about a hundred. Every title earns its place against the five areas of my life I care most about: career, capital, personal growth, health and family. The numbers are permanent. Book 01 is always Book 01, which means my notes, files and audio reviews can all point at the same thing.

Analysis. Every book goes through the same seven questions. What are the core ideas? Why was it written, and what was the world like then? Where is it strong and where is it weak? How does it apply today to leadership, family and money? Which few lines are worth remembering, and what do they mean in plain words? How does it compare with people thinking about the same problem now? And finally, what would I actually do differently?

A fixed template matters more than it sounds. When every book answers the same questions, books start talking to each other. I can lay three books on decision-making side by side and see where they agree.

Archive. Each analysis is saved as a document under its number, in one place. I use AI tools to help with the first pass of the analysis, the way I’d use a capable research assistant. The judgment calls, the disagreements and the “what I’d do differently” are mine.

Review. Ideas fade unless you meet them again. I turn each analysis into an audio review I can listen to on a run or a commute. Hearing a book’s argument a second time, a few weeks later, is when most of it finally sticks.

People are books too

The same line runs on people. I study the lives of leaders whose decisions I admire, a few each week. The question I bring to each one is narrow on purpose. I don’t ask what they did. I ask what their operating rules were: what they refused to do, how they made hard calls, what they repeated for decades.

What someone did depends on their era and luck. Their rules often travel. Morris Chang’s refusal to compete with his own customers is a strategy you can use in a dozen industries. Ray Dalio’s habit of writing down why he made a decision, before he knows the outcome, works for anyone.

The step most people skip

The hardest part of the line is the last inch: rewriting someone else’s idea as your own rule, in your own words, attached to a real situation.

Here is one example. The E-Myth Revisited argues that most small businesses fail because the founder keeps doing the technical work instead of building the business. That is an insight. It only became useful to me when I rewrote it as a question I ask myself every week: “Is this a technician reaction or a capital allocator decision?” When I catch myself fixing something personally that a system should fix, that question is the alarm.

An idea becomes yours when you can name the moment it should fire.

A version you can start with this weekend

You don’t need my whole setup. Three steps cover most of the value:

1. Use one template for every book. Five questions is enough. Write the answers within a week of finishing.
2. End every set of notes with one rule. Phrase it as something you will do or ask, and name the situation that triggers it.
3. Meet the idea again. Reread your notes, or listen to them, a month later. Keep the rules that survived. Drop the ones that didn’t.

Over a year, that is a small personal library of rules you have tested. Over ten years, it starts to look like judgment.