Why do engineering organizations often struggle as they scale from 10 to 100 engineers? This topic identifies three predictable inflection points: around 15 engineers, where informal coordination breaks; around 35, where culture and engineering practices must become explicit; and around 70, where bureaucracy can slow execution. The episode argues that scaling problems are structural, not personal leadership failures. It recommends architecture decision records, stronger onboarding, management development, decision-rights frameworks, explicit ownership, senior engineering density, and deliberate feedback loops to preserve speed, judgment, culture, and purpose as organizations grow

Why do build-versus-buy decisions often go wrong in technology organizations? The episode argues that the choice should not begin with cost, speed, or vendor features, but with one central question: is the capability inside or outside the organization’s zone of differentiation? It outlines common failure modes, including poor cost comparisons, wrong decision ownership, and treating build versus buy as a simple binary. The episode then presents a seven-question framework covering total cost of ownership, urgency, lock-in, vendor risk, internal capacity, reversibility, and AI-specific uncertainty

Organizations are deploying AI faster than governance functions can adapt, creating a critical risk gap. Most companies lack visibility into their AI systems, exposing them to data privacy, liability, IP, and bias risks. The issue isn’t lack of intent but structural misalignment between speed and oversight. Leading organizations address this with cross-functional governance, real-time AI inventories, proportionate risk frameworks, and early-stage impact assessments. The goal isn’t to slow AI adoption—but to move with clarity and control. Those who build governance capabilities now will outperform those waiting for regulatory certainty that may never fully arrive.