Podcast Episode Summary
Podcast: Scrum Master Toolbox Podcast: Agile storytelling from the trenches
Episode: Stop Teaching and Start Doing—The Secret to Agile Adoption in Construction
Host: Vasco Duarte
Guest: Felipe Engineer-Manriquez
Date: January 26, 2026
Overview
This episode kicks off a special week focused on Agile and Scrum in the construction industry, featuring Felipe Engineer-Manriquez—bestselling author, speaker, and host of The EBFC (Easier, Better for Construction) Show. The conversation centers on the challenges and realities of bringing Agile methodologies, especially Scrum, into traditionally structured industries like construction. Felipe shares his personal journey from exhaustion and inefficiency to learning and applying Lean and Agile principles, along with the critical lesson: stop teaching Agile—start doing it instead.
Key Discussion Points & Insights
1. Felipe’s Introduction and Backstory ([01:25] – [05:30])
- Felipe’s Experience in Construction: Nearly 30 years in the industry, with half of his career unaware of Lean or Agile.
- Origin Story: Discovered Lean out of necessity after severe burnout from overwhelming workloads and commutes.
- Catalyst for Change: Attended a company presentation by “Mike,” who introduced him to Lean for construction.
- Entry into Agile: Quickly moved from Lean to Agile; highly influenced by Jeff Sutherland’s book “The Art of Doing Twice the Work in Half the Time.”
- Early Practical Steps: Implemented his first Scrum board within days after absorbing the book's content.
Notable quote:
“I was working over 10 to 15, sometimes 16 hours a day... I was just seeing someone else’s team who was happy and I thought, why am I working so hard? What are they doing differently?”
— Felipe Engineer-Manriquez ([03:05])
2. The Gantt Chart Religion and Shifting Perspectives ([05:30] – [06:23])
- Construction's Traditional Tools: Heavy reliance on Gantt Charts, almost to a religious extent—strong faith in their predictive power.
Notable quote:
“We in the construction industry love Gantt Charts to death, and we are almost religious in our belief in how these schedules predict the future.”
— Felipe Engineer-Manriquez ([05:32])
3. The Origin of a Common Agile Mistake ([06:23] – [09:56])
- The Estimation Debate: Recognition of camps in Agile—those who estimate effort in time, and those who prefer sizing tasks using simple units.
- Felipe’s Approach: Aligns with Vasco’s “No Estimates” thinking, preferring simplicity (“counting my tasks as one is the easiest algebra and math I’m going to do”).
- Common Mistake: The urge to “teach” Agile, rather than demonstrating and integrating it into real work.
- Key Lesson: Team members often lack enthusiasm for change unless they understand the problem—it’s vital to let them experience success before introducing theory.
Notable quotes:
“My mistake early was to stop and move into teaching mode too soon. Now I wait until people actually pull for teaching if they want to learn.”
— Felipe Engineer-Manriquez ([07:57])
“It's almost disrespectful to people to come in and tell them the way they're doing things is wrong... It's better now to act as a guide and go along with them and show people the way.”
— Felipe Engineer-Manriquez ([09:25])
4. Real-World Contrast: Teaching vs. Doing ([09:56] – [15:10])
- Experimenting with Family: Applied Scrum with his 4-year-old son for practice—immediate resistance surfaced just by labeling the process.
- Workplace Case Study: On a large, high-stakes construction project, previous attempts to teach Lean tools had led to resistance. The transition: stopped overtly teaching and instead began to simply facilitate and embody Scrum practices.
- Results:
- Implemented visual management via Scrum boards.
- Focused on making work visible and delivering real, observable results—without formal Agile education.
- Only after witnessing better outcomes did a team member approach him, intrigued by the impact; this prompted a pull for learning.
- Team leaders and adjacent PMs eventually sought help for results, not instruction.
- Resistance often rooted in "not invented here" thinking and skepticism about methods “from other domains,” whether software or construction.
- Drastic improvement and real transformation occurred only after shifting away from teaching to modeling behavior and delivering value.
Notable quotes:
“Every time we'd start to go use a tool, I would go into teaching mode right away and it would just turn people off... they didn't understand the problem they were in.”
— Felipe Engineer-Manriquez ([07:58])
“People will figure out that you're doing something different and they will Google and try to understand from Google search results... And see that this is a software thing. We're not doing a software thing in construction.”
— Felipe Engineer-Manriquez ([11:58])
“Once I stopped trying to teach and just did the system...making work visible, going after problems in a systematic way...One project manager out of the 15...said, ‘You, this is a radically different type of management than traditional project management. What are you actually doing?’”
— Felipe Engineer-Manriquez ([13:02])
“...the things that you do are really simple. How is it so effective? It doesn't make—it’s counterintuitive.”
— Tom, Specialty Rigging PM ([15:10], as recounted by Felipe)
5. Lessons Learned and Takeaways ([15:10] – [16:37])
- Results Over Rhetoric: Colleagues cared about outcomes, not the Agile or Scrum label or theory.
- Peer Impact: Initially resistant peers eventually sought results assistance but continued to avoid discussion of Scrum/Agile concepts—showing the value of pragmatism.
- Summary Principle: Success comes from integrating Agile/Lean practices in action, not by formal instruction—only teaching if engaged interest emerges naturally.
Notable quotes:
“They didn't want teaching. They didn't want to learn how this thing works. They just wanted the results. And I think that's something a lot of people forget. And that's what Dr. Jeff Sutherland says all the time: ‘If you don’t actually ship product at the end of your sprint, you're not even doing Scrum...’”
— Felipe Engineer-Manriquez ([16:25])
Memorable Moments
- Applying Scrum at Home: Felipe’s first Scrum “team” was with his 4-year-old son, highlighting that even simple language or labeling can provoke unexpected resistance ([10:20]).
- The Theater Rigging Manager’s Reaction: “We’ve never come to a project where people held their promises and, like, just acted truthfully. I was like, this is how bad construction is.” ([13:46])
- Host’s Reaction: Vasco’s intent to share Felipe’s story with current clients for inspiration, underlining the relevance beyond construction ([15:03]).
Timestamps for Important Segments
- Felipe’s Introduction & Discovery of Lean/Agile – [01:25] – [05:30]
- Gantt Chart Religion – [05:30] – [06:23]
- Mistake: Teaching Instead of Doing – [06:23] – [09:56]
- Real-World Story: Resistance & Results – [09:56] – [15:10]
- Lessons and Final Takeaways – [15:10] – [16:37]
Final Thoughts
This episode vividly illustrates a universal Agile lesson: “stop teaching and start doing.” Through stories from both the home and challenging project environments, Felipe demonstrates that embodying Agile principles and delivering tangible results is the most powerful driver of change—especially in industries steeped in tradition and skepticism.
Listeners seeking to foster agility in their own teams or sectors, whether construction or elsewhere, will find actionable wisdom in Felipe’s advice: “Show them, don’t tell them.”
