The work looked right. The question is whether it was.

In Part 2, Dr. Ahmed El-Rasheed gets into the mechanics of how electrical systems actually fail — and why more than half the time, the cause traces back to something that happened during construction. Not a bad design. Not a faulty component. The build itself.

We go inside the insulation resistance test: what it measures, what it catches, and what slips through when nobody's running one. We talk through what the silver tsunami actually means for crews in the field — what gets lost when the experienced hands walk out, and how that gap shows up months or years after handoff. Ahmed shares the story of two solar sites, same company, same equipment, one crew running clean for five years and one getting called back every month — the only difference being the experience of the people who built it.

From there we look forward: data centers wired end to end with sensors, telemetry outpacing human review, and AI increasingly doing what no person can do fast enough. Ahmed is optimistic. So am I. But the throughline doesn't change — none of it works if the work wasn't proven right at the start.

This is Part 2 of 2. Start with Part 1 if you haven't.

https://open.spotify.com/episode/2U5nI8TNxRscnRwYYjS1KB?si=792e12a43b094e13

Guest: Dr. Ahmed El-Rasheed — Industry Director at Megger, ~18 years in electrical test & measurement. PhD in electrical engineering (testing, sensors, multi-sensor integration with AI). Sits on standards committees for NETA, IEEE, IEC, and BSI.

Resources mentioned

• NETA — InterNational Electrical Testing Association
• IEEE
• IEC
• BSI
• AVO Training Institute (Dallas)

What does it actually mean to know electrical work was done right?

Not hope.
Not assume.
Know.

Dr. Ahmed El-Rasheed has spent his career inside the world of electrical testing and measurement. As Industry Director at Megger, he works at the intersection of power systems, field practice, and the instruments used to verify that critical infrastructure is ready to perform.

In Part 1, Ahmed and Nick cover:

• How Ahmed’s path from taking apart broken VCRs to electrical engineering shaped the way he thinks about measurement

• Why Megger became synonymous with insulation resistance testing in the electrical trades

• The difference between work being done and work being proven

• What Ahmed’s research with Jaguar taught him about visual completion versus verified quality

• Why electrical testing matters before energizing data centers, hospitals, power stations, and other critical infrastructure

• How renewables, HVDC, bidirectional power flow, and data center demand are changing the complexity of the grid

• Why certainty, skilled labor, and documentation matter more as the margin for error gets smaller

Part 2 picks up where this leaves off: testing culture, commissioning, workforce readiness, and what it takes to hold a higher standard in the field before the lights come on.

Support the show!

• Make sure to like, subscribe, and share your thoughts.

• Visit our founding sponsor at www.avicado.com

"Slow is smooth. Smooth is fast."

You've heard it on a call, on a jobsite, in a review — and nobody ever asks what it means. We just nod.

This Field Note is about why that phrase keeps resurfacing right now. The built world is accelerating — bigger projects, tighter schedules, less room for error — and the cost of getting things wrong is climbing. But most failures don't begin when something breaks. They begin weeks or months earlier, in a skipped verification, an assumption, a rushed review. Something that saved a few minutes. Until it didn't.

Everybody wants acceleration. Very few people talk about recovery. A short one on why speed without control eventually creates its own delay.

Field Notes. No guests. Just what the work is teaching us.

Most construction technology conversations ask the wrong question. They ask why adoption is slow. Jeff Sample asks something harder: are we even solving the right problem?

Jeff is Senior Industry Development Manager for Trades at Bluebeam and host of The ConTech Crew — a technologist with 30 years in IT who found construction a decade ago and never left. His perspective crosses job sites, startups, and strategy in a way most people in this industry never get.

In Part 2, Nick and Jeff get into: why disruption is a byproduct and not a goal — and what the Uber story actually teaches us. Why construction's technology problem is a translation problem, not an adoption problem. What separates high-performing crews from struggling ones when it comes to innovation. Why proximity to the work is non-negotiable for anyone trying to change how building gets done. And what the next generation of builders needs from the people ahead of them.

What you'll walk away with: a cleaner frame for why good tools fail in the field, and a sharper sense of what it actually takes to connect leadership intent to field reality.

Support the show!

• Make sure to like, subscribe, and share your thoughts
• Visit our founding sponsor at www.avicado.com

The industry knows the barriers. Community opposition. Workforce gaps. Power constraints. Access. Everyone in the room at DICE this week could name them.

But naming barriers isn't the same as being ready to clear them.

In this Field Note, Nick Caravella breaks down what readiness actually requires in data center construction — and why the industry keeps confusing hitting a schedule date with actually being prepared to finish the work.

Readiness isn't a milestone. It's a condition. And until we stop using the schedule as a substitute for that condition, we'll keep handing over buildings that aren't done — we just ran out of time to pretend otherwise.

Three conditions this episode examines:— The schedule problem: why the date gives you somewhere to hide— The workforce problem: people don't fall from the sky— The community problem: they're not an obstacle, they're a condition of completion

Field Notes. No guests. Just what the work is teaching us.

Why does construction technology keep landing wrong — even when the tools are better than they've ever been?

Jeff Sample has spent years traveling the industry as a host of the ConTech Crew and, more recently, as head of global industry strategy at Bluebeam. He's been in more contractor offices, job site trailers, and conference rooms than almost anyone in the construction technology space — which gives him a rare view of how technology actually behaves inside real companies and real teams.

In Part 1, Jeff and Nick cover:

• How Jeff's path from IT architect to ski resort technologist to construction tech leader shaped how he reads the industry
• Why people, process, and technology have to happen in that order — and what breaks when they don't
• The shift from evangelist to facilitator: why you can't preach adoption and what actually creates room for change
• What the industry gets wrong about RFIs — and what that reveals about how we handle expertise and risk

Part 2 picks up where this leaves off: culture beyond the company, grassroots adoption versus leadership alignment, and what it means to build an industry that's greater than the sum of its parts.

Support the show!

• Make sure to like, subscribe, and share your thoughts.
• Visit our founding sponsor at www.avicado.com

Most conversations about AI in construction focus on what the tools can do. This one focuses on what it actually takes to use them.

Marcus Turner has been building with AI tools in real construction and knowledge-work contexts for years. He is not predicting the future of AI. He is living in the present tense of it.

In this conversation:

• Why domain knowledge is the multiplier and AI only amplifies what you already understand
• What "context engineering" means and why most people are still using AI like a search engine
• How builders can start experimenting today without feeling like they are already behind
• What a personal AI agent stack looks like when someone actually builds one

The industry is not short on AI opinions. It is short on people who have gotten their hands dirty with it. Marcus is one of them.

Most conversations about construction technology focus on what the tools can do. This one focuses on what they actually do — to the people using them.

Rob Sloyer is VP of Innovation and Strategic Services at KAST Construction, a Florida-based multifamily builder with over two decades building at scale. He's been close to BIM since before most companies knew how to spell it — and he's watched enough hype cycles to know that technology without purpose doesn't just fail to help. It actively makes things worse.

In this conversation:

• Why BIM shifted problems earlier in the process instead of eliminating them
• The three-part test for whether a tool actually belongs in the work
• What AI adoption is getting wrong — and why it's hitting the same walls as every wave before it
• The workforce shortage, rework as a safety multiplier, and why the field pushes back

We never have time to do it right, but we always find time to do it again. This conversation is about changing that.