The Book
Inside the Book: Structure, Principles, and Publication Details
Whom This Book is For
The book targets the four groups who can make an impact on how we develop products
For Practitioners
For Teachers and Students
For Innovation Leaders
For Tool Vendors
What is the book about, and why does it matter now?
Product development is undergoing a major shift, especially for systems that integrate mechanical, electrical, and software components. Practices that have transformed software (like rapid iteration and continuous integration) can also accelerate physical product development. Companies like BYD launch new vehicles in 18 months, while industry standard is four years; SpaceX iterates engine design every two days, while others take months.
This book presents structured, reusable solutions to recurring systems engineering challenges, focusing on tightly integrated development artifacts through systems and design modeling. For instance, model parameters can drive simulations, enabling near-instant requirements verification.
Instead of prescribing a full methodology, the book offers modular solutions that enhance existing frameworks like SAFe or SYSMOD. It aims to boost speed and quality without disrupting existing workflows. While the need for organizational change is acknowledged, it’s not the book’s focus—excellent resources already exist in that area.
This book introduces “Lean Systems Engineering” as a practical, tool-neutral approach to developing complex, multidisciplinary products faster than traditionally possible.
What Makes This Book Unique?
The potential for continuous development for physical systems remains largely untapped. While many frameworks and methods exist, it’s often unclear how they integrate into a practical, end-to-end toolchain. This book addresses that gap by outlining common use cases (e.g., test case generation from system models), implementation strategies (e.g., OSLC-based scripting), and assessments of tools like Flow Engineering using realistic scenarios.
A recurring case study—a moderately complex IoT device—demonstrates how these concepts apply across mechanical, electrical, and software domains. Introduced early, it grounds the book with practical examples throughout.
Few books tackle this space today. Influential titles like The Principles of Product Development Flow and Agile Systems Engineering are over a decade old and don’t reflect recent advances like AI-driven requirements reuse or SysML v2. Some of the newer books, like The Agile Model-Based Systems Engineering Cookbook tend to overemphasize MBSE over agile, limiting their usefulness to industries like aerospace, defense or automotive. This book fills that gap with real-world patterns using off-the-shelf solutions that are applicable to projects of all sizes.
It also draws on approaches from Joe Justice (e.g., SpaceX’s rapid engine redesigns), including automation, simulation, and strict interface contracts. His practices will be featured, and he will be consulted during development.
The book can be read front to back for a complete picture or used as a reference guide offering modular, actionable solutions.
Publication Timeline
The manuscript will be completed by Q1 2026 with publication scheduled mid of 2027.
Why so long? As an academic publisher, MIT Press conducts thorough due diligence with multiple levels of review, copy editing and typesetting. This takes time, but ensures that the resulting book has the highest quality and stands the test of time. (More information)
*Of course you can unsubscribe anytime (Privacy Policy).
Table of Contents
This is the current books structure (as of February 2026)
Chapter 1: Introduction
Frames the problem that product companies are facing, describes the structure of the book and introduces the case study.
Part I: Why and How Product Velocity Works (Proof)
This part explains why physical product development must accelerate and how lessons from systems engineering and modern software practices reveal a path forward. It shows that competitive pressure is rising fast and that proven high-velocity approaches already exist.
Chapter 2: The Product Velocity Imperative
Understand why acceleration is unavoidable by examining external pressures like cost, regulation, and customer expectations alongside internal pressures such as complexity and change. Learn how software solved a similar crisis and what principles transfer to physical systems.
Chapter 3: What Works Today, What Holds Us Back, and What’s Possible
We rely on safety-proven practices for physical products, but they are slow and brittle under rising complexity and innovation. The task is to preserve what ensures safety and reliability while replacing what blocks speed, across both practices and organizational culture. This transformation is achievable: newer companies like SpaceX and BYD were built for it, and established players such as General Electric and ZF Friedrichshafen have shown it can be done with deliberate cultural change.
Chapter 4: The Velocity Loop
We have established that achieving high product velocity is both possible and practical. The remaining challenge is not whether it can be done, but how to get there in a systematic and repeatable way. The Velocity Loop provides this structure. Inspired by the DevOps Loop, it adapts the core idea of continuous feedback and integration to the realities of cyber-physical product development.
Chapter 5: Cadence and Synchronization
Cadence provides temporal structure that lets complex product organizations move fast without losing coherence. When practices and commitments evolve at different speeds, continuous synchronization creates drag, while unchecked autonomy leads to fragmentation. This chapter introduces cadence as a deliberate coordination mechanism that defines when alignment occurs, not how work is done. It outlines four core questions, explains nested cadences across time horizons, and clarifies what cadence is not. Treating time as a first-class design concern allows learning to propagate through the Velocity Loop while preserving local autonomy.
Part II: Define & Align (Value Thinking)
This part centers on stakeholder value as the core driver of product development. It introduces value flow that starts in the business, continuous alignment, and measurable objectives, showing how early clarity and constant learning keep development focused, synchronized, and economically sound.
Chapter 6: Create a Culture That Enables Value Flow
Build an entrepreneurial mindset supported by empowerment, psychological safety, and cross-functional collaboration. Remove organizational barriers that slow decision-making or impede value creation.
Chapter 7: Define Value and Measurable Success Criteria
Create a digital thread of value that connects stakeholder needs to engineering activities. Use measurable success criteria to keep work aligned and prevent waste caused by cross-domain disconnects.
Chapter 8: Continuously Discover and Align Stakeholder Needs
Identify stakeholders, capture their evolving needs, and refine engineering inputs through continuous feedback. Maintain alignment by updating assumptions as new insights emerge.
Chapter 9: Map and Improve Value Streams
Visualize how value flows from concept to customer to detect bottlenecks and delays. Use this transparency to guide ongoing improvements.
Chapter 10: Capture, Share, and Institutionalize Knowledge
Turn lessons learned into reusable assets, patterns, and processes, ensuring teams accelerate over time rather than relearning the same insights.
Part III: Structure & Scale (Architect for Flow)
This part describes how to architect both the product and the development environment for continuous flow. It covers modular systems architecture, interface clarity, platform thinking, effective modeling, and managing cross-cutting concerns through a connected digital thread.
Chapter 11: Product Architecture
Use black-boxing and modular system structures to manage complexity and support scalable development, drawing inspiration from proven software practices.
Chapter 12: Interface Management
Ensure predictable integration by defining, managing, and maintaining interfaces across products and platforms. Stable interfaces keep teams decoupled and productive.
Chapter 13: Platform Thinking
Shift from project-centric engineering to product-centric and platform-centric architecture. Build reusable foundations that support multiple product variants efficiently.
Chapter 14: System Models and the Digital Thread
System models make architectural intent explicit. The digital thread links these models across tools and lifecycle stages, preserving traceability and decision context so that change can propagate predictably without breaking flow.
Chapter 15: Cross-Cutting Concerns
Cross-cutting architectural constraints that influence decomposition and interfaces. That means things like: Safety architecture patterns, Security boundaries, Regulatory partitioning, Data ownership \& sovereignty, Observability as architectural property, Variant management principles, Lifecycle layering decisions, Governance structures for architecture.
Part IV: Build & Validate (Shift Left)
This part shows how continuous integration, early validation, and coordinated cross-disciplinary collaboration reduce risk and accelerate development. It connects simulation, automation, AI, and digital twins into a coherent shift-left strategy.
Chapter 16: Cross-Disciplinary Collaboration
Align mechanical, electrical, software, and systems teams through shared language, synchronized cadence, and interface clarity to ensure effective integration.
Chapter 17: Continuous Integration & Verification
Integrate artifacts across disciplines, augment them with simulation and testing, and build the foundation for model-based V&V and digital twins.
Chapter 18: Towards Industrial DevOps
Adopt continuous integration and delivery practices for physical products, creating a unified development and deployment pipeline.
Chapter 19: Digital Twin
Use high-fidelity models linked to real data for continuous validation, insight into integration issues, and feedback to the digital thread.
Part V: Operate & Evolve (Accelerate)
This part explains how long-term success depends on operating products as evolving platforms. Continuous learning, coordinated hardware-software evolution, and organizational adaptation ensure products remain competitive and teams sustain high velocity.
Chapter 20: Operational Lifecycle & Feedback Loops
Manage the full operational lifecycle and use feedback loops to refine products, architectures, and processes over time.
Chapter 21: Co-Evolving Hardware and Software
Coordinate hardware and software evolution in a platform ecosystem, ensuring both progress together without friction or regression.
Chapter 22: Evolving the Organization
Adapt structures, roles, and culture as products and platforms mature. Close the book by showing how organizations must grow alongside technology.