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 

⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠[email protected]⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ 

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