Over-Commitment and Silence—The Deadly Duo Destroying Your Teams | Felipe Engineer-Manriquez

Summary

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]

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]

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]

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

[B]

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]

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.

[B]

Lean construction techniques, I think theory of constraints is one of those underrated aspects that can fully transform a system once system, when we grasp it and how it's applied. Talking about transforming a system, very often we work with teams and some teams are great, amazing. They get these ideas, they apply them, they just rock. And others kind of self destruct. And on Tuesdays we always explore that because we want to know what are the patterns that lead to that kind of self destruction. So share a story of a team with us Felipe. And what are those patterns, those behaviors that maybe you know, started to show up as small interactions but eventually grew and had a huge impact on the team's ability to perform?

[C]

Yeah, and I'll say like even just piggybacking from the goal, that really taught me to internalize systems thinking. And I've read more books on that. But that is fundamental and I learned in that book just like there in that book. And real teams in construction, they don't self destruct because they're bad or you have bad characters or you have people like actively trying to sabotage. That I've never seen. But 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. So one of the first patterns I see is if I, if I can discern that people are doing lots of workarounds to make processes, to support processes that are garbage, to get the outputs, then I know that we're in a very self destructive way and that they're going to get hurt. There was one hospital project I'm working on in particular and the biggest pattern of self destruction that 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. And people would over commit impossible things. Like people would commit to, yeah, we're going to pour concrete on Thursday. And you would go and you know today's Monday so that's like four days from now. And you'd go and you see there's not even rebar down to the area where they're supposed to pour. And these areas were so large that it's physically not possible to put the rebar in place that's going to be embedded in the concrete, let alone all the other things that have to happen before you pour concrete. But the concrete person was forced to, to say because of the system. Thursday it is because that's what the schedule says. So now as a, when I see these patterns happen, I'll be sometimes the first voice that says but don't you need this so that you can do that? And I'm breaking the pattern.

[B]

That's actually a great point. Let's, let's, let's. I want to highlight that you ask the question with the aim, with the intention of breaking a pattern that you already know is self destructive.

[C]

Yes, absolutely. And that, that type of questioning is, it can be seen as annoying by, by certain team members, especially the ones that are holding the craziest to the Gantt chart schedule. But I always tell people like I, 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. But what I'm telling the as I'm answering to create the safety and to show them this anti pattern is that trust is too low and they can't say that things are uncommittable.

[B]

And so it's like we have to surface the things that cannot be spoken. Right. Like if there's lack of psychological safety, a lot of important things will not be talked about. But we have to learn to surface that in a way that the people that need to surface it don't feel like they being, they're being blamed or pointed to or called out.

[C]

Right, exactly. And then by just telling people that. So it's a simple thing like don't you need this so you can do that in, in scrum? Like I like my action oriented scrum cards of verb down phrases. I'm using a verb down phrase like I'm making a scrum task that I don't show them so that they can actually do their work. And that is very powerful to help make the work more visible and to break this pattern. Because we're really in a low trust environment and low trust environments, especially in our industry where yelling is still a thing, yelling at people is still a way to motivate teams. It can be a very tough industry to work in. And that type of environment really lowers trust. A turning point is when you can slow down, make the work visible and allow people to actually say no. Like I teach now like this accountability because accountability is like super hot thing. And I tell people for real accountability, if people are not allowed to say no, then they actually can't make a real promise.

[B]

It's not Accountability. Yeah, exactly. That's hiding from accountability. Saying yes in those contexts is hiding from accountability.

[C]

Yeah, and we teach like too. Like, silence is not alignment. And that's a risk, especially for executives that come and make proclamations. They'll come and make these proclamations of things that we should do. And they, with the best of intent for the project. But when the team can't like react and say yes, I, I'll often, like again raise my hand, say, excuse me, I didn't see actually anybody agree to that. And I'll. And I'll ask another question. What would need to be true so that we could agree. That's a totally different question because now you have people engaging their imagination and they can talk in a very detailed way of what is necessary to do so that they can be accountable and they can align to what's going on.

[B]

Yeah, that's actually a great, great question to ask. What would need to be true? Last week we interviewed someone who was talking about decision hallucination. So decision hallucination was when you are making decisions based on assumptions that are no longer true or were never true. So it's a hallucination, right? Like it's imagining something that isn't there. And what you just said just triggered that thought in me, that a lot of the decisions we make are in fact decision hallucinations. We're basing those decisions on something that either wasn't or is no longer true.

[C]

Right.

[B]

That's a great story. Thank you for sharing that with us, Felipe.

[C]

Yeah, thank you, Oscar.

[A]

All right, I hope you liked this episode, but before you hit next episode, here's the deal. This podcast is powered by people like you. The members who wanted more than just inspiration. They wanted real tools and real connection to people who are practicing agile. Every day we're talking access to over 700 hours of agile gold, CTO level strategy talks, Summit keynotes, live workshops, E courses, deep dive interviews, books. And if you're into no estimates, we got the pioneers of no estimates in those deep Dive interviews as well. Agile business intelligence, creating product visions, coaching your product owner courses, you name it. You'll get invites to monthly live Q&As with agile pioneers and practitioners. Plus a private Slack community which is free of all of that AI slop you see everywhere. And of course, without the flame wars, it's a community of practitioners that want to learn and thrive together. It's the best place to connect with community and learn together. So if this podcast has helped you before, imagine what you will get from this podcast. Membership. So head on over to scrummastertoolbox.org membership and join the community that's shaping the future of Agile. We have so much for you. So so check out all the [e-mail] membership because listening is great. It's important. But doing it together, that's next level. I'll see you in the community.

[C]

Slack.

[B]

We really hope you liked our show. And if you did, why not rate this podcast on Stitcher or itunes? Share this podcast and let other Scrum masters know about this valuable resource for their work. Remember that sharing is caring.