The B2B Podcast Index
Index
All categories
MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
MethodologySubmit
Best of:MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
An independent project byFame
SearchBest episodesGuestsInsightsMethodologySubmit a podcast
Index/Ops/Lean By Design
Lean By Design artwork

0310. The Slow Leak Dismantling Your Operations

Lean By Design · 2026-08-19 · 7 min

0:00--:--

Key moments - from our scoring

Substance score

23 / 100

Five dimensions, 20 points each

Insight Density9 / 20
Originality7 / 20
Guest Caliber0 / 20
Specificity & Evidence5 / 20
Conversational Craft2 / 20

Oscar, founder of Sigma Lab Consulting and host of Lean by Design, launches a series of excerpts from his book Predictably Broken, which addresses operational dysfunction in organizations. Rather than manifesting as dramatic crises, dysfunction operates as a "slow leak" - spreading gradually through vague responsibilities, ambiguous reporting requirements, and disconnected processes that compound invisibly until they become undeniable problems. Using his experience discovering water damage in his Boston-area home, Oscar illustrates how dysfunction follows indirect paths, traveling along hidden routes before symptoms become visible. The book targets three audiences: newcomers to industry who assume their workplace functions well, middle managers trapped in reactive firefighting, and leaders failing to recognize how operational misalignment cascades across the organization. Oscar draws on his background in academia and pharma to demonstrate how blame-gaming prevents direct problem-solving. Organizations typically respond only when issues become crises, but Oscar argues that recognizing early warning signs - the subtle stains - allows for proactive repair rather than emergency response.

Key takeaways

  • →Operational dysfunction spreads invisibly like a slow leak rather than announcing itself through crises, making early detection critical for prevention.
  • →Vague responsibilities and ambiguous reporting requirements are the primary symptoms of organizational misalignment that precede visible operational breakdown.
  • →Water damage in his home taught Oscar that dysfunction travels indirectly and accumulates in hidden areas before becoming obvious, mirroring how process gaps spread through organizations.
  • →Most organizations only address operational problems reactively when they become crises, missing opportunities for earlier intervention.
  • →Predictably Broken provides specific language and frameworks for identifying and repairing broken systems, particularly valuable for middle managers and disconnected leaders.

Topics in this episode

Root cause analysisReporting structuresOrganizational systems thinkingPredictably Broken (book)Sigma Lab Consultingoperational dysfunctionprocess alignmentresponsibility mappingreactive managementproactive problem prevention

Questions this episode answers

What does Oscar mean by calling operational dysfunction a 'slow leak' instead of a 'blowout'?

Dysfunction spreads gradually and invisibly through organizations - via missed deadlines, vague responsibilities, and unclear reporting - rather than manifesting as dramatic, obvious crises, making it easy to overlook until it becomes severe.

Who is Oscar's book 'Predictably Broken' written for?

The book targets newcomers to industry, middle managers working excessive hours fighting fires, and leaders who don't recognize how disconnected operations slow down their entire organization.

What does the water damage story in Oscar's home illustrate about organizational problems?

Just as water didn't travel straight from the source but dripped along floorboards and puddled indirectly, organizational dysfunction spreads through non-obvious paths before becoming visible, meaning problems have typically been building for years before they surface.

What are the main symptoms Oscar identifies as warning signs of operational dysfunction?

Missed deadlines, vague responsibilities, ambiguous reporting requirements, and blame-gaming among colleagues are early indicators that point to underlying systemic problems.

What our scoring noted

Our reviewer’s read on each dimension, with quotes from the episode.

Insight Density

9 / 20

The episode delivers a serviceable metaphor (dysfunction as slow leak) and identifies real symptoms (vague responsibilities, ambiguous reporting), but lacks actionable depth or novel diagnostic frameworks. The home repair analogy is relatable but doesn't translate into specific operational fixes or mechanics that practitioners wouldn't already intuitively understand.

Operational dysfunction isn't always loud, doesn't wave its arms or send out press releases. It creeps in slowly, showing up as missed deadlines, vague responsibilities, or reporting requirements that no one fully understands.
By the time the dysfunction is visible, it has been building up for quite a while, potentially years.

Originality

7 / 20

The slow-leak metaphor is intuitive but not particularly fresh; the framing of operations problems as hidden and systemic is standard consulting orthodoxy. The episode lacks contrarian claims, first-principles reasoning, or any framework that challenges how operators typically think about dysfunction.

Dysfunction is a slow leak, not a blowout.
Much like you would expect finding gaps in your processes and dysfunction in your operations. It's not always a straight line.

Guest Caliber

0 / 20

This is a solo host reading from his own book prologue; no guest is present. While Oscar claims consulting and pharma/academia experience, the episode format is a pure book excerpt with no real guest interaction or cross-examination.

Hey listeners, Oscar here, host of Lean by Design and founder of Sigma Lab Consulting.
This snippet comes from the prologue.

Specificity & Evidence

5 / 20

The episode relies entirely on a single anecdotal home repair story and generic symptoms (missed deadlines, vague responsibilities). No data, metrics, named companies, or concrete examples of operational fixes are provided. The personal home story is illustrative but not evidence of broader operational patterns or solutions.

I noticed something. This was a new build.
This looked like a water stain coming from the area above the garage.

Conversational Craft

2 / 20

This is a monologue reading, not a conversation. There are no host questions, guest pushback, genuine dialogue, or productive disagreement. The format is a book excerpt delivery with rhetorical prompts to the listener but no actual conversational dynamic.

