Buildable{ish}

“Install per manufacturer’s instructions.” In this episode of The Spec Trap, Brian and Alex unpack what really hides behind that seemingly harmless sentence. From blocking that never made it onto the drawings to maintenance clearances, seismic bracing, structural supports, specialty anchors, and coordination conflicts, they explain why manufacturers’ installation requirements often contain critical design information that nobody discovers until the product has already been ordered. Listen here: Apple Podcasts: https://lnkd.in/e3yFN83D Spotify: https://lnkd.in/e3m7uyav #Podcast #Engineering #Architecture #ProjectManagement #Buildable #Build #Construction

“Install per manufacturer’s instructions.” It’s one of the shortest notes in a specification—and one of the longest change orders on a project. The manufacturer usually isn’t the problem. They’re simply documenting what their product actually needs to perform as intended. The trouble starts when those requirements aren’t discovered until after the product has been selected, ordered, or delivered to the jobsite. In this episode of The Spec Trap, Brian and Alex discuss: • Why manufacturers’ instructions often contain critical design requirements • Hidden structural supports, blocking, anchorage, and maintenance clearances • Why performance specifications don’t eliminate coordination • How the submittal process should catch these issues before procurement 🎧 New minisode available now. Listen here: Apple Podcasts: https://lnkd.in/e3yFN83D Spotify: https://lnkd.in/e3m7uyav #Podcast #Engineering #Architecture #ProjectManagement #Buildable #Build #Construction

Why is this longer than my project specifications? Who hurt these people? Listen here: Apple Podcasts: https://lnkd.in/e3yFN83D Spotify: https://lnkd.in/e3m7uyav

“Install per manufacturer’s instructions.” It’s one of the most common phrases in construction specifications—and one of the easiest ways to create expensive surprises. If you’ve ever opened a submittal and realized the installation manual contains more design requirements than the drawings… this one’s for you. Listen here: Apple Podcasts: https://lnkd.in/e3yFN83D Spotify: https://lnkd.in/e3m7uyav #Podcast #Engineering #Architecture #ProjectManagement #Buildable #Build #Construction

Episode 11 is out now. If you can spot all the references, you may have a future as a physical security consultant. Listen here: Apple Podcasts: https://lnkd.in/e3yFN83D Spotify: https://lnkd.in/e3m7uyav #Podcast #Engineering #Architecture #ProjectManagement #Buildable #Build #Construction #PSRDM

Good security isn’t about adding more hardware. It’s about making better design decisions. One of the biggest takeaways from Episode 11 is that many security features are added late in design after someone reacts to a headline or requests “more security.” Good security design begins with understanding the actual risks, integrating protection into the architecture, and creating layers that work together—not simply adding visible security features after the fact. In this episode we discuss: • Why “security theater” creates the illusion of protection • Risk and threat assessments before design begins • Designing buildings that feel welcoming without sacrificing safety • Why layered security outperforms single solutions • How architects, engineers, and security consultants should collaborate from day one • Why the best security systems are often the ones people never notice The best security feature isn’t the most obvious one. It’s the one that quietly works exactly as intended. Episode 11 — Panic Rooms and Parking Lots is available now. Listen here: Apple Podcasts: https://lnkd.in/e3yFN83D Spotify: https://lnkd.in/e3m7uyav

Security Theater Listen here: Apple Podcasts: https://lnkd.in/e3yFN83D Spotify: https://lnkd.in/e3m7uyav

When an owner says, “Make it more secure,” what does that actually mean? In this episode of Buildable{ish}, Brian welcomes physical security consultant Herb Ubbens to explore the difference between real security and what security professionals call security theater—design features that create the illusion of safety without actually reducing risk. Listen here: Apple Podcasts: https://lnkd.in/e3yFN83D Spotify: https://lnkd.in/e3m7uyav #Podcast #Engineering #Architecture #ProjectManagement #Buildable #Build #Construction #PSRDM #PhysicalSecurity

We hope you enjoyed this week's minisode! Can you spot all the hidden references from Redlines & Regrets Episode 2? Listen here: Apple Podcasts: https://lnkd.in/e3yFN83D Spotify: https://lnkd.in/e3m7uyav

If a requirement is important enough to enforce… is it important enough to draw? General notes are intended to clarify a project. Too often, they become a hiding place for scope that should have been obvious from the drawings. In our newest Redlines & Regrets minisode, General Notes Roulette, we discuss why this happens and how it creates unnecessary RFIs, change orders, cost disputes, and frustration for everyone involved. We cover topics including: • Why critical scope should never live only in the general notes. • How boilerplate language quietly creates project risk. • Why contractors naturally prioritize drawings over dense text. • Practical ways designers and project managers can make critical information impossible to miss. One of my favorite takeaways from the episode: “If it’s important enough to enforce, it’s important enough to draw.” If you work in architecture, engineering, construction, or project management, you’ve almost certainly played a round of General Notes Roulette—whether you realized it or not. 🎧 Give it a listen, and let us know: What’s the most expensive thing you’ve ever found buried in a set of general notes? Listen here: Apple Podcasts: https://lnkd.in/e3yFN83D Spotify: https://lnkd.in/e3m7uyav #Buildableish #AEC #Construction #Architecture #Engineering #ProjectManagement #DesignCoordination #Specifications #ConstructionDocuments