Systems Thinking Chapter 6: A System of Learning
The book is called “Learning Systems Thinking.” We talked about systems. We talked about thinking. Chapter 6 is about the third word. Learning.
And not the kind you imagine. Not classrooms and certification exams. Not whiteboard interviews. Diana means generative learning. The kind that actually increases your capacity to synthesize knowledge and experience. The kind that makes you better at dealing with complex stuff.
From Data to Wisdom
Diana walks us through a progression: data, information, knowledge, wisdom.
Data is raw facts. “I was born on April 22nd.” Cold, simple, just a fact.
Information gives data context. “My mother was young, it was a late April snowstorm, and it would later become Earth Day.” Now you are imagining something. Making inferences without a photo.
Knowledge is trickier. Larry Prusak calls it a “fluid mix of framed experience, values, contextual information, expert insight and grounded intuition.” Knowledge is not facts stacked together. It is experience and reasoning mixed with facts to create something useful.
Wisdom? Russell Ackoff says it is “the ability to increase effectiveness.” Knowing what to do with your knowledge. Here is the paradox: you need wisdom to recognize wisdom. Systems thinking is full of these loops.
There is also understanding, a layer between knowledge and wisdom. Understanding is knowing WHY the knowledge matters. Not just having it, but knowing when and where to use it.
Knowledge Stock vs Knowledge Flow
This was my favorite part of the chapter. Diana introduces two concepts: knowledge stock and knowledge flow.
Knowledge stock is what you know. All the JavaScript frameworks in your head. All the design patterns. All the debugging tricks. A “10x developer” is basically someone with huge knowledge stock. They know a lot and they can apply it fast.
Knowledge flow is different. It is your ability to transfer knowledge between people. To help others grow. To evolve your own knowledge when paradigms shift. To synthesize experience in ways that generate real impact.
In tech, we worship knowledge stock. We hire for it, we interview for it, we promote for it. But Larry Prusak lists “emphasizing knowledge stock to the detriment of knowledge flow” as one of the 11 common mistakes organizations make.
Think about it. The person who knows everything but cannot explain it to the team. The architect who builds perfect systems but nobody understands why. That is stock without flow. Learning, Diana says, is increasing your capacity for knowledge flow.
She gives a great metaphor. Information is a recipe. Knowledge is a cook. Wisdom is a chef. A cook follows instructions. A chef understands food deeply enough to create something new. Your goal is not to become a “flambe developer” who only knows one trick. Your goal is to do good things with code, sometimes by setting things on fire.
A Learning-Driven Career
Diana shares her own story. Twenty years ago she downloaded Drupal, got curious, found a client, kept learning. A few years later she was engineering lead at a top consultancy. Career built on constant learning, not on a fixed set of skills learned once.
She makes an interesting observation. Passion for learning is not common among technologists anymore. Most of us were trained to meet external expectations. Get the grade. Pass the exam. Get the job. Actual curiosity got pushed to after-hours hobbies.
Systems thinking needs internal motivation. There is no way to think in systems without developing personal mastery.
Four Types of Learning Activities
Diana outlines four activities for learning anything. She uses three characters throughout: a chef, a systems architect, and a JavaScript developer.
Generate Artifacts. Make stuff. Write code, build models, create documents. Moving ideas from your mind into concrete form is the most impactful learning practice. Documentation is not busywork. It is knowledge flow in action.
Observe and Inquire. Watch how things work. Ask questions. The questions you generate are more valuable than the answers you find. Read code made by others. Pair program. Do EventStorming with a group.
Synthesize. Read books, watch talks, take courses. But synthesizing is different from accumulating information. You are looking for patterns and core concepts. Thinking critically, not just storing data.
Experience. Apply what you learn to real problems. In real life, you are not just implementing Kafka streams. You are discovering leverage points, building teams, serving customers. Experience reveals your strengths and weaknesses.
Learning Outcomes for Systems Thinkers
Traditional learning measures your knowledge stock. Can you pass the exam? Systems thinking learning measures something harder. Can you actually solve real problems? Can you discern when to use Python and then deliver the solution?
Diana lists seven outcomes to aim for:
- Shift perspective. Look at things from multiple points of view.
- Tolerate ambiguity. There is rarely one right answer. Things change.
- Understand context. How does your subject depend on where it lives?
- Identify patterns. See how events over time form behaviors.
- Create boundaries without reductionism. Like how the Dewey Decimal System turns a pile of books into a library.
- Think critically. Recognize assumptions and logical fallacies.
- Develop interpersonal skills. Thinking well together is a top priority.
She compares concepts to Lego bricks. Learning expands the number of bricks you have. It improves your ability to build new shapes. And it helps you see which bricks are missing.
Feedback Loops and Learning Partners
Getting feedback on your learning is important. But Diana warns that most people can hinder rather than help. You share something new and get aggressive criticism or impatient judgment. Or someone is just mean.
You need learning partners. People who help you do hard things, not knock you down. When you ask for feedback, be specific. Not “what do you think?” but “did you trip over anything?” or “what about this is not strong enough yet?” Vague requests get vague responses. “This is good!” does not help you make it gooder. (Her word, not mine. I like it.)
Learning Never Ends
Diana pushes back against the idea that learning is for young people. In tech, there is a bias toward people under 35. We think learning happens in your 20s, then you apply it for 40 years.
Nonsense. Learning is like breathing. You do it forever. She has pivoted three times in her adult life.
She shares something personal. Until age 30, her focus was theater. She never made it to Broadway. But five skills from theater made her tech career: public speaking, self-awareness, improvisation, thinking about backstory (what is unseen beneath the surface), and willingness to risk looking foolish. Everything is interrelated.
My Take
The stock vs flow distinction is something I wish someone explained to me 15 years ago. I spent years building knowledge stock, collecting certifications, mastering tools. The real breakthroughs came when I started sharing what I knew. Teaching others. Writing things down. That is when learning became alive instead of just data stored in my head.