So ask yourself where is the slow leak your organization now?
And what could it turn into?

Conversation analysis

Computed from the transcript - who did the talking, and the words that came up most.

Most-used words

dysfunction5book4started4broken3leak3house3ceiling3predictably2wrote2figured2finding2operations2start2vague2responsibilities2reporting2

Episode notes

Send us Fan Mail A tiny stain on a garage ceiling doesn’t feel like a big deal until it comes back, darker, wider, and harder to ignore. That’s the exact pattern we see in operational dysfunction: the real problem isn’t loud, it doesn’t send alerts, and it rarely shows up where it started. It creeps in through missed deadlines, vague responsibilities, unclear ownership, and reporting requirements no one truly understands. As we close out season three of Lean by Design, I’m sharing short snippets from my book, Predictably Broken, written for people who sense something is off at work but don’t yet have the language to describe it. If you’re new to the industry and assumed the system was solid, if you’re a middle manager working all hours just to keep things from breaking, or if you lead teams and can feel operations slowing everything down, this one will land. This reading from the prologue uses a real story from my first home purchase near Greater Boston: a “fixed” leak that was painted over, only to resurface years later because the water traveled along an unexpected path.

Full transcript

7 min

Transcribed and scored by The B2B Podcast Index.

Hey listeners, Oscar here, host of Lean by Design and founder of Sigma Lab Consulting. If you caught our last episode, we're doing something a little different here as we finish out season three of the podcast. For the next few weeks, I'm going to release snippets of my book, Predictably Broken. I wrote this book for those new to the industry who thought their workplace had it all figured out.

For the middle manager finding themselves working at all hours of the day and night, plugging holes, putting out fires. And for the leaders who haven't quite figured out how disconnected operations is slowing everything down. I wrote this book as a no-fluff reflection of my experiences working in academia and pharma, where I felt no one faced issues head-on, instead, playing the blame game amongst colleagues. This book gives you the language to talk about it and outlines how to start repairing a broken system.

Predictably Broken is available on shelves now, in digital and in print form. Let's get started. This snippet comes from the prologue. Operational dysfunction isn't always loud, doesn't wave its arms or send out press releases.

It creeps in slowly, showing up as missed deadlines, vague responsibilities, or reporting requirements that no one fully understands. Dysfunction is a slow leak, not a blowout. I have a small story about my first home that I purchased right out here in the Greater Boston area. This was a couple years ago, just before COVID, about a year before COVID.

And I noticed something. This was a new build. We got lucky, we jumped in, got the house. But I also noticed there was some ceiling staining in the garage.

And I know this from my learnings as a young kid following my dad around making repairs around the house. This looked like a water stain coming from the area above the garage. After we brought it up, they said that was the builder, and their attorney said, Oh, great catch. We had a leak and we fixed it.

We're gonna go ahead and patch it up. So they went in, they painted it, covered it up, bought the house, we moved in. Two years later, I started to notice that the staining was returning. The ceiling wasn't wet, there was no noise, there was no smell, just a color.

Small color stain. Over time it became more yellow. It looked and appeared to be more prominent, more recent. And as I began to address the root of the problem by cutting in a space in the drywall, removing insulation, we found that the water was traveling.

You see, the dysfunction that we found was not traveling in a straight line. Much like you would expect finding gaps in your processes and dysfunction in your operations. It's not always a straight line. It would drip and travel along the floorboards until it pulled and puddled and began to drip down.

So by the time the dysfunction is visible, it has been building up for quite a while, potentially years. Most organizations only respond when it becomes a crisis. These things are bound to happen. We bought a home.

You started an organization and started to hire people, managers, workers, leadership. The goal is to recognize it. The vague responsibilities, ambiguous reporting requirements. These are symptoms, stains in the ceiling beneath the bathroom.

These are systems that most people relate to their team or project they're working on. So ask yourself where is the slow leak your organization now? And what could it turn into? It might be time to start repair.

Thanks for listening.

Related episodes across the Index

Other episodes covering the same guests and topics, from across The B2B Podcast Index.

  • Building Internal Governance: Duncan Astill On Healthcare Safety Beyond External RegulationThe Connection · on Root cause analysis86 / 100
  • Continual Improvement, Nonconformities, and Corrective Actions | Interview with Carlos CruzSecure & Simple · on Root cause analysis85 / 100
  • DevOps and observabilityNext in Tech · on Root cause analysis79 / 100
  • Systems Over Signs: How James Ferrell is Engineering Out Workplace HazardsThe Canary Report: Safety & Risk Management · on Root cause analysis79 / 100
  • CX Superheroes podcast - Series 15 Episode 1 - Leading CX at Sclae - Tina LiljeCustomer Experience Superheroes · on Root cause analysis79 / 100
  • Why Testers Are Safe Despite AI Hype - Mitko MitevSoftware Testing Unleashed · on Root cause analysis76 / 100

More from Lean By Design

All episodes →
  • 0308. The Space Between Systems77 / 100
  • 0306. When Your Systems Don't Match How Work Happens56 / 100
  • 0305. Facility Readiness: More Than a Checklist56 / 100
  • 0304. When Data Exists but No One Sees the Full Picture47 / 100
  • 0303. When Hard Work Isn't Enough in Complex Projects81 / 100
Explore the best B2B Ops podcasts →
All Lean By Design episodes →