Something that struck me listening to this episode is that Tiago, @MacSparky and @mikeschmitz all seem to have a similar, fairly narrow concept of how and why to take notes on books. The bit that really raised my eyebrows was when they said taking notes on the book should only add 5-10% to the time you spent reading it, but as the podcast went on this singe point of view on notetaking came up in other ways as well. The emphasis on distilling and only capturing a small number of concepts that would be most useful to future you, for instance.
That’s a great approach for the kind of work the three of them do, reading productivity/philosophy type books with an eye to incorporating ideas into their own systems (and their future writing/podcasting on the subject). However, there are lots of other reasons to take notes and some of those are going to demand very different techniques. For instance, when I’ve taken notes on detailed technical subjects it takes far longer and captures much more. As part of my ongoing career change I’ve been reading books on whitewater rafting and I’m sure that my notetaking on the river hydraulics chapter took much longer than it would have just reading the chapter straight through.
That’s not even touching on the fact that all this seems to be very focused on taking notes on books and other written material, as opposed to in-person learning, or notes to document what you’ve done and how, or factual notes for future reference (for stuff that’s not available via Google), etc.