Why I write book notes

The argument for reading hundreds of books is that knowledge accumulates, building up like compound interest. 

As a kid, I remember writing revision notes in an attempt to push the required knowledge into my head. Now, I compress down insights and thoughts into concise statements or directives. An idea that I picked up from Derek Sivers

If reading books is about banking the knowledge for some time in the future, then writing book notes and creating directives feels like having cash in your pocket. It’s useful now.

A process that has challenged me to slow down and consider what I’ve read. To embrace, reject, or accept another viewpoint. 

Once I’ve decided that I want to engage with an idea. Directives bring constraints. Do this. Don’t do that. A way to practice commitment to a decision. 

Nobody has to listen. There is no pressure to impress or perform. It’s on you to develop the idea and your belief in the usefulness of the knowledge you have acquired. 

The first draft helpfully named the vomit draft, gets me started with no expectation. After that, each edit and rewrite builds commitment to an idea. The challenge is to become clear and concise in my communication. Leaving no doubt in my words. 

In coaching, we ask students to learn a concept and then teach it. Poor student coaches collect knowledge in the hope it will someday be useful. Which is like collecting lego in the hope it will someday make you a good architect.

Good student coaches know they need to constantly work with the knowledge they have now.