
Sign up to save your podcasts
Or


Problems that keep coming back usually come from the structure around the people, not the people themselves. This book gives managers and leaders tools such as the Iceberg Model and system maps for finding that structure.
In Chapter Five, we dive into how quick fixes can often backfire in complex systems. Analog Devices implemented a comprehensive Total Quality Management (T-Q-M) program that dramatically improved efficiency and quality metrics but inadvertently caused significant financial issues. The T-Q-M improvements were real, yet the standard cost-accounting system penalized the company for its own success by treating increased efficiency as excess capacity, leading to layoffs and reduced morale among employees who had bought into continuous improvement efforts.
The MIT researchers John Sterman, Nelson Repenning, and Fred Kofman meticulously traced this phenomenon using a simulation model. Their analysis revealed how an immediate visible benefit (quality improvements) masked delayed negative consequences (financial crises). This pattern is known as "Fixes That Fail" in systems thinking—a common trap where short-term gains overshadow long-term risks.
The root cause lies partly in human psychology: hyperbolic discounting makes us overvalue immediate relief while underestimating future costs. Escalating commitment means once a fix starts showing success, the organization becomes less likely to critically assess potential side effects. This chapter is crucial for understanding how even sophisticated organizations can fall into such traps.
Before implementing any quick fix, it's essential to ask: What problem will this relieve immediately? And what part of the system might absorb that relief in unexpected ways?
Chapters:
0:00 Intro
0:20 Chapter Five: When Quick Fixes Make Problems Worse
4:24 Naming the Pattern
6:17 Why This Trap Is So Easy to Walk Into?
9:38 Practice: Four Questions Before You Apply a Fix
13:13 Chapter Summary
14:59 Outro
Systems Thinking for Work by Albert Rutherford: Chapter 5, an audiobook preview.
The release date will be announced. This preview is shared with permission and is available on this channel for a limited time. It will come down when the audiobook is released.
Audiobook details: https://www.amazon.com/dp/B0HMDJK87Z
#Podcast #YouTube #BookClub
The Wright brothers’ journey to flight began with a simple letter in 1899. Wilbur wrote to the Smithsonian asking for guidance on what to read about flying machines. The reply pointed him and his brother Orville towards valuable resources that would shape their two-year project loop: Try → Get Feedback → Find the Error → Adjust → Try Again. This method is now scaled down into a practical "30-Day Build," focusing on one real project, aiming for a visible outcome, and iterating weekly.
We delve deeper into how this method works today. Choose your own project with a specific goal and deadline, make an initial attempt within the first week of starting, get feedback from peers or customers, identify what went wrong, tweak it slightly, and try again next week. This loop not only accelerates learning but ensures each effort is grounded in real-world outcomes.
Butler's study showed that repeated quizzes with feedback enhance recall significantly—a principle reinforced by Dyson’s 5,127 prototypes over five years. Each prototype answered a question the previous one raised. Your project needs a similar iterative process: try something new each week and observe how it performs against your goal. This method encourages you to adjust based on tangible results rather than theoretical knowledge.
For those stuck in copying mode, making that first original change can be daunting but essential for true learning. Start by asking someone who knows more to critique your work, whether a customer or a mentor. Each iteration should focus on one variable at a time so you can pinpoint what works and what doesn’t. This approach ensures your efforts are focused and effective.
Remember, real-world feedback is key. Ask an honest customer or a knowledgeable peer for input regularly. Push your AI tools to critique rather than generate work. The goal is to build skills by working through problems firsthand, making each mistake count as part of the learning journey. So pick your project today, set your number and date, make that first attempt within seven days, and let the feedback loop begin.
#non-fiction
Chapters:
0:00 Intro
0:12 Chapter 6: Learn by Building
4:10 Studying Feels Like Progress
5:36 Why Making Beats Reading
7:44 Turn the Light On: One Error, One Change, Every Week
13:26 Size the Build
16:25 Use AI Like a Sparring Partner
18:16 Ben’s Thirty Days
22:16 Chapter Summary
23:14 Try This Week
25:15 Outro
You don't have to be the best at one thing. You become rare by combining a handful of solid skills. This book lays out a four-step method for doing it: See It, Stack It, Build It, Prove It.
Become One of One by Peter Hollins: Chapter 6, an audiobook preview.
The release date will be announced. This preview is shared with permission and is available on this channel for a limited time. It will come down when the audiobook is released.
Audiobook details: https://www.amazon.com/dp/B0HM2TLJRZ
In this chapter, we delve into how creating a Proof-of-Stack Page can transform your job search. This page is designed to show the outcome of two or more skills you combine to achieve something tangible and valuable. It's not just about listing your skills but proving their effectiveness through concrete examples that potential employers can see and appreciate.
We discuss how visible results, whether in a photo gallery, client testimonials, or measurable outcomes, are much more compelling than vague descriptions. The key is to identify one skill you can demonstrate clearly, like Carmen’s quick drawings explaining medical procedures for frightened ICU families, or Mira’s packaging design that helps bakeries sell their products better.
Creating such proof doesn’t always require complex setups; it could be as simple as documenting the success of a project you’ve worked on. This approach also benefits from feedback and validation by others who can vouch for your results. By positioning yourself correctly with these proofs, you make a stronger case for why hiring you would benefit them.
For those in sensitive fields like healthcare or finance where confidentiality is key, we offer strategies to still create visible proof without breaching privacy. Building the page result-first ensures that people can immediately see what value they'd receive from your work.
As a challenge, try building your own Proof-of-Stack Page based on one of your recent projects and share it with potential clients or employers. This practical step helps you refine how you present yourself and may even lead to better job opportunities.
Chapters:
0:00 Intro
0:12 Chapter 7: Ability Doesn’t Signal Itself
2:59 Being Good and Being Seen Are Two Different Jobs
4:11 The Experiment That Put a Price on Proof
8:06 Most Proof Sits a Rung Lower Than You Think
10:30 Price the Next Job From the Last Result
12:16 The Night Carmen Counted
15:14 One Page That Shows the Whole Stack
18:07 Make the Category Smaller
21:03 When Nobody Needs It
24:13 Chapter Summary
25:10 Try This Week
27:07 Outro
You don't have to be the best at one thing. You become rare by combining a handful of solid skills. This book lays out a four-step method for doing it: See It, Stack It, Build It, Prove It.
Become One of One by Peter Hollins: Chapter 7, an audiobook preview.
The release date will be announced. This preview is shared with permission and is available on this channel for a limited time. It will come down when the audiobook is released.
Audiobook details: https://www.amazon.com/dp/B0HM2TLJRZ
#ProofofStackPage #jobsearch #freelancework
In this episode, we dive into the fascinating world of combining seemingly unrelated skills to solve complex problems. The Weekly Collision technique is introduced as a simple yet powerful tool for generating ideas and improving your approach to challenges at home or in the workplace. By pairing two different skills each week, you can uncover new solutions that neither skill alone could have produced.
We explore real-life examples like how insights from working behind a pastry counter helped design better boxes for pastries. Each episode wraps with a challenge encouraging listeners to apply these concepts to their own lives and share their experiences in the comments section below.
Chapters:
0:00 Intro
0:12 Chapter 5: Make Your Skills Collide
4:02 The Supermarket in the Machine Shop
7:05 The Thursday Meeting
10:12 The Useful Idea Shows Up Past Line Six
13:54 Sunday’s Skill, Monday’s Problem
16:10 Introduce Them on Purpose
20:12 Chapter Summary
20:57 Try This Week
23:05 Outro
You don't have to be the best at one thing. You become rare by combining a handful of solid skills. This book lays out a four-step method for doing it: See It, Stack It, Build It, Prove It.
Become One of One by Peter Hollins: Chapter 5, an audiobook preview.
The release date will be announced. This preview is shared with permission and is available on this channel for a limited time. It will come down when the audiobook is released.
Audiobook details: https://www.amazon.com/dp/B0HM2TLJRZ
#WeeklyCollision #diverseskillset #problemsolving
In today's fast-paced work environment, keeping up with evolving skill sets is crucial for career success. This chapter delves into the constant race against skill obsolescence, emphasizing how to audit and upgrade your skills before they become outdated. By adopting a quarterly stack audit process, you can prioritize which skills to deepen or hand off, ensuring continuous relevance in your field.
Start by listing every skill in your stack—those you love, those that feel like a chore—and assign each one a word: Keep, Deepen, Add, Hand Off, or Drop. This exercise helps identify and focus on the skills most valuable right now. Adding new skills while current ones still pay can be a smart strategy for long-term career growth.
Another key tool is maintaining a Bottleneck Log. When a problem prevents you from achieving better results, document it and track potential solutions. Over time, these logs help pinpoint areas where investment in new capabilities could significantly improve your performance.
Understanding the transition of skills from rare to common can also guide strategic skill planning. As old skills evolve into judgment and systems understanding, they remain valuable but require less active effort to maintain their benefits.
Stay ahead by continuously assessing what you do best and how you add value to others—this insight guides both personal growth and professional development choices.
Chapters:
0:00 Intro
0:12 Chapter 8: Rebuild Before You Have To
4:08 The Hottest Skill Has the Shortest Shelf Life
7:32 Where a Skill Goes to Get Cheap
10:33 Chase the Bottleneck
13:00 Give Every Skill One Word, Every Quarter
19:06 The Name Tag That Won’t Come Off
20:56 Chapter Summary
21:48 Try This Week
24:34 Outro
You don't have to be the best at one thing. You become rare by combining a handful of solid skills. This book lays out a four-step method for doing it: See It, Stack It, Build It, Prove It.
Become One of One by Peter Hollins: Chapter 8, an audiobook preview.
The release date will be announced. This preview is shared with permission and is available on this channel for a limited time. It will come down when the audiobook is released.
Audiobook details: https://www.amazon.com/dp/B0HM2TLJRZ
#careerdevelopment #jobmarkettrends #skillobsolescence
The Wright brothers’ journey to flight began with a simple letter in 1899. Wilbur wrote to the Smithsonian asking for guidance on what to read about flying machines. The reply pointed him and his brother Orville towards valuable resources that would shape their two-year project loop: Try → Get Feedback → Find the Error → Adjust → Try Again. This method is now scaled down into a practical "30-Day Build," focusing on one real project, aiming for a visible outcome, and iterating weekly.
We delve deeper into how this method works today. Choose your own project with a specific goal and deadline, make an initial attempt within the first week of starting, get feedback from peers or customers, identify what went wrong, tweak it slightly, and try again next week. This loop not only accelerates learning but ensures each effort is grounded in real-world outcomes.
Butler's study showed that repeated quizzes with feedback enhance recall significantly—a principle reinforced by Dyson’s 5,127 prototypes over five years. Each prototype answered a question the previous one raised. Your project needs a similar iterative process: try something new each week and observe how it performs against your goal. This method encourages you to adjust based on tangible results rather than theoretical knowledge.
For those stuck in copying mode, making that first original change can be daunting but essential for true learning. Start by asking someone who knows more to critique your work, whether a customer or a mentor. Each iteration should focus on one variable at a time so you can pinpoint what works and what doesn’t. This approach ensures your efforts are focused and effective.
Remember, real-world feedback is key. Ask an honest customer or a knowledgeable peer for input regularly. Push your AI tools to critique rather than generate work. The goal is to build skills by working through problems firsthand, making each mistake count as part of the learning journey. So pick your project today, set your number and date, make that first attempt within seven days, and let the feedback loop begin.
#non-fiction
Chapters:
0:00 Intro
0:12 Chapter 6: Learn by Building
4:10 Studying Feels Like Progress
5:36 Why Making Beats Reading
7:44 Turn the Light On: One Error, One Change, Every Week
13:26 Size the Build
16:25 Use AI Like a Sparring Partner
18:16 Ben’s Thirty Days
22:16 Chapter Summary
23:14 Try This Week
25:15 Outro
You don't have to be the best at one thing. You become rare by combining a handful of solid skills. This book lays out a four-step method for doing it: See It, Stack It, Build It, Prove It.
Become One of One by Peter Hollins: Chapter 6, an audiobook preview.
The release date will be announced. This preview is shared with permission and is available on this channel for a limited time. It will come down when the audiobook is released.
Audiobook details: https://www.amazon.com/dp/B0HM2TLJRZ
Problems that keep coming back usually come from the structure around the people, not the people themselves. This book gives managers and leaders tools such as the Iceberg Model and system maps for finding that structure.
In this chapter, we delve into the bullwhip effect, a phenomenon where small changes in consumer demand are amplified as they travel upstream through supply chains. We break down how overreaction to short-term signals and large batch ordering contribute to this distortion. Hau Lee's influential 1997 paper with colleagues Padmanabhan and Whang formalized these mechanisms. Additionally, we discuss how workplace issues often form feedback loops that aren't always linear or straightforward.
Understanding causal loop diagrams is key to mapping these complex systems accurately. These diagrams use circles (variables) and arrows (causal relationships), along with plus or minus signs to indicate if the relationship moves in the same or opposite direction. We explore a specific example of workload, errors, and rework reinforcing each other in a closed loop.
The chapter also provides practical advice on building your first causal loop diagram, using early client churn as an illustrative pattern. It highlights the importance of identifying delays between cause and effect and tracing arrows back to form complete loops rather than chains.
Practicing this method can reveal hidden connections within workplace dynamics and offer insights into persistent problems like missed deadlines or high churn rates.
Chapters:
0:00 Intro
0:20 Chapter Three: Mapping Cause and Effect at Work
4:49 The Problem With Thinking in Straight Lines
6:21 Reading the Notation
7:54 Practice: Building Your First Causal Loop Diagram
11:33 Two Mistakes to Watch For
13:30 Chapter Summary
14:43 Outro
Systems Thinking for Work by Albert Rutherford: Chapter 3, an audiobook preview.
The release date will be announced. This preview is shared with permission and is available on this channel for a limited time. It will come down when the audiobook is released.
Audiobook details: https://www.amazon.com/dp/B0HMDJK87Z
#bullwhipeffect #causalloops #workplaceproblems
Problems that keep coming back usually come from the structure around the people, not the people themselves. This book gives managers and leaders tools such as the Iceberg Model and system maps for finding that structure.
In this chapter, we dive into the concept of reinforcing and balancing loops within business operations. We explore how People Express initially experienced rapid growth through a reinforcing loop that accelerated their success until capacity constraints began to overpower it via a balancing loop. Understanding these dynamics helps us see why growth often comes with hidden challenges like operational strain and declining service quality. Peter Senge introduced the terminology for these loops in "The Fifth Discipline," labeling them as R (reinforcing) and B (balancing). We discuss how counting minus signs can help identify whether a system is reinforcing or balancing, providing insights into potential future shifts in business dynamics.
Chapters:
0:00 Intro
0:20 Chapter Four: The Loops Running Your Organization
6:32 Naming the Two Loop Types
8:28 Practice: Labeling the Loops in Your Own System
12:34 A Dip Isn’t a Reversal
13:37 Chapter Summary
14:58 Outro
Systems Thinking for Work by Albert Rutherford: Chapter 4, an audiobook preview.
The release date will be announced. This preview is shared with permission and is available on this channel for a limited time. It will come down when the audiobook is released.
Audiobook details: https://www.amazon.com/dp/B0HMDJK87Z
#businessstrategy #organizationalgrowth #reinforcingloops
You don't have to be the best at one thing. You become rare by combining a handful of solid skills. This book lays out a four-step method for doing it: See It, Stack It, Build It, Prove It.
In this chapter, we explore the idea that not every skill needs to be mastered completely. The book suggests focusing on "Minimum Viable Competence," which is enough proficiency to get a job done effectively without wasting time or resources. We delve into how different skills require varying levels of depth within your professional toolkit.
The conversation touches on practical examples and personal anecdotes from the likes of Joe Gebbia, one of Airbnb’s founders, who emphasizes the importance of light learning for immediate application rather than exhaustive training. The text also discusses strategies like using an exit test to define when a skill is learned well enough and practicing skills from memory to solidify knowledge.
By applying these principles, you can allocate your time more effectively across different tasks, ensuring that each new skill contributes meaningfully to your overall stack without overcommitting resources. Think about the last skill you tried to learn thoroughly versus how much of it was truly necessary for your needs.
#learning-skills #education-strategy #skill-depth-versus-breadth #minimum-viable-competence #continuous-improvement
Chapters:
0:00 Intro
0:12 Chapter 4: Learn Only as Deep as You Need To
3:09 Airbnb Learned Just Enough Photography, Then Stopped
6:24 Someone Who Knows Data
9:50 Why Enrolling Feels Safer Than Starting
11:39 Match Each Skill’s Depth to Its Job
15:04 Define Done Before You Start
18:07 Pull It Out Instead of Putting It In
20:03 Chapter Summary
21:00 Try This Week
23:58 Outro
Become One of One by Peter Hollins: Chapter 4, an audiobook preview.
The release date will be announced. This preview is shared with permission and is available on this channel for a limited time. It will come down when the audiobook is released.
Audiobook details: https://www.amazon.com/dp/B0HM2TLJRZ
Problems that keep coming back usually come from the structure around the people, not the people themselves. This book gives managers and leaders tools such as the Iceberg Model and system maps for finding that structure.
Systems Thinking for Work by Albert Rutherford: 1, an audiobook preview.
The release date will be announced. This preview is shared with permission and is available on this channel for a limited time. It will come down when the audiobook is released.
Audiobook details: https://www.amazon.com/dp/B0HMDJK87Z
From the publisher's feed