When a mislabeled breaker or an out‑of‑date floorplan turns a routine maintenance task into a multi‑hour outage, the failure rarely stemmed from bad hardware — it came from bad documentation. In this episode Alex Morgan interviews Michael Harrington to expose how documentation hygiene (labels, as‑builts, change logs, and accessible drawings) sits at the intersection of operations, vendor coordination, and business continuity. We frame the problem with a concise real‑world hook, then unpack the root causes—trade handoffs, temporary fixes made permanent, and poor version control—and tradeoffs property teams face when deciding how “complete” documentation needs to be. Michael shares pragmatic examples from his portfolio, sizing the problem in operational dollars and describing affordable, repeatable practices to keep documentation living and useful. Listeners will leave with three concrete actions to reduce mean time to repair and a realistic plan for making documentation part of capital and operational workflows.

Buildings don’t fail because the tech was bad — they fail because the knowledge left with the project team. This episode digs into the routine but under‑discussed problem of project handoffs: incomplete documentation, missing firmware notes, inaccessible spare parts lists, and ambiguous vendor responsibilities that turn turnovers into months of firefighting. Alex Morgan interviews Michael Harrington to expose the most common handoff failure modes, the operational and financial costs they create, and realistic governance and process fixes that work across owners, general contractors, IT, and facilities teams. Listeners will hear concrete examples from real projects, practical checklists you can adapt for your next turnover, and a simple governance framework that prevents a completed job from becoming tomorrow’s outage. The tone is practical and non‑technical — focused on decisions, tradeoffs, and repeatable processes property and IT leaders can implement immediately.

When a modest network switch or a replacement access controller sits on a pallet in a warehouse, it’s either insurance or money wasted. This episode walks property operators, IT leaders, and facilities managers through a practical, repeatable approach to spare‑parts and lifecycle planning for building technology. Alex Morgan interviews Michael Harrington to explore why spares matter, how undocumented BOM drift and procurement lead times create hidden downtime risk, and what an efficient spare strategy looks like in practice. Listeners will hear concrete tradeoffs—cost versus availability, testing versus storage, and standardization versus tenant needs—and leave with an operational checklist for determining which parts to hold, how to rotate and test inventory, and how to bake spares into capital and vendor conversations. The conversation is tactical, non‑technical, and aimed at decisions teams can implement within months.

Buildings fail in surprising ways because people haven't practiced the response. In this episode Alex Morgan sits down with Michael Harrington to walk through how structured tabletop exercises and runbooks turn chaotic outages into controlled recovery plans. We explain why simulations matter for access control, BMS, power, and networks; how to scope scenarios so drills are realistic without disrupting tenants; and what success looks like when a plan is tested against actual operational constraints. Listeners will get concrete exercise templates, roles to include, simple metrics to measure readiness, and guidance on translating tabletop outcomes into capital and operational adjustments. This is for property owners, facilities leaders, and IT managers who need practical, repeatable ways to reduce downtime and make investment decisions grounded in operational reality—without vendor hype or deep technical configuration.

Many modern buildings quietly host networks that facilities and IT never approved: contractor Wi‑Fi for commissioning, tenant IoT meshes, vendor‑managed sensors, and rogue access points. These 'shadow networks' cause RF interference, create unmanaged attack surface, complicate troubleshooting, and extend mean time to repair. In this episode Alex Morgan talks with Michael Harrington to map where undocumented wireless and IoT show up, why they persist, and pragmatic ways property teams detect, prioritize, and remediate them without alienating tenants. We break down operational causes, tradeoffs between enforcement and continuity, and how to bake detection and governance into lifecycle planning so buildings stay resilient and serviceable. Listeners will hear real-world examples, low‑friction discovery techniques, governance patterns that respect tenant needs, and a concise checklist property teams can use on day one to reduce blind spots and speed incident resolution.

