Concept to Cloud
Engineering leadership without the bullsh*t. Deep dives into the real challenges facing mid-size engineering teams: modernisation, architecture decisions, team structure, and the technical debt nobody wants to talk about. 20 to 40 minutes, weekly.
18 episodes
Featured episodes
Start here if you're new to Concept to Cloud.
Tack On, or Rebuild?
The tack-on-or-rebuild call is the most consequential judgment in product, and the customer can never make it for you. They reason from the surface (a feature request in the vocabulary of the product they already have); the answer lives in the structure underneath.
Your Users Don't Care If It's AI - They Just Want Results
Users grade you on whether the product works the same way twice, not on the impressiveness of the model. A cheaper tuned model that returns consistent answers beats an expensive frontier model that drifts.
The Trio Model: Breaking Down Business-IT Walls for Better Engineering Collaboration
Business-IT alignment problems are structural, not staffing problems. Hiring more managers, adding meetings, or buying tools makes them worse, not better.
Why Your Team Rituals Are Optimized for the Wrong Thing
Most mid-sized companies have too many rituals, not too few. Sprint planning, standups, roadmap reviews and stakeholder syncs are perfunctory: they answer 'what' and 'when' but never 'why does this matter to you' or 'what are we not talking about'.
You Don't Need Kubernetes: Right-Sizing Platform Engineering for Mid-Size Companies
The NASA JPL story is the whole argument. A four-person team ran Kubernetes with service mesh and custom operators. When funding shifted and half the team was reassigned, deployments went from 5 minutes to an afternoon. Ripping it out and running Docker on VMs with a bash script cut onboarding from two weeks to twenty minutes.
The Architecture Decision Framework - When You Actually Need Microservices (Spoiler: Probably Not Yet)
A 12-person team running 47 services is a disaster waiting to happen, and the word 'microservices' is partly to blame. Chasing 'micro' encourages bad decisions like putting an address CRUD behind its own database and deployment pipeline.
Escaping Technical Purgatory
The 'missing middle' (200-1000 employees, 20-150 engineers) is not a soft spot in your journey. It is a distinct engineering problem: too big for startup osmosis, too small for enterprise frameworks. Copying either playbook is the fastest way to make it worse.
Topics covered
All episodes
Tack On, or Rebuild?
Tom rebuilt Saiku - an open-source analytics platform he first shipped years ago - and got 97 new installs. He also found roughly 180 people still running the old one.
From Napkins to Agents: How AI Rewired Product Design
In this episode of Engineering Evolved, Tom sits down with Amelia Prasad, Director of Product at Concept to Cloud, to trace how AI has reshaped the day-to-day of UX and product design. Amelia — who came to product from astrophysics and climate science ...
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.
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 falli...
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.
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 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 Yo...
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 imp...
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 ...
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...
DevOps for the Skeptical VP: Building Your Business Case in 30 Minutes
Summary In this conversation, Tom Barber discusses the challenges of managing feature requests and the importance of strategic deployment to enhance team efficiency. He emphasizes the need to prioritize time-consuming tasks to free up valuable hours fo...
Cloud Migration Without the Chaos - A Product Manager's Approach
Summary In this episode of Engineering Evolved, Tom Barber discusses the critical aspects of cloud migration, emphasizing that many migrations fail due to poor planning and execution. He contrasts successful migrations, like Netflix's, with failures li...
The Three Types of Technical Debt Your Finance Team Actually Cares About
SummaryIn this conversation, Tom Barber discusses the significant impact of technical debt on American companies, highlighting that it costs them $1. 5 trillion annually.
The Architecture Decision Framework - When You Actually Need Microservices (Spoiler: Probably Not Yet)
Summary Most midsize companies are making terrible architecture decisions because they're copying Netflix instead of solving their actual problems. This episode cuts through the hype and gives you a practical framework for deciding when you need micros...
Cross-Functional Teams vs. Feature Factories: What's Actually Different?
Episode Summary Are your "cross-functional" teams actually just a feature factory in disguise? In this solo deep-dive, I break down the real differences between truly empowered teams and organizations that just reorganized the boxes on an org chart.
The Product Thinking Framework
Most engineering leaders would fail miserably as product managers. They'd get fired for shipping features nobody wants, ignoring user feedback, and measuring the wrong things.
How I Accidentally Became A Modernization Director
Nobody wakes up wanting to be a modernization director. In this deeply personal episode, I share my journey from writing simple code at NASA JPL to leading complex system transformations at a fintech startup—and the expensive failures that taught me ev...
Escaping Technical Purgatory
Why Mid-Sized Companies Are Stuck (And How to Break Free) You've achieved product-market fit. You're generating real revenue.