Voice over Work - An Audiobook Sampler

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 how Boeing turned to outsourcing as a quick fix for cost and capacity pressures in the early 2000s. The move allowed them to cut costs and increase flexibility by converting their large manufacturing workforce into an outside supplier relationship. While this strategy worked initially, it gradually weakened their internal capabilities in engineering oversight and quality control over time. Boeing's reliance on outsourcing continued for two decades as each instance of cost or capacity pressure resurfaced, reinforcing the notion that cutting corners was a viable long-term solution. This dynamic created a dangerous cycle where the fundamental problem—lack of in-house expertise—was never addressed properly. Instead, it grew worse with every use of the symptomatic fix. The story culminates with Boeing's 787 Dreamliner program, which faced significant delays and cost overruns due to its overly aggressive outsourcing model, highlighting how relying on quick fixes can undermine a company’s ability to solve long-term issues effectively. By the time this became apparent, it was much harder for Boeing to invest in rebuilding those core competencies. The Shifting the Burden archetype helps us understand these dynamics: each application of the symptomatic solution (outsourcing) gradually weakens the fundamental one (rebuilding internal capability), making the former seem more necessary over time. This pattern is not unique to Boeing but applies broadly across industries and teams facing similar pressures. For listeners, consider reflecting on your own contexts where quick fixes are preferred over long-term solutions. How do you ensure that short-term relief doesn’t come at the expense of fundamental problem-solving capacity? Chapters: 0:00 Intro 0:20 Chapter Six: When Quick Solutions Become a Habit 5:20 Why This Is a Different Trap Than a Fix That Fails 7:46 The Three-Loop Structure 10:01 A Faster Version of the Same Pattern 12:50 Practice: The Long-Running Problem Worksheet 15:47 Chapter Summary 17:43 Outro Systems Thinking for Work by Albert Rutherford: 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/B0HMDJK87Z #Boeing #Outsourcing #Manufacturing

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. This chapter dives into how Morton Thiokol’s engineers correctly identified risks in the O-rings but were overridden by management due to organizational pressures and a lack of clear, implementable recommendations. Sociologist Diane Vaughan's concept of "normalization of deviance" highlights how known risks can become accepted practices over time. The text argues that effective recommendations must be designed for those who approve, implement, and live with them, addressing their unique pressures and constraints. The chapter offers a framework to ensure recommendations are not only correct but also resilient in implementation. It advocates for making interventions reversible and testable at small scales, which can prevent catastrophic failures like the Challenger disaster. This approach recognizes that different stakeholders may prioritize compliance, risk management, or operational efficiency differently. For those interested in improving decision-making processes within their organizations, understanding these dynamics is crucial. The chapter provides insights on how to craft recommendations that survive real-world scrutiny and pressures. Chapters: 0:00 Intro 0:20 Chapter Nine: Making Systemic Recommendations That Get Implemented 3:43 Why a Correct Diagnosis Isn’t Enough 6:25 What a Recommendation Has to Survive 8:29 Practice: Five Questions Before You Present a Recommendation 13:31 Chapter Summary 15:16 Outro Systems Thinking for Work by Albert Rutherford: Chapter 9, 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 #Challengerdisaster #NASA #Thiokol

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. This chapter examines how Toyota's impressive growth strategy led it into a situation where its very success became a constraint. As Toyota expanded rapidly, the company found that its ability to train engineers and maintain quality control couldn't keep pace with the rapid scale-up. This scenario is known as "Limits to Success" in systems thinking—where an initially effective strategy produces diminishing returns once it hits an unaddressed constraint. The chapter details how Toyota's growth engine relied heavily on global manufacturing volume, while its cultural bedrock of deep quality control couldn't be replicated at the same pace. As the company pushed harder on its existing strategy, it ran into a wall of constrained capacity for training and supplier development. This mismatch led to significant issues like recalls and congressional testimony regarding compromised safety standards. Understanding this dynamic is crucial for organizations looking to avoid similar pitfalls. The key takeaway is recognizing when your growth strategy is hitting limits beyond which pushing harder won’t work—instead, direct investment into the constraint is needed. It’s a lesson in adapting strategies as they encounter unforeseen constraints rather than continuing with what has always worked. Chapters: 0:00 Intro 0:20 Chapter Seven: When Success Creates Its Own Limits 5:55 The Shape Underneath the Pattern 7:06 Practice: Using Limits to Success as a Planning Tool 11:09 Distinguishing This From Shifting the Burden 13:17 Chapter Summary 15:04 Outro Systems Thinking for Work by Albert Rutherford: 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/B0HMDJK87Z #Toyota #LimitstoSuccess #GrowthStrategy

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. The Keystone Initiative dramatically reduced hospital infections by focusing on small but strategic changes. Instead of increasing budgets or staffing levels, they implemented a checklist to ensure all necessary steps were followed during procedures. Regular reporting of infection rates back to units allowed staff to monitor and improve their performance directly. The key innovation was authorizing any staff member, regardless of rank, to halt a procedure if safety protocols were being compromised. This shift in power dynamics empowered frontline workers to prioritize patient safety over hierarchy. By operating at the level of rules, information flows, and decision-making authority rather than just adding resources or changing parameters like budgets, they achieved remarkable results with minimal costs. For teams facing similar challenges, identifying leverage points can provide powerful insights into making lasting improvements. For instance, in customer service, allowing agents to escalate issues directly to engineers without managerial approval can significantly enhance response times and problem resolution. Such changes redistribute authority effectively while ensuring everyone has the necessary information to act responsibly. The lesson here is that focusing on high-leverage interventions often yields better results than just increasing resources or tweaking superficial metrics. Chapters: 0:00 Intro 0:20 Chapter Eight: Finding the Right Place to Intervene 3:25 Why Some Interventions Punch Far Above Their Size? 6:01 The Keystone Initiative, Reread Through This Lens 9:02 Practice: Comparing Interventions Against the Hierarchy 13:16 The Level Most Fixes Never Reach 14:47 Chapter Summary 16:45 Outro Systems Thinking for Work by Albert Rutherford: 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/B0HMDJK87Z #hospitalinfections #keystoneinitiative #leveragepoints

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 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

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

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-improvementChapters:0:00 Intro0:12 Chapter 4: Learn Only as Deep as You Need To3:09 Airbnb Learned Just Enough Photography, Then Stopped6:24 Someone Who Knows Data9:50 Why Enrolling Feels Safer Than Starting11:39 Match Each Skill’s Depth to Its Job15:04 Define Done Before You Start18:07 Pull It Out Instead of Putting It In20:03 Chapter Summary21:00 Try This Week23:58 OutroBecome 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