Many property teams live in reactive vendor loops—late-night call trees, rotating contractors, and tenants frustrated by repeat outages. This 10‑minute case‑study interview opens with a human 2am alarm vignette and moves into a tightly scoped conversation with Michael Harrington (senior property manager) and an operations lead who built a lean on‑site tech ops function. We surface measurable outcomes owners care about—typical MTTR reductions around 20–35%, 30–50% fewer vendor escalations, and pilot payback windows often within a single lease cycle—then translate those results into an operational blueprint: when to pilot versus scale, three compact role profiles, on‑call design that limits burnout, and three short playbooks that cut repair time. Guests are pre‑briefed to avoid HR, payroll, or vendor endorsements. The episode closes with three immediate actions and a Starter Pack teaser (role templates, 30‑day pilot checklist, sample playbooks, and a KPI dashboard) available on the show hub.

Procurement decisions can lock operations into costly rip-and-replace cycles. This episode opens with a tense, audio-first cold open: a frustrated operator clicks a locked “export” button, the UI clicks, then a subtle alarm tone underscores the risk. Host Alex Morgan interviews Michael Harrington (senior property manager), an independent systems integrator, and a procurement practitioner to deliver vendor-neutral, operational tactics listeners can use immediately. We identify practical proposal red flags (closed export formats, missing APIs, single local control paths), walk through staged exit planning (data snapshots, rollback workflows, budgeted optionality) and give explicit, audio-friendly acceptance tests you can run—e.g., export a 30-day snapshot to CSV/JSON and import it into an open-source viewer, or verify a documented API endpoint returns device lists. Guests share anonymized case studies, offer a contract-neutral acceptance criterion example listeners can read back in meetings, and translate lessons into three immediate actions. The episode ends with a clear CTA to download the Vendor Exit Checklist at builtwiredsecured.com/exit-checklist.

The episode opens with an anonymized, cinematic vignette: a newly instrumented floor reduces HVAC complaints but sparks occupant unease—after simple policy and communication changes the same property saw complaints drop by roughly 40%. Host Alex is joined by a senior property manager and a privacy/analytics engineer to translate that story into concrete steps any team can apply. The conversation stays operational and vendor-neutral: we walk listeners through a rapid 5-minute sensor audit they can run during the episode, model a 30–60s read-aloud tenant notice listeners can copy, and share a lightweight approval checklist for new sensor projects. The episode closes with three immediate actions to apply on-site, a link to a downloadable privacy checklist and templates, and an invitation to submit audit results to the show hub for a future follow-up episode that tracks outcomes. No legal advice—just practical controls, communications, and governance that protect trust.

Physical connectivity decisions—where fiber enters a campus, how risers are routed, how tenant demarcation is handled—are quietly critical and stubbornly long-lived. This episode opens with a short, anonymized scene where a single construction cut severed a building’s only service entry and brought tenants to a standstill, then translates that failure into an actionable framework owners, FMs, and IT leaders can use today. Guests include a senior property manager and a telco coordination lead who walk through common single-point failures, pragmatic design tradeoffs between diversity and cost, and the operational playbooks that speed recovery after a fault. The conversation stays vendor-neutral and decision-focused: how to specify diverse entry paths, manage carrier handoffs, document physical routes, and test restoration procedures. Listeners leave with three concrete inspection checkpoints, a template list of questions for carrier coordination, and clear next steps to harden physical connectivity without overcomplicating builds.

We follow a tight through-line: two neighboring tenant floors experience the same outage but diverge after different power decisions. An anonymized micro-case compares outcomes one floor endured ~4 hours of downtime with lost services and tenant disruption; the other reduced downtime to under 30 minutes after modest UPS sizing, clear ownership boundaries, and a documented testing cadence. Early in the episode listeners hear a three-item audible checklist they can use immediately: (1) define and agree critical loads, (2) match redundancy to downtime tolerance, (3) require testable handover documentation. The main segment diagnoses common root causes undermetering, mixed tenant loads, ambiguous metering/ownership and compares backup strategies (tenant vs building UPS, generator sizing philosophy, centralized vs distributed batteries) using decision heuristics rather than product recommendations. The close gives operational practices, repeatable questions for design reviews, and points listeners to the show's resource hub for a downloadable checklist. Listeners are reminded to consult licensed electricians and local code officials for implementation or compliance.