Engineering Evolved

Tom Barber

Where business meets innovation and technology drives transformation. Engineering Evolved is the podcast for leaders navigating the forgotten ground between startup chaos and enterprise bureaucracy. If you're building and scaling teams at organizations in the middle — where startup rules no longer apply and enterprise playbooks are far too large — this show is for you. Hosted by Tom Barber, each episode explores the real challenges facing today's engineering leaders: scaling systems without breaking them, building high-performing teams, aligning engineering strategy with business goals, and making technical decisions that drive measurable impact. Whether you're a Director of Engineering, VP of Technology, CTO, or an IC engineer stepping into leadership, you'll find practical insights drawn from real-world experience — not theoretical frameworks that only work on whiteboards. Topics include: Scaling engineering teams and systems for growth Building effective engineering culture Bridging the gap between technical and business strategy Leadership tactics that actually work in the messy middle Making architectural decisions with limited resources Navigating organizational complexity Engineering Evolved — guiding today's leaders through the evolution of engineering. New episodes drop weekly. Subscribe now and join the conversation about what it really takes to lead engineering in the modern era.

  1. 6d ago

    The $13K Company Backlog: Private Equity's Capital Return Crisis in 2025

    Private equity firms are facing an unprecedented challenge with a backlog of 13,000 companies. The biggest issue for 2025 isn't raising capital or sourcing deals—it's successfully returning capital to investors after buying at market peaks. Show Notes Episode Overview A concise analysis of the private equity industry's current crisis: managing a backlog of 13,000 companies while struggling to return capital to investors. Key Topics Covered The 13,000-Company Backlog Unprecedented number of portfolio companies awaiting exits Industry-wide challenge affecting firms of all sizes Redefining what success means in private equity The Capital Return Challenge Why returning capital has become the #1 priority for 2025-2026 Shift from traditional metrics of success (fundraising and deal flow) Impact on limited partners and fund performance Market Timing Issues Consequences of buying at market peaks The "top of the bubble" problem Current valuation challenges and exit environment Key Takeaways The private equity industry faces a structural challenge with 13,000 companies in the exit pipeline Capital return has superseded fundraising and deal sourcing as the primary challenge Firms that bought at peak valuations are particularly vulnerable The traditional definition of private equity success is being rewritten Relevant for: Private equity professionals Limited partners and institutional investors M&A advisors and investment bankers CFOs and business owners considering exits Financial market analysts Chapters 0:00 - Introduction: The Private Equity Challenge 0:11 - The 13,000-Company Backlog Crisis 0:19 - Capital Return: The New Priority 0:28 - The Peak Valuation Problem

    1 min

  2. Jun 16

    Your Users Don't Care If It's AI - They Just Want Results

    Tom Barber challenges the AI hype cycle, arguing that users care about outcomes, not architecture. Learn why slapping an 'AI-powered' label on everything is the wrong approach, and discover how to thoughtfully integrate LLMs into products without falling into common pitfalls like dependency on unstable APIs or unnecessary chatbot interfaces. Show Notes Episode Overview Tom Barber returns with a critical examination of AI integration in modern software development, challenging teams to focus on user outcomes rather than jumping on the AI hype train. Key Topics Covered The AI Marketing Problem Why 'AI-powered' labels are often meaningless marketingThe difference between machine learning (which has existed for decades) and modern LLMsExamples of invisible AI: spam filtering, fraud detection, map reroutingUsers grade products on consistency, not on the impressiveness of the underlying modelEngineering Considerations for LLM Integration Choosing the right model for your specific use case (Opus, Sonnet, GPT-4, etc.)Tradeoffs between cost, speed, and inference qualityBuilding evaluation systems and fallback pathsManaging latency budgets and graceful degradationHandling API outages from providers like Anthropic and OpenAIThe risks of depending on frontier models that can be deprecatedTrust and Transparency AI as a potential trust liabilityManaging user expectations around hallucinationsThe importance of data provenance and quality (garbage in, garbage out)When and how to disclose AI usage to usersThe ethical obligation to be transparent when AI makes consequential decisionsProduct Strategy Why you can't charge an 'AI tax' on top of existing pricingPricing based on outcomes, not on the technology stackHow to use LLMs to deliver genuine efficiency gainsReducing user overhead and friction through thoughtful AI integrationBeyond Chatbots Why chatbots may be the most inefficient way to interact with LLMsThe challenge: How to integrate LLMs without forcing users to type everythingAsking 'What's now instant that wasn't?' instead of 'How do we add AI?'Innovation opportunities for those who can solve the chatbot problemKey Takeaways Users care about reliable outcomes, not whether you're using AIEngineer for model availability issues and API outages from day oneSelect and tune models specifically for your use case rather than defaulting to frontier modelsBe transparent about AI usage, especially for consequential decisionsFocus on delivering value through AI rather than adding an 'AI-powered' label for marketingThe future belongs to products that leverage LLMs without relying on chatbot interfacesResources Mentioned Various LLM providers: Anthropic (Claude/Opus/Sonnet), OpenAI (ChatGPT-4)Example of model deprecation: Fable model being pulledConnect Engineering Evolved is hosted by Tom Barber. If you found this episode valuable, please leave a rating and review to help other leaders discover the show. Chapters 0:00 - Introduction: Users Don't Care If It's AI1:01 - Machine Learning Has Always Been Here2:19 - The AI Marketing Problem: Selling Architecture vs Outcomes5:16 - Engineering Realities: Models, Consistency, and Reliability10:11 - The Cost of the AI Label: Trust and Pricing14:39 - When Users Do Care: Transparency and Consequential Decisions17:15 - Beyond Chatbots: The Future of LLM Integration

    20 min

  3. 12/15/2025

    The Trio Model: Breaking Down Business-IT Walls for Better Engineering Collaboration

    Engineering leaders learn how the Trio model can eliminate the blame game between business and IT teams. Discover practical strategies for cross-functional collaboration that actually work. The Trio Model: Breaking Down Business-IT Walls Key Topics Covered The Business-IT Dysfunction Problem Why blame games develop between business and IT teamsThe 'technical purgatory' of mid-sized companies (200-1000 employees)Common symptoms: endless backlogs, shadow IT solutions, demoralized engineersWhy Traditional Fixes Fail Hiring more managers: Adds abstraction without contextAdding more engineers: Brooks' Law in actionBetter ticketing systems: Makes misalignment visible but doesn't fix itMore meetings: Creates 'status theater' without decisionsThe Trio Model Explained Three core roles: Business owner, technical lead, designer/analyst/ops leadCo-ownership of outcomes, not just task handoffsClear decision rights to prevent gridlockNot a committee: Explicit authority assignmentImplementation Strategy Which problems warrant a trio (high ambiguity, cross-functional dependencies)Decision rights frameworkShared metrics and accountabilityStarting with 1-2 pilot areasLeadership Requirements Stop bypassing trio processes with 'urgent' requestsProtect trio time and focusHold business owners accountable for outcomesAccept timeline realitiesKey Quotes "If every request is urgent, there's no way for IT to prioritize""Shared ownership of the outcome doesn't mean you can point at someone else when your part goes wrong""The trio owns it can quickly become no one owns it"Action Items Identify 1-2 high-friction problem areasForm pilot trios with clear problem definitionsEstablish shared success metricsReview and iterate after one quarterChapters 0:00 - The Business-IT Blame Game Problem1:56 - Life in Technical Purgatory5:29 - Why Traditional Fixes Don't Work10:09 - Introducing the Trio Model15:51 - Implementation and Decision Rights23:42 - Measuring Success with Shared Metrics24:50 - Leadership Changes Required29:25 - Getting Started: A Practical Approach

    34 min

  4. 12/10/2025

    Why Your Team Rituals Are Optimized for the Wrong Thing

    How many meetings moved your team forward last week? Tom explores why most team rituals fail at building trust and alignment, sharing lessons from NASA JPL and startups on creating ceremonies that actually work. Why Your Team Rituals Are Optimized for the Wrong Thing Key Topics Covered The Missing Middle Challenge Why mid-sized companies (200-1000 employees) face unique coordination challengesToo big for startup osmosis, too small for enterprise playbooksThe need for distributed decision-making without dedicated alignment teamsTwo Contrasting Standup Experiences NASA JPL: Nightly standups across three time zones that built trust and enabled handoffsMedical Startup: Transactional daily standups that created artificial harmonyWhat made the difference: optimization for relationship building vs. status updatesThe Five Dysfunctions of a Team Framework Absence of Trust - Vulnerability-based trust, not competence trustFear of Conflict - Artificial harmony vs. productive disagreementLack of Commitment - What happens when people don't feel heardAvoidance of Accountability - When standards become suggestionsInattention to Results - Individual ego over team successThree Practical Shifts for Better Rituals Shift 1: Surface Vulnerability Leadership modeling uncertainty firstStructured moments for admitting what you don't knowMoving from posturing to problem explorationShift 2: Practice Disagreement Red team rotations in roadmap reviewsMaking challenge a role, not a personality traitEnsuring friction happens constructively in the roomShift 3: Build Shared Context (Not Just Information) The difference between "here's the roadmap" and "here's the trade-off I struggled with"Smaller cross-functional context sessions vs. large all-hands presentationsEnabling distributed decision-making through understanding reasoningKey Questions for Diagnosis How much time was spent on information transfer vs. relationship building?Did anyone admit uncertainty without it being a problem?Was there constructive disagreement that led to better outcomes?Do people understand the reasoning behind decisions, not just the decisions themselves?Resources Mentioned Patrick Lencioni's "The Five Dysfunctions of a Team" (2002)Concept of vulnerability-based trustRed team methodology for productive conflictNext Episode Preview Episode 14: The Product Trio Model - Making it Actually Work in Engineering-Heavy Organizations Chapters 0:00 - The Meeting Problem: Status Theater vs. Real Progress2:20 - The Missing Middle: Mid-Sized Company Challenges4:21 - Tale of Two Standups: NASA vs. Startup11:15 - The Five Dysfunctions Framework16:13 - Three Practical Shifts for Better Rituals23:55 - The Compounding Effect of Trust28:39 - Diagnostic Questions and Next Steps

    32 min

  5. 11/30/2025

    Why Kubernetes Is Probably Wrong for Your Mid-Sized Company

    Engineering leader Tom Barber challenges the default adoption of Kubernetes, sharing why simpler alternatives often serve mid-sized companies better and how to make pragmatic infrastructure decisions. Episode 12: Why Kubernetes Is Probably Wrong for Your Mid-Sized Company Key Topics Covered The Kubernetes Reality Check Why most mid-sized companies don't need Kubernetes complexityThe hidden costs: maintenance, YAML management, and developer experienceReal-world example from NASA: when impressive engineering doesn't solve business problemsUnderstanding Kubernetes Context Origins from Google's Borg system designed for massive scaleCore benefits: fault tolerance, auto-scaling, declarative infrastructureWhy these benefits require significant investment to realizeThe Real Downsides Complexity: Even cloud vendors are building products to hide KubernetesYAML Everything: Config management becomes a people and process problemCost at Scale: Engineering hours, infrastructure, and mental health costsDeveloper Experience: High barrier to entry and friction in feedback loopsPortability Mirage: Cross-cloud deployment still requires deep vendor knowledgeWhen Kubernetes Makes Sense Genuine scale requirements (dozens/hundreds of services)Multiple teams with dedicated platform engineering capacityComplex deployment patterns that serve real business needsPractical Alternatives VMs with Docker: Boring is good, boring is maintainableManaged Container Services: ECS/Fargate, Cloud Run, Azure Container AppsServerless: Lambda, Cloud Functions for event-driven workloadsSimple Deployment Scripts: Often cheaper than cluster managementDecision Framework: Do You Actually Need Kubernetes? What specific problem are you solving?Do you have dedicated team capacity?What's your actual scale (services, teams, traffic)?How frequently do you deploy?Have you exhausted simpler options?Resources Mentioned Free Download: "You Actually Need Kubernetes" Checklist (available in show notes)Consulting: Concept Cloud - Pragmatic infrastructure decisions for mid-sized companiesWebsite: www.conceptcloud.comContact: tom@conceptcloud.comNext Episode Preview Episode 13: "Why Your Engineers and Product Managers Still Don't Talk to Each Other (And How to Actually Fix It)" Engineering Evolved is the podcast for engineering leaders at mid-sized companies who are tired of getting advice that only works for startups or enterprises. Chapters 0:00 - Introduction: The Kubernetes Controversy3:00 - A Personal Story: Getting It Wrong at NASA4:58 - Understanding Kubernetes: Context and Core Benefits7:07 - The Real Downsides: Complexity, Cost, and Developer Experience10:49 - When Kubernetes Actually Makes Sense13:39 - Practical Alternatives to Kubernetes15:51 - Decision Framework: Do You Actually Need It?18:36 - Wrap-up and Next Episode Preview

    20 min

  6. 11/16/2025

    You Don't Need Kubernetes: Right-Sizing Platform Engineering for Mid-Size Companies

    In this episode of Engineering Evolved, Tom Barber discusses the pitfalls of over-engineering platform infrastructure, particularly for mid-sized companies. He shares insights from his experience at NASA's Jet Propulsion Laboratory, emphasizing the importance of right-sizing infrastructure to match team needs and capacity. The episode covers the build versus buy framework, the challenges of internal tooling, and the significance of documentation and automation in maintaining efficient operations.

    36 min

  7. 11/09/2025

    How to Sunset a Legacy System Without Destroying Team Morale

    Summary In this conversation, Tom Barber discusses the challenges organizations face when dealing with legacy systems and the importance of recognizing the human element in system migration. He emphasizes that migration is not just a technical project but a transition that impacts people's identities and roles within the organization. Takeaways Think about your current environment for a second.Do you have systems running that are older than some of your engineers?Maybe it's that monolithic application written in a language nobody wants to touch.Maybe it's hardware that needs special handling.Or maybe it's just tribal knowledge locked in the heads of three people.Not if, but when, that time comes.You can treat it like a purely technical project.It's a transition that affects people's identities.A transition that affects people's identities, their expertise.Their sense of value to the organization. (00:00) - Intro (00:32) - Title (01:16) - The Challenge of Sunsetting Legacy Systems (05:59) - Principals for Successful Legacy Migration (11:52) - Creating a Culture of Evolution

    18 min

  8. 11/09/2025

    The First 90 Days of Your Modernization Initiative

    Summary In this episode of Engineering Evolved, Tom Barber discusses the critical first 90 days of a modernization initiative for engineering directors. He emphasizes that success is not solely about technology but about understanding the business pain, building trust, and navigating organizational dynamics. The episode provides a week-by-week action plan, highlighting the importance of quick wins, effective communication, and avoiding common pitfalls in modernization efforts. Takeaways The first 90 days will make or break your initiative.It's about trust, momentum, and not declaring war on allies.Understand the business pain that led to your hiring.Your job isn't to fix everything but to prove you can be trusted.Conduct a 10-day discovery sprint to clarify needs.Weeks one and two should focus on listening and mapping.Identify a quick win that builds credibility.Stay engaged during the execution of the quick win.Communicate your vision and reset expectations with leadership.Avoid common pitfalls like ignoring the human side of technology. (00:00) - Intro (00:31) - Title (01:13) - The Crucial First 90 Days (07:48) - Week-by-Week Action Plan (13:58) - Communicating the Vision (19:16) - Conclusion and Next Steps

    21 min
See All (16)

About

Where business meets innovation and technology drives transformation. Engineering Evolved is the podcast for leaders navigating the forgotten ground between startup chaos and enterprise bureaucracy. If you're building and scaling teams at organizations in the middle — where startup rules no longer apply and enterprise playbooks are far too large — this show is for you. Hosted by Tom Barber, each episode explores the real challenges facing today's engineering leaders: scaling systems without breaking them, building high-performing teams, aligning engineering strategy with business goals, and making technical decisions that drive measurable impact. Whether you're a Director of Engineering, VP of Technology, CTO, or an IC engineer stepping into leadership, you'll find practical insights drawn from real-world experience — not theoretical frameworks that only work on whiteboards. Topics include: Scaling engineering teams and systems for growth Building effective engineering culture Bridging the gap between technical and business strategy Leadership tactics that actually work in the messy middle Making architectural decisions with limited resources Navigating organizational complexity Engineering Evolved — guiding today's leaders through the evolution of engineering. New episodes drop weekly. Subscribe now and join the conversation about what it really takes to lead engineering in the modern era.

Information

  • Creator
    Tom Barber
  • Years Active
    2025 - 2026
  • Episodes
    16
  • Rating
    Clean
  • Copyright
    © 2025 Spicule LTD
  • Show Website
    Engineering Evolved