Sep 24, 2026 · 38 min · 9 segments
Send us Fan Mail On the Appetite for Construction podcast, as we set our sights in the ASPE Convention next month in OKC, we caught up with Bryan…
Brian HuttonGuest
John MesenbrinkHost
Tim WardHost

What are you hearing from your constituents as far as like challenges that need to be addressed in your organization?

You know, when you look at the challenges today, technology just continues to advance so fast.

But we have a, I mean, just looking at codes, let's look at code cycles first.

When you think about codes, you know, I'm not a proponent of designing to a code.

And the reality is if you look across the U.S., just looking at the U.S., I mean, we're a global organization, but when you look across the U.S., whether you're looking at the ICC codes or you're looking at the IAPMO codes, you know, there's differences between the two.

Then you've got people like Chicago or Massachusetts who do something even different.

But when you look at these codes and standards, you can find people on the 2012 code.

But with technology and how we're getting faster with these building information management systems where you're designing and you're linking things to real products and 3D modeling and those type of things, I mean, the possibilities are endless.

But you also have to have a little hesitation when you look at things because, I mean, think about the building in New York that's leaning to the side, right? where they take a building that's been sitting there for decades and there's never been any issues, and now you have an architect and a firm that's gone through and they've put in new beams and changed, they've added things, and it didn't turn out the way it was supposed to, right? Things, they buckled, there were some issues.


What are you hearing from your constituents as far as like challenges that need to be addressed in your organization?

You know, when you look at the challenges today, technology just continues to advance so fast.

But we have a, I mean, just looking at codes, let's look at code cycles first.

When you think about codes, you know, I'm not a proponent of designing to a code.

And the reality is if you look across the U.S., just looking at the U.S., I mean, we're a global organization, but when you look across the U.S., whether you're looking at the ICC codes or you're looking at the IAPMO codes, you know, there's differences between the two.

Then you've got people like Chicago or Massachusetts who do something even different.

But when you look at these codes and standards, you can find people on the 2012 code.

But with technology and how we're getting faster with these building information management systems where you're designing and you're linking things to real products and 3D modeling and those type of things, I mean, the possibilities are endless.

But you also have to have a little hesitation when you look at things because, I mean, think about the building in New York that's leaning to the side, right? where they take a building that's been sitting there for decades and there's never been any issues, and now you have an architect and a firm that's gone through and they've put in new beams and changed, they've added things, and it didn't turn out the way it was supposed to, right? Things, they buckled, there were some issues.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.