Over-Commitment and Silence—The Deadly Duo Destroying Your Teams | Felipe Engineer-Manriquez - Scrum Master Toolbox Podcast: Agile storytelling from the trenches

Scrum Master Toolbox Podcast Summary
Episode Title: Over-Commitment and Silence—The Deadly Duo Destroying Your Teams
Guest: Felipe Engineer-Manriquez
Host: Vasco Duarte
Date: January 27, 2026

Episode Overview

This episode dives into the twin anti-patterns of over-commitment and silence within Agile teams, especially in the context of construction and Lean/Agile practices. Host Vasco Duarte and guest Felipe Engineer-Manriquez explore how these patterns devastate team performance, the deeper systemic issues that drive them, and actionable interventions that Scrum Masters and team leaders can apply.

Key Discussion Points & Insights

The Transformative Power of “The Goal” and Theory of Constraints

[01:25 – 05:07]

Book That Changed Felipe’s Practice:
Felipe credits The Goal by Eliyahu Goldratt as the most transformative book in his Lean/Agile journey. He emphasizes the importance of the Theory of Constraints (TOC) for understanding and optimizing systems, both in construction and general Agile work.
Quote:

“The most transformative, the most amazing book that even sounds like a radio production is Eliyahu Goldratt’s The Goal... What you learn in that book is that it’s the slowest, slowest part of a process that actually governs and dictates where the improvement should happen.”
— Felipe Engineer-Manriquez [02:16]
Underutilized Practice:
Felipe notes that many Scrum training programs skip over TOC and value stream mapping due to time constraints, leaving many certified Scrum Masters unfamiliar with these crucial concepts.

“A lot of Scrum Masters that get credentialed never actually learn this.” [03:44]

The ‘Herbie’ Metaphor and Systems Thinking

[03:57 – 05:07]

Use in Real Teams:
Felipe brings “Herbie” (the slow hiker from The Goal) as a powerful metaphor for bottlenecks in teams: addressing the bottleneck benefits the whole system.
Practical Application:
Value stream mapping and reverse phase pull planning (as in the Last Planner System) help make bottlenecks and dependencies visible.

“Once you start doing this… that’s a whole rabbit hole you could go into value stream mapping that I think is very underutilized by so many Scrum Masters.” [02:56]

Patterns of Self-Destruction: Over-Commitment & Silence

[05:07 – 11:28]

Root Cause: Bad Systems, Not Bad People
Self-destructive teams usually aren’t filled with “bad actors,” but with people crushed by broken systems. Workarounds proliferate to make up for process dysfunctions.

“They don’t self destruct because they’re bad or you have bad characters … what I do see is people getting crushed in terribly bad systems and these people are doing all these workarounds to try to survive broken systems.”
— Felipe [05:58]
Case Story: The Consequences of Silence
In construction, over-commitment is common: teams promise impossible things (e.g., scheduling a concrete pour without necessary prep). Low psychological safety leads to no one speaking up about obvious problems.
Quote:

“The biggest pattern of self destruction I saw was over commitment coupled with silence where people can’t bring up problems. Psychological safety was so low that people could not even say that the emperor has no clothes.”
— Felipe [06:33]
Systemic Impact:
This combo leads to unrealistic deadlines, hidden blockers, and inevitable failures. Concrete team members “forced” to commit to undeliverable work because the system demands it.

Surfacing Problems: Asking Tough Questions

[07:39 – 11:28]

Breaking the Pattern with Curious Questions:
Felipe makes it a point to voice “obvious” dependencies (“Don’t you need X in place for Y?”), which can seem annoying but is necessary to expose unspoken risks and foster safety.
Quote:

“I just have to apologize. I’m just a simple dumb general contractor and I don’t understand this and I really don’t, I don’t understand why people need to overcommit. I mean I do understand—it’s because of the low psychological safety.”
— Felipe [08:10]
Reimagining Accountability:
Real accountability comes only when people are empowered to say ‘no’ without fear. If they can’t say no, commitments are meaningless.

“For real accountability, if people are not allowed to say no, then they actually can’t make a real promise.”
— Felipe [09:31]
Making Work Visible:
Using “verb down” scrum cards (action-oriented phrasing) and tasks as a way to explicitly break down complexities and dependencies.

Silence Is Not Alignment

[10:10 – 10:54]

The Executive Trap:
Leaders often interpret silence as agreement; in reality, it signals fear or disengagement.
Quote:

“Silence is not alignment. And that’s a risk, especially for executives that come and make proclamations... When the team can’t like react and say yes, I’ll often raise my hand, say, excuse me, I didn’t see actually anybody agree to that.”
— Felipe [10:12]
Changing the Conversation:
Pivotal question Felipe uses:

“What would need to be true so that we could agree?”
— Felipe [10:45]
This reframes accountability and unlocks constructive team participation.

“Decision Hallucination”

[10:54 – 11:28]

Related Insight (from prior guest):
“Decision hallucination” is the act of making decisions based on invalid or out-of-date assumptions, a natural consequence of suppressed truth-telling within teams.

“You are making decisions based on assumptions that are no longer true or were never true. So it’s a hallucination, right?”
— Vasco Duarte [10:56]

Notable Quotes and Takeaways

“Don’t you need this so that you can do that?” – Calling out dependencies is the first step in restoring rational planning and trust. [08:58]
“If people are not allowed to say no, then they actually can’t make a real promise.” – True accountability demands psychological safety. [09:31]
“Silence is not alignment.” – Don’t mistake lack of feedback for consent. [10:10]
“What would need to be true so that we could agree?” – A simple, non-blaming phrase to surface blockers and empower teams. [10:45]

Episode Structure & Timestamps

[01:11] Introduction and guest welcome
[01:25–05:07] Influence of The Goal, Theory of Constraints, and value stream mapping
[05:07–07:39] Patterns of over-commitment, silence, and systemic dysfunction
[07:39–10:02] Tactics for surfacing issues, the nature of accountability, and visibility
[10:02–11:28] Silence vs. alignment; powerful tools for team conversation
[11:28–11:39] Summary and closing remarks

Conclusion

This episode offers real-world insights for Scrum Masters and Agile leaders facing unhealthy patterns of over-commitment and silence within teams. Through vivid examples and actionable advice, Felipe Engineer-Manriquez reminds listeners that the root cause is almost always the system, not the people. The path forward lies in making work visible, asking candid questions, and fostering psychological safety—so that teams can move from “decision hallucination” toward meaningful, accountable delivery.

Transcript

A (0:04)

Hey there, agile adventurer, just a quick question. What if for the price of a fancy coffee or half a pizza, you could unlock over 700 hours of the best agile content on the planet? That's audio, video, E courses, books, presentations, all that you can think of. But you can also join live calls with world class practitioners and hang out in a flame war free and AI slop clean slack with the sharpest minds in the game. Oh, and yes, you get direct access to me, Vasko, your Scrum Master Toolbox podcast. No, this is not a drill. It's this Scrum Master Toolbox membership. And it's your unfair advantage in the agile world. So if you want to know more, go check out scrummastertoolbox.org membership. That's scrummastertoolbox.org Membership. And check out all the goodies we have for you. Do it now. But if you're not doing it now, let's listen to the podcast.

B (1:11)

Hello everybody. Welcome to our team Tuesday. This week we have with us talking about agile in construction, Felipe, Engineer Manriquez. Hey Felipe, welcome back.

C (1:21)

Hey Vasco, thanks for having me back. Love what's going on here. Let's keep going.

B (1:25)

Yeah, me too, me too. This is getting so interesting. I already selected a clip to send to one of my teams because they really need to listen to what we talked about yesterday. Diving into the Tuesday episode. First, let's talk about a book that influenced you. What was the book that most influenced you and helped you define your own approach to lean and agile construction?

C (1:46)

Yeah, I would say the number one game changer book of my early career when I was first learning about Lean and I was consuming about a book a month, that's as fast as I could read in those early days and mostly on audible. So like if it wasn't a book on tape, it wasn't happening. And the most transformative, the most amazing book that even sounds like a radio production is Elijah Goldrat's the Goal. The Goal. And I know it's like it's an amazing book about, it's fictional, but to show and explain and teach and so you can internalize the theory of constraints. And that book is something that even now, as a registered Scrum Master trainer that I try to embody and teach each of my students that are becoming Scrum Masters so they can understand how to make rapid improvements. And I think the goal, and this is not talked about that often, is really a phenomenal book so that you can implement Kaizen, which is rapid change. Rapid change for the better. With teams. And so in applying theory of constraints, I'm able to think as a system, observe an actual value stream, and mentally. And once you start doing this and that, that's a whole rabbit hole you could go into value stream mapping. That I think is very underutilized by so many Scrum Masters. And I'll even tell you that when I'm in Scrum training, in the early days when I was becoming a Scrum trainer, as people get to the end of the sprints, it's usually two day training. If the class is doing really well and asking a lot of questions and they're running out of time, they skip the lean stuff at the end of the final spri. And they don't teach people theory of constraints. And so a lot of Scrum Masters that get credentialed never actually learn this. Now I, luckily for me, I learned theory of constraints even way before Scrum. And what I used it for is in this method called Last Planner System Production Controls, where we do reverse phase pool planning, we create what look like Scrum boards, but instead of labeling to do doing done, we use days of the week because we know we love Gantt charts. So we have to make our visuals look just like a schedule. It's got to look like a schedule. And it looks like, it looks like a waterfall schedule. But with the new understand theory constraints. And there's a beautiful story for your. A lot of your listeners have probably at least heard of this book because the Goal was a, a worldwide phenomenon that's been published in dozens and dozens of languages. What you learn in that book is that it's the slowest, slowest part of a process that actually governs and dictates where the improvement should happen. And in the Goal, there's a great story, there's a story within the story. It's very meta, where there's a, a team of hikers going. And this, I can still remember this like. And I haven't read the Goal. It's been like at least two years since the last time I've reread it. But this is a book that I revisit in my like yearly. I'll probably read it again now just because you're reminding me how awesome it is. But there's a story where the, the main character is taking some kids to hike in the woods and there's a guy named Herbie that's slow and by helping Herbie, he speeds the whole process up and everything changes for the better. And I use that concept every single time I Work with project teams today, whether I'm doing full scrum or just.