Now’s the part of the course where you think.
I want you to reflect on two things.
First, I want you to reflect on this third lecture about systems thinking. Particularly, I want you to think whether you agree with the title of this episode. Do you agree that complex problems are solved by complex systems?
Can you find counter example of that?
Second is a pair of complimentary questions.
Have you ever encountered a complex problem and did not know how to solve it?
And
Have you ever encountered a complex problem that you solved by changing just one thing?
The goal here is to get some anecdotes that highlight systems thinking. I want to make make something clear though. Sometimes, all you need is a simple fix, and trying complex solutions might not lead anywhere. Using systems thinking doesn't mean you'll solve all problems all the time. It just means that you're more likely to get back to balance and harmony.
So these questions will be posted online and I invite you to contribute to the conversation, or just strike a conversation with a friend.
Now, let's look at the project part of the course.
Again, sit down for 15 minutes with no distractions with the same sheet of paper with the changes you want to see in you and the world and the first principles you found within those things.
The prompt of this lecture is to try to spot if any of the things are related to a system. Try to think if the system is complex or simple or chaotic. Try to see if you can picture the structure as a network, and identify the processes. Try to identify the function of the system. Try to use your systems lens.
Once your ideas slow down, try to think of anything else you can spot that is complex system.
Don't overthink it. You're not an expert in systems thinking. It's okay if you make mistakes or you don't fully understand and you don't get the right answer. The goal again is to start thinking about systems thinking and building awareness. Don't try to cheat by using AI.
So let's recap:
Discuss the title of the episode.
Then discuss the pair of question, those being:
Have you ever encountered a complex problem and did not know how to solve it?
And
Have you ever encountered a complex problem that you solved by changing just one thing?
Then, do the class project by identifying systems within the things you want to improve.
And before I leave you, let me ask one last question: Can you spot anything about this course that reflects systems thinking?
I invite you to pause and take the think to think it through.
The organization of each episode uses systems thinking. They follow the same building blocks, I even say the same things from one episode to the next. It makes it easier for me to manage, and easier for you to understand and remember.
Also, the teachings are interconnected. Everything being a system, as I mentioned, is a first principle. And as we'll continue, I'll be mentioning the different ways of thinking in subsequent episodes.
Then, the course is organized into a system as well, aimed to be more than the sum of its parts. We have the audio here, then we have a forum for discussion, and then I present to you, the website. It's been on since the beginning, but only now I'm mentioning it. The website contains the scripts for all the episodes. Then it also contains the ideas behind those episodes in form of links.
The website was built using a network structure. In fact, this website is a digital garden that I made using Obsidian - a free note-taking app that allows you to link notes together. I remember when I first started to use the app, I was doing it wrong. I was trying to categorize notes, and create big descriptions for topics. That's what I though note-taking was about. I've been reading "How to take smart notes", but Sonke Ahrens, and it changed how I use the app now. It's based on Niklas Luhmann's system of a slip box. I will let you explore it on your own if you're interested.
But the point here is that I am building a network structure for my notes, and they are all on that website. On it, there are two types of notes. First, Atomic notes. Those are short ideas. They are meant to be short, that's why they're called atomic. I link those together to then be able to go from one to the other easily. As my network of notes grow, instead of it becoming messy and requiring a lot of maintenance, it becomes more valuable as I can find new connections.
Then I have project notes. Those are things that uses the atomic notes for purpose. Like this script.
But anyways, I'll let you explore the website. It's called thebookofwhys.com. Whys spelled W-H-Y-S. The book of whys.
Thank you for listening, it really warms my heart that some of you are taking this course.
I welcome any form of feedback.
And as always, a mind is a precious thing to waste, therefore, stay hungry, stay foolish.