A sample note from reading
Thinking in Systems by D. H. Meadows
I read this book when I wanted to get serious about creating a publishing "flywheel" system for lead generation. I listened to the audiobook version.
“A company can build up a larger workforce by more hiring, or it could do the same thing by reducing the rates of quitting and firing”.
Knowing this particular piece of wisdom gives an edge to the executive, but they might not think of the mental model of stocks and flows while thinking it.
But it’s good wisdom nonetheless.
It makes me think that being clever about systems might not necessarily give me new wisdom, not as a beginner at least. I might conclude something from a beginner’s grasp of systems thinking and then be blind to a bigger side-effect.
So maybe I should read this book alongside a list of rules of thumb (wisdoms condensed into maxims and aphorisms), such as Taleb’s “Bed of Procrustes”. Interesting.
Hi, I'm Pascal, and I've read
Thinking in Systems by D. H. Meadows.
I recommend this book if, before you start on your next career moves, you'd like to understand the concept of a "flywheel" in more depth, with some more rigour, scrutiny and skepticism. I was hesitating on which topic to publish about, and so abstract concepts in this book allowed me to understand what causes small consistent actions to compound (or not). I learned about the general idea of a stock and drew my own list of freelancing stocks: some are fragile and need protection, some will grow organically, some others can grow quickly with effort. It's an abstract book and my notes contain my concrete applications to freelancing.
Using ReadWith, you can read this book and get access to my reading notes, which I'll share with you as you record your own notes. It'll feel like you're in a mini reading group with me, and it's a great way to deepen your insights while reading. This package includes 44 reading notes in total, disclosed progressively.
Here's how ReadWith works: As you save your own notes about the book, my notes (up to the place you’re at in the book) will be shown to you. An entry contains both your note and progress info, and it calculates how far by percentage you are compared to other people's notes.
You shared
"It takes time to build the wood in a forest"
If I don't understand the slowness of inflows, I won't go anywhere fast with a flywheel.
This note at the top, that's the one you just added (let's say).
This one below, that's my note, made accessible because you're matching the previous note's progress (by percentage of total time).
Pascal shared
“A company can build up a larger workforce by more hiring, or it could do the same thing by reducing the rates of quitting and firing”.
Knowing this particular piece of wisdom gives an edge to the executive, but they might not think of the mental model of stocks and flows while thinking it.
But it’s good wisdom nonetheless.
It makes me think that being clever about systems might not necessarily give me new wisdom, not as a beginner at least. I might conclude something from a beginner’s grasp of systems thinking and then be blind to a bigger side-effect.
So maybe I should read this book alongside a list of rules of thumb (wisdoms condensed into maxims and aphorisms), such as Taleb’s “Bed of Procrustes”. Interesting.
I built ReadWith to read books with other people, to simulate the experience of a reading group, where everyone can get a turn to share their reaction on a passage from the book.
To read Thinking in Systems by D. H. Meadows alongside my reading notes, purchase access and you'll hear from me today or tomorrow with the next steps.
In a reading group, you get to hear other people's insights.
With ReadWith, you get that feeling of a reading group, but you read at your own pace. No need to schedule a reading session, just read when you can.
Personally, I can't wait to read other's reactions, so this system gets me to read and contribute my thoughts more frequently, setting a good natural reading pace.
You won't be able to see notes further than your place in the book, so there's no risk of spoilers. No disconnect between what you're reading (in the book), and what you've heard about the book, because we'll both be reacting to the same passages.
Why this book and not another book you have on your "to read" list? I found that a reading group, even reading a book with just another person, makes the process of reading that much more enjoyable and meaningful. It's the alone part that makes reading a book a little bit of a chore. But when reading a book alongside someone else, it's a little bit different. You develop insights better, you remember the lessons better, you turn your reading into a little more of an investment.
The price only includes access to the reading notes. Here's my pitch however: books are expensive right? Their price is low compared to, say, an online course, but their true cost is in the time you'll be putting in to read it, and the cost of changing your mind. I'm confident ReadWith will help reduce both those non-price costs for you. You'll read the book, you'll learn the insights. Tell you what, let me make it interesting for you: you'll find it a bargain or your money back.
I find that the best books are the ones worth re-reading. And so, if you'd like to re-read it alongside my reading notes, (or in a future update maybe, alongside your own private reading notes, I've tried it, it's great), then consider using ReadWith for this book.
"Ok, I'm ready to start reading Thinking in Systems with you Pascal."
Yep, besides Thinking in Systems by D. H. Meadows, I've been recording my reading notes for other books (See my profile page). I only put reading notes for sale for the books I'd recommend, which means I only publish my reading notes for a few books a year. I'll be announcing new books soon.
I'll also be sharing about new features I'm building for ReadWith, and so here's where you can sign up to stay in the loop: