Buildable {ish}

Brian and Alex
  • 5,0 (7)
  • Nghề nghiệp
  • Hằng tuần

A smart, funny podcast cohosted by a structural engineer and a project manager – two professionals who live day-to-day in construction coordination. We take a candid, smart, and often humorous look at what really happens between design intent and finished construction. Each episode breaks down a common project challenge; misaligned specs, missing details, inspection surprises, field fixes, and the infamous “that wasn’t on the drawings” moment. Keywords: Buildable, Buildableish, Buildable ish, Build, Buildable(ish), Buildable (ish)

  1. Hold For Clarification: Means & Methods

    5 ngày trước ·  Nội dung tặng thêm

    Hold For Clarification: Means & Methods

    “Means and Methods.”  It’s one of the most misunderstood phrases in construction—and one of the easiest ways for a routine field decision to quietly become an engineering problem.  In this Hold for Clarification minisode, Brian and Alex explain where means and methods begins, where it ends, and why changing how something is built can sometimes change the design itself. From temporary shoring and sequencing to documentation, liability, and engineering review, they explore the blurry line between contractor responsibility and design responsibility.  Leave feedbackfor Brian and Alex  ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠brian@buildableish.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠    LINKS: Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ LinkedIn:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠⁠ Show Notes  Means and Methods includes:  • Sequencing and staging. • Temporary supports and shoring. • Equipment access and installation. • Construction procedures that do not change the design intent.  It stops being Means and Methods when:  • The load path changes. • Structural behavior changes. • Temporary conditions become permanent. • Engineering assumptions are affected.  Takeaways:  • Engineers design the outcome—not the construction choreography. • Physics doesn’t negotiate. • If the math changes, engineering review is required. • A field decision is not automatically a contractor decision. • Good documentation today prevents expensive surprises tomorrow.  “Means and methods ends the moment the math changes.”  This episode is part of our Hold for Clarification series—short dives into the words and phrases we hear every day in design and construction that sound straightforward but often create confusion, coordination issues, and costly mistakes.

    12 phút
  2. In the Room Where It Happens: Women in Engineering

    24 thg 6

    In the Room Where It Happens: Women in Engineering

    Women in engineering don’t just have to solve technical problems—they often have to prove they belong in the room before anyone listens to the solution.  Brian and Alex tackle the realities of being a woman in a traditionally male profession, from being mistaken for support staff and having expertise questioned to navigating imposter syndrome, jobsite culture, and the subtle biases that still exist throughout design and construction. Through personal stories, hard-earned lessons, and candid discussion, this episode explores what it takes to establish authority, earn trust, and advocate for others in the industry.  If you've ever watched the smartest person in the room get talked over, had to re-establish your credibility in every meeting, or wondered how the industry can continue improving for future generations of engineers…this one's for you.  Leave feedbackfor Brian and Alex  ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠brian@buildableish.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠    LINKS: Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ LinkedIn:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠⁠ Show Notes  Chapter 1 – Getting in the Room  Being mistaken for support staff instead of the engineer  First impressions and assumed roles in design meetings  Why women often have to repeatedly establish authority  The balancing act between confidence and being labeled 'abrasive'  How visible leadership support changes careers    Chapter 2 – Speaking with Authority  Vendors, consultants, and the credibility gap  The PE license versus perceived expertise  Getting talked over, interrupted, or ignored in meetings  Advocating for colleagues and redirecting conversations  The hidden cost of over-preparing to avoid being questioned    Chapter 3 – Owning the Room During Construction  Jobsite interactions and contractor assumptions  When expertise gets questioned until a man repeats it  PPE, safety gear, and field conditions not designed for women  Building credibility through competence and problem-solving  Why respect often arrives only after the problem is solved    Chapter 4 – Staying in the Room  Inspections, closeout meetings, and maintaining authority  Imposter syndrome in engineering and leadership  Women in STEM: progress, challenges, and industry trends  Documentation as a tool for credibility and protection  Creating a culture where expertise matters more than assumptions    Key Takeaways  Authority should come from expertise and credentials, not assumptions  Advocating for colleagues can dramatically change workplace culture  Many biases are subtle, unintentional, and still impactful  Documentation and preparation remain powerful professional tools  Engineering is strongest when every qualified voice is heard

    53 phút
  3. Scope Gap: The Roof

    17 thg 6 ·  Nội dung tặng thêm

    Scope Gap: The Roof

    Everybody needs something on the roof.  Mechanical has equipment. Electrical needs conduits. Plumbing needs vents. Architecture wants screens. Structural gets to support all of it.  The roof isn't usually the problem.  The problem is that everyone assumes someone else coordinated it.  In this Scope Gap minisode, Brian and Alex climb onto one of the most crowded and overlooked parts of a building. From equipment supports and conduit penetrations to roof curbs, screens, warranties, and future expansion, they explore why rooftop coordination often falls into the gaps between disciplines—and why those gaps usually show up after the roof is already finished.  Leave feedbackfor Brian and Alex  ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠brian@buildableish.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠    LINKS: Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ LinkedIn:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠⁠ Show Notes  The roof assumes:  Everyone coordinated their equipment.  The penetrations are accounted for.  The supports are designed.  The future needs were considered.  In practice, it becomes:  A coordination problem nobody owns.  A warranty nobody can maintain.  A very expensive core drill.  Takeaways:  Coordinate rooftop equipment before finalizing layouts.  Identify all penetrations, supports, and future expansion needs early.  Don't assume another discipline is managing roof coordination.  If the roofing contractor is already gone, you're probably out of good options.  "The roof problems rarely come from the roof itself. They come from all the decisions that showed up after it was finished."

    19 phút
  4. Baton Drop: Handoffs Gone Wrong

    10 thg 6

    Baton Drop: Handoffs Gone Wrong

    Every project starts with a kickoff meeting, a schedule, and a team that swears everything is documented. Then somebody leaves.  Brian and Kyle head into the chaotic world of project handoffs — where meeting minutes vanish, email archives disappear, RFIs are marked resolved without answers, and institutional knowledge walks out the door. From inherited projects and undocumented owner decisions to handoff binders filled with notes that simply say 'See Email,' this episode explores why project transitions can create more risk than the design itself.  If you've ever inherited a project halfway through design, searched years of email chains for answers, or discovered that nobody remembers who approved a critical decision…this one's for you.    Leave feedbackfor Brian and Alex  ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠brian@buildableish.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠    LINKS: Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ LinkedIn:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠⁠ Show Notes  Chapter 1 – The Exchange Zone  • Why project handoffs break down during design  • Owner requests that never make it into the drawings  • Tribal knowledge versus documented decisions  • Managing owner expectations after a PM transition  • Why documenting assumptions early matters  Chapter 2 – See Email  • Deleted inboxes and disappearing project history  • Bid logs without context and procurement archaeology  • Value engineering decisions nobody remembers making  • Personal emails, shared drives, and institutional memory  • Why 'See Email' is not a documentation strategy  Chapter 3 – Reopening the RFI  • Construction-phase handoffs and unresolved issues  • RFIs marked closed but never actually answered  • How vague contractor questions create expensive misunderstandings  • Getting contractor, owner, and design-team buy-in  • Resetting expectations when the new PM takes over  Chapter 4 – The Binder Trap  • Punch lists versus warranty items  • Closeout packages that create more confusion than clarity  • Live walkthroughs between outgoing and incoming PMs  • Collaborative checklists and transition planning  • Treating handoffs as a formal project phase  Key Takeaways  • Assumptions vanish when they are not written down  • Project knowledge is often more valuable than project files  • Archived emails can save years of confusion and rework  • A closed RFI is not resolved unless everyone agrees on the answer  • The best handoff is one that happens before someone walks out the door

    35 phút
  5. Scope Gap: Slabs on Grade

    3 thg 6 ·  Nội dung tặng thêm

    Scope Gap: Slabs on Grade

    Scope Gap is where coordination goes to die.  The concrete isn't usually the problem.  The problem is everything hidden inside it.  In this Scope Gap minisode, Brian and Alex dig into one of the most coordination-heavy elements of any project: the slab on grade. From floor boxes and floor drains to control joints, conduit, reinforcement, and slab depressions, they explore how scope gaps get buried before the concrete truck even arrives—and why those gaps often become demolition plans later.  Leave feedbackfor Brian and Alex  ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠brian@buildableish.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠    LINKS: Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ LinkedIn:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠⁠ Show Notes  The slab assumes:  Everyone coordinated the utilities.  The plumbing elevations are correct.  The conduit routing fits.  The control joints were coordinated.    In practice, it becomes:  A coordination problem nobody owns.  A field decision made under schedule pressure.  A very expensive concrete saw.    Takeaways:  Coordinate utilities before the pour.  Verify slab depressions, leave-outs, and floor boxes early.  Don't assume someone else owns slab coordination.  If the concrete truck is already on site, you're probably out of good options.    "The slab problems rarely come from bad concrete. They come from decisions that never met each other before the pour."    This episode is part of our Scope Gap series – short dives into the spaces between disciplines, responsibilities, and assumptions where construction problems love to hide.

    18 phút
  6. Scope Safari: Hunting the Ever-Expanding Project

    27 thg 5

    Scope Safari: Hunting the Ever-Expanding Project

    Every project starts with a clean scope, a reasonable budget, and a confident owner. Then somebody says, “While you’re at it…”  Brian and Alex head into the wild world of scope creep — where one extra office triggers structural redesigns, “future-proofing” quietly doubles costs, and punch lists somehow turn into owner wish lists. From vague contract language and moving project targets to value engineering confusion and last-minute upgrades, this episode explores how projects slowly evolve into something nobody originally agreed to build.  If you’ve ever sat through a meeting where someone casually suggested “just one more change,” watched an RFI become a redesign, or discovered the owner expected something that was never actually in the drawings…this one’s for you.  Leave feedbackfor Brian and Alex  ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠brian@buildableish.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠    LINKS: Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ LinkedIn:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠⁠ Show Notes  Chapter 1 – Spotting the Tracks  How “small” owner requests snowball into major redesigns  Scope creep during programming and schematic design  Future-proofing and overdesign that never gets used  FCA reports, outdated deficiency lists, and shifting priorities  Why documenting assumptions early matters  Chapter 2 – Herding Cats with Contracts  Vague contract language and “as needed” scope traps  Defining deliverables, exclusions, and responsibility gaps clearly  Design-build repricing games and constant scope negotiation  Pre-engineered building surprises and hidden assumptions  Why alternates and allowances need tight definitions  Chapter 3 – The Migration of Change Orders  Owner walkthroughs and late-stage “minor” changes  Unforeseen conditions becoming upgrade opportunities  Contractors and subs pushing alternate products midstream  Schedule impacts, stacked trades, and morale fatigue  Using RFIs and change orders to control scope creep  Chapter 4 – Punch List or Safari Cleanup?  Punch list items becoming owner upgrade requests  Warranty confusion and last-minute “clarifications”  Municipal requirements appearing after construction is complete  Defining substantial completion clearly  Why project autopsies help prevent future chaos  Key Takeaways  Scope creep rarely starts with huge changes — it starts with vague requests  Every project change has cost, schedule, and coordination impacts  Documentation and meeting minutes are survival tools  Tight contracts and clearly defined deliverables prevent chaos later  Lessons learned meetings are one of the best training tools a team can have

    44 phút
  7. The Spec Trap: Maintain 1-Hour Rating

    20 thg 5 ·  Nội dung tặng thêm

    The Spec Trap: Maintain 1-Hour Rating

    It sounds straightforward — until someone cuts a six-inch hole through the wall and fills it with whatever was in the truck. In this Spec Trap minisode, Brian and Alex dig into one of the most abused phrases in construction documents: “Maintain 1-hour rating.” From mystery firestop materials to field-built “solutions” that were never tested, they break down how vague life safety language creates confusion, failed inspections, and expensive late-stage fixes.  Along the way:  Someone uses spray foam where it absolutely should not go.  Nobody can find the UL assembly.  and a crash-test dummy loses its head in a story neither host will ever forget.  Leave feedbackfor Brian and Alex  ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠brian@buildableish.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠    LINKS: Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ LinkedIn:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠⁠   Show Notes  The phrase assumes:  Someone detailed the required assembly.  The trades coordinated penetrations ahead of time.  Everyone understands the tested firestop system.  The installer knows what product belongs there.  In practice, it becomes:  Oversized penetrations patched in the field.  Spray foam and red caulk used as universal repair products.  Firestop systems chosen after installation instead of before.  Trades assuming “someone else” owns the rating continuity.  It often leads to:  Failed life safety inspections.  Delayed occupancy approvals.  RFIs after the wall is already closed.  Last-minute patchwork that nobody wants to sign off on.    Takeaways  Specify the tested assembly, not just the rating.  Coordinate penetrations before rough-in.  Clearly define responsibility for maintaining rated assemblies.  Require approved firestop systems and inspection documentation.  “Maintain 1-hour rating sounds simple — until the inspector asks what UL system you used and the entire room suddenly gets quiet.”   This episode is part of The Spec Trap series — short dives into spec language that sounds professional but quietly causes problems in the field.

    21 phút
  8. The Great Brain Drain

    13 thg 5

    The Great Brain Drain

    Losing a team member mid-project is frustrating. Losing them along with every design decision they ever made? That’s chaos. Brian and Alex break down what really happens when the “brain trust” leaves the building. From undocumented design intent and mystery file folders to confused clients and shifting specs, this episode dives into how quickly a project can unravel when knowledge isn’t shared. If you’ve ever opened a file labeled “FINAL_v7_forREAL_iMEANit,” tried to decode someone else’s half-finished model, or explained a design decision you didn’t make…this one’s for you.  Leave feedbackfor Brian and Alex  ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠brian@buildableish.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠    LINKS: Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ X: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ LinkedIn:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠⁠⁠ Show Notes  Chapter 1 – The Vanishing Point  Long projects = inevitable team turnover (sometimes multiple times)   Why documenting design intent and decisions early is critical   Meeting minutes and decision summaries (and where AI helps…or doesn’t)  Shared file systems, version control, and avoiding “desktop hoarding”   Managing owner expectations and capturing their quirks, preferences, and approvals  Chapter 2 – Spec Roulette  What changes when someone leaves vs. gets let go mid-project   Keeping specs aligned with original design intent through transitions   The importance of version control and updating bid sets immediately   Documenting vendor quotes and assumptions to avoid surprises later   Maintaining relationships and communicating confidence during uncertainty  Chapter 3 – Field Day without a Guide  Assigning a new point of contact quickly to keep projects moving   Maintaining RFI and submittal turnaround during team transitions   Avoiding the “check their old emails” trap with inbox triage    Protecting scope in the field when history is unclear   Managing team morale and keeping communication clear on site    Chapter 4 – Punch List or Treasure Hunt?  Gaps in drawings and specs that show up late in construction   Verifying installations match submittals and chasing missing closeout docs   Creating “as-constructed” record drawings when design history is incomplete   Rebuilding O&M info and leaning on manufacturer reps   Using post-mortems to understand what went wrong and improve processes    Key Takeaways  Document early and often. Design memory fades fast   Assign backups for every critical role and responsibility   Keep files, specs, and drawings organized, dated, and accessible   Manage owner expectations and maintain strong vendor relationships   Recognize team effort and learn from every transition

    47 phút
Xem tất cả (20)

Xếp Hạng & Nhận Xét

5
/5
7 Xếp hạng

Giới Thiệu

A smart, funny podcast cohosted by a structural engineer and a project manager – two professionals who live day-to-day in construction coordination. We take a candid, smart, and often humorous look at what really happens between design intent and finished construction. Each episode breaks down a common project challenge; misaligned specs, missing details, inspection surprises, field fixes, and the infamous “that wasn’t on the drawings” moment. Keywords: Buildable, Buildableish, Buildable ish, Build, Buildable(ish), Buildable (ish)

Thông Tin

  • Nhà sáng tạo
    Brian and Alex
  • Năm hoạt động
    2 N
  • Tập
    20
  • Xếp hạng
    Sạch
  • Bản quyền
    © Brian and Alex
  • Trang web chương trình
    Buildable {ish}