Chapter 01
The New Engineering Paradigm
Explain changing expectations, software-inspired workflows, AI, and two co-evolving systems
Read chapter →Engineering transformation · Software-driven practices · AI
Markets expect shorter development cycles, more frequent improvements and higher quality. Software-inspired practices are spreading across electronics, physical products and systems engineering; AI introduces new ways to explore, implement and evaluate changes. This lab examines how we can make engineering faster and more dependable without overlooking whole-product evidence.
We build the machine that builds the machine: improve the engineering environment alongside the product.
Product system
Software · electronics
Physical design · AI
Understand use
Model
and experiment
Integrate
and validate
New product ambitions
change the engineering work
Decide what to test
and what to build next.
New engineering capabilities
expand what we can try
Engineering
environment
People · models
Tools · AI agents
Develop methods and models
Work with
AI agents
Automate
and evaluate
A fictional city considers improving a four-way intersection. First we establish stakeholders, system boundaries and uncertainty; later we use a bounded fixed-phase model to test one specific question. Read the introduction to the example.
Define + model
Clarify the needs of drivers, pedestrians, operators and maintainers before selecting a preferred solution or model.
Execute + evaluate
Use controlled scenarios and tests to explore alternatives. AI agents may help refine bounded changes where independent automated checks provide meaningful feedback.
The example is fictional. Fast automated feedback supports learning and agentic iteration; whole-product evidence determines which results are actually relevant to integration and release.
01 / Modelling and exploration
Use software models, simulations and physical prototypes to examine specific engineering questions. Deterministic calculations have predictable results for defined inputs; experiments reveal what changes when conditions or designs change.
02 / Teams and workflows
Design automated behavioral and integration checks that tell agents what failed and why. Let them refine bounded changes, while preserving independent criteria and making demonstrated behavior—not generated output—the measure of progress.
03 / Release and feedback
Automated tests support fast inner loops. Product validity, physical interfaces, operational conditions and release authority form a broader loop with different evidence and cadences. A green test suite cannot answer every product question.
Begin with the changing engineering paradigm, then follow one fictional traffic intersection from uncertain intent to an integrated product and the engineering capabilities needed to sustain it.
All fifteen chapters are available below following initial author review. The examples are fictional teaching cases; interactive V3 graph and model tools remain in development. Earlier lessons remain available separately.
Chapter 01
Explain changing expectations, software-inspired workflows, AI, and two co-evolving systems
Read chapter →Chapter 02
Understand stakeholders, system boundaries, and the fictional case
Read chapter →Chapter 03
Select a meaningful investigation and decide what is ready to commit
Read chapter →Chapter 04
Explain controlled engineering information, typed relationships and change impact
Read chapter →Chapter 05
Select a model, define assumptions and interpret a bounded experiment
Read chapter →Chapter 06
Curate, annotate, inspect and reuse engineering observations
Read chapter →Chapter 07
Define a bounded next increment while leaving other uncertainties open
Read chapter →Chapter 08
Bound, observe and review delegated engineering work
Read chapter →Chapter 09
Establish useful review boundaries and cross-discipline dependencies
Read chapter →Chapter 10
Bridge model/software work to product interfaces, physical integration and intended use
Read chapter →Chapter 11
Qualify claims against the integrated configuration and intended use
Read chapter →Chapter 12
Identify controls, authority, technical integrity and residual risks
Read chapter →Chapter 13
Design and operate an engineering factory for controlled changes
Read chapter →Chapter 14
Reuse sources, models, tests and working methods with judged applicability
Read chapter →Chapter 15
Synthesize the two-system story into an investment decision
Read chapter →V2 · Chapter 1 · Earlier preview
Start with The New Engineering Paradigm