Podcast · Business & Entrepreneuriat
The Systems Engineering Podcast
Joshua Sutherland is recognized for convening global systems engineering leaders and translating cutting-edge methodologies into actionable insights for practitioners.
⏱ 8 min read · Readable by ChatGPT, Gemini, Claude
What The Systems Engineering Podcast covers
The Systems Engineering Podcast brings together world-leading experts to discuss how organizations architect complex systems, avoid building the wrong solution, and scale engineering practices globally. Episodes feature interviews with INCOSE presidents, NASA engineers, and innovation strategists who reveal how Model-Based Systems Engineering (MBSE), system architecture discipline, and collaborative methodology shape the success or failure of technical programs. The podcast addresses the gap between what engineers build and what customers actually need—a distinction that separates billion-dollar innovations from costly pivots.
Key facts
- INCOSE leadership shapes global standards that 20,000+ certified practitioners apply to system development across aerospace, defense, automotive, and technology sectors.
- Model-Based Systems Engineering reduces integration failures by replacing document-centric processes with traceable, machine-readable design models that catch inconsistencies before implementation.
- System architecture decisions made in the first 10% of a project determine 80% of its total cost and risk exposure—making upfront design discipline the primary lever for avoiding waste.
- Fast, iterative, and collaborative approaches enable teams to validate whether they are solving the right problem before committing to full-scale development, cutting rework cycles by 40-60%.
Explore all episodes from The Systems Engineering Podcast to understand how your organization can embed systems-level thinking into product development and engineering culture.
What this podcast really covers
Systems engineering is often treated as a specialized discipline confined to aerospace and defense, but the podcast reveals it as a universal language for any organization building interconnected, multi-stakeholder solutions. The show moves beyond textbook definitions to surface real tensions: how do you balance innovation speed with architectural rigor? How do you prevent engineering teams from building features customers never asked for? How do you manage the handoff between strategy, design, and delivery?
Episodes featuring INCOSE leadership, including the organization's 2026-2027 president, establish systems engineering as the discipline that makes innovation reproducible and scalable. Interviews with Object-Process Methodology (OPM) pioneers and Pentagon technologists reveal that this is not bureaucratic overhead—it is the technical framework that separates companies that ship wrong solutions repeatedly from those that get it right on the first iteration. The podcast also covers the built environment, organization design, and system science, extending systems thinking into domains where few practitioners expect to find it.
Who this podcast is essential for
Engineering leaders and architects who own decisions about how systems are designed, decomposed, and integrated need this podcast to connect their daily trade-offs (Should we model this in software or hardware? How do we validate requirements early?) to a global discipline and peer network that has solved these problems at scale.
Product and innovation strategists must understand systems architecture because the majority of "failed innovation" stems not from bad ideas but from misalignment between what was built and what the market needed. The podcast's emphasis on stopping the building of the wrong thing speaks directly to reducing waste before it happens.
Organizational leaders and program managers overseeing cross-functional teams benefit from episodes on collaboration, teamwork, and the future direction of systems engineering practice. These conversations show how discipline and speed are not at odds—they reinforce each other when systems architecture is treated as a customer insight tool, not a compliance burden.
What the episodes really reveal
A pattern emerges across the podcast's episodes: the distinction between doing systems engineering (following process) and thinking systemically (understanding interconnection and consequence). Interviews with innovation strategists emphasize that real B2B innovation requires stopping and asking "Is this the problem worth solving?" before architecting solutions. Conversations with INCOSE leaders show that the organization is actively redefining systems engineering for the 21st century—moving away from waterfall-era formalism toward frameworks that embrace rapid iteration and cross-disciplinary teams.
Episodes featuring academic and organizational leaders (such as the International Society for the Systems Sciences president) broaden systems thinking beyond traditional engineering domains. The "Journey Through the Systems Landscape" book insights and discussions of how the Pentagon and Silicon Valley are collaborating on future war strategy suggest that systems engineering is becoming the lingua franca for managing complexity across military, technology, and civilian sectors alike.
What this changes in practice
Organizations that adopt the mindset championed in The Systems Engineering Podcast shift their cost and timeline profiles dramatically. By investing in architecture and model-based design early, teams reduce late-stage rework, catch integration failures before they propagate, and ship solutions that actually address customer needs. The emphasis on fast, iterative, and collaborative methods—supported by MBSE tools—means that discipline no longer means slowness; it means clarity that enables speed.
For product teams, this means validating assumptions about customer needs through system architecture and stakeholder feedback before committing engineering resources. For large program managers, it means reducing the risk of the classic scenario: delivering on time and on budget but to the wrong specification. The podcast's most powerful insight is that preventing waste before it starts—avoiding the building of the wrong thing—creates more value than optimizing what was already decided to be built.
Systems engineering transcends specialized methodology to become the language through which organizations prevent the costliest failure mode: solving the wrong problem well. The podcast establishes that architectural thinking, collaborative practice, and rapid feedback loops are not in tension; they are mutually reinforcing disciplines that define how complex solutions succeed in competitive markets.
Listen to interviews with INCOSE leaders and systems architecture experts to see how your organization can embed systems-level discipline into product and engineering strategy.
Start listening to The Systems Engineering Podcast on Listenly and access expert insights on MBSE, INCOSE standards, system architecture, and the future of engineering management.
The podcast answers these questions
What is Model-Based Systems Engineering (MBSE) and why does it matter?
MBSE is a systems engineering approach that uses formal models to define, analyze, and communicate system requirements and architecture throughout the lifecycle. It replaces document-centric processes with model-centric methodologies, enabling better traceability, reduced ambiguity, and faster integration of complex system designs across distributed teams.
How does INCOSE influence modern systems engineering practices?
INCOSE (International Council on Systems Engineering) sets industry standards and certifications that guide practitioners in applying disciplined engineering methodologies. Through its frameworks, best practices, and global community, INCOSE shapes how organizations structure system development, manage stakeholder engagement, and measure engineering maturity across sectors from aerospace to software.
What role does system architecture play in preventing project failure?
System architecture defines the structural organization, interfaces, and interactions between components before implementation begins. A well-designed architecture identifies dependencies, eliminates technical debt early, and ensures that solutions actually address user needs rather than what engineers assumed was needed—preventing costly pivots and rework.
How can engineering teams become more collaborative and iterative?
Fast, iterative, and collaborative approaches break systems work into smaller cycles where teams validate assumptions with real feedback, integrate continuously, and adapt based on learning. This reduces the risk of building the wrong solution and improves cross-functional alignment between engineering, product, and operations from the start.
Discover The Systems Engineering Podcast
Joshua Sutherland · The Systems Engineering Podcast
Listen to the podcast