I — Frame the Work · Chapter 01

All fifteen chapters
  1. The New Engineering Paradigm
  2. Introducing the Engineering Challenge
  3. Planning Under Uncertainty
  4. Engineering Knowledge as Code
  5. Learning Through Models and Prototypes
  6. Engineering Data: From Measurements to Decisions
  7. Spec-Driven Development Without Waterfall
  8. Directing AI Engineering Agents
  9. Engineering in Small, Reviewable Increments
  10. From Models to an Integrated Product
  11. Verification, Validation and Engineering Evidence
  12. Governance and Engineering Authority
  13. Continuously Integrated Engineering
  14. Managing Engineering Knowledge at Scale
  15. Choosing the Next Engineering Capability

The New Engineering Paradigm

Why engineering is changing—and what leaders and teams must change with it.

Engineering organizations face a widening gap between how quickly products need to evolve and how slowly many engineering decisions move through fragmented disciplines, documents, tests, approvals and delivery processes. Software and artificial intelligence (AI) offer new capabilities, but neither removes the responsibility to develop safe, useful and trustworthy systems.

The opportunity is broader than automating old tasks: engineer the product and the capability to improve it, together. This chapter sets out the whole picture. The next chapter introduces a fictional four-way intersection used to explore the practical implications throughout the course.

Expectations are changing

Customers increasingly expect products to gain capabilities, respond to feedback and remain useful after delivery. Competitive pressure raises expectations for shorter development cycles, higher quality, more frequent improvements and faster adaptation to new needs. These pressures affect software-intensive systems, electronics, mechanical products and the services surrounding them.

They create a demanding combination: develop faster, release more often where feasible, and increase confidence in what is released. Faster output alone is not a solution. A team that produces more changes but cannot integrate, test or authorize them has merely moved work into a queue elsewhere.

Release frequency also differs by product. A web service may deploy repeatedly; embedded software may require controlled integration and qualification; electronics and physical designs involve supplier, manufacturing and test constraints. The objective is not one universal release rhythm. It is to shorten the time between a relevant question, reliable feedback, an informed decision and a useful product improvement.

Software-inspired engineering moves beyond software

Software development has pioneered practices that other disciplines can adapt: smaller increments, explicit configurations, automated checks, continuous integration, versioned information, simulation and feedback from operation. Their contribution is not that an electrical or mechanical product becomes software. It is that more of the engineering work can become connected, reviewable and progressively testable.

A model of a physical function can be executed before hardware is ready. An interface contract can be checked when either side changes. An engineering decision can retain its rationale and applicable evidence. Automated checks can detect regressions early, while system-level validation still determines whether the complete product meets its intended use.

For multidisciplinary systems, the challenge is to connect these practices without assuming that every discipline has the same cycle time. Early model learning can prevent expensive physical changes; physical experiments can reveal assumptions the model cannot represent.

AI expands what engineering teams can do

AI assistance can help teams explore alternatives, work with large collections of engineering information, draft and review technical artifacts, write software, prepare experiments and interpret results. Tool-using AI agents may also carry out bounded tasks: propose a change, invoke tools, inspect feedback and revise the work before handing it back for review.

These capabilities matter most when the environment provides meaningful, sufficiently independent checks. An agent iterating against weak or self-modified acceptance criteria can produce a convincing-looking but invalid result. Engineering judgment is still needed to set objectives, protect constraints, decide what evidence is credible and authorize consequential changes.

AI used to develop a product is distinct from AI built into that product. A team may use agents to improve engineering workflows without deploying AI in the delivered system. Conversely, a product may use predictive or adaptive AI that requires its own safety, performance and validation work.

AI is therefore a major accelerator and potentially an enabler of new ways of working—but it is not the original reason engineering needs to evolve.

Two systems must evolve together

Every engineering organization is developing two related systems.

The product system includes software, electronics, physical components, interfaces, operators and the operating environment. It is judged by what it can actually do, under the conditions that matter.

The engineering system includes people, methods, engineering knowledge, executable models, development environments, automated tests, integration equipment, decision processes, supply-chain relationships and AI-enabled workflows. It is judged by how well it helps the organization make sound product decisions and deliver improvements.

“We build the machine that builds the machine.” This is a reminder that engineering capability itself requires intentional design, investment, operation and improvement. It is not an argument for building a large new tool platform before solving a product problem.

The two systems form a feedback relationship. A difficult product question may reveal the need for a new simulation or test fixture. A better engineering capability may make previously expensive options practical to investigate. Improvements to the engineering system should be justified by the product decisions and delivery outcomes they enable.

From document-driven handoffs to executable feedback

Documents and reviews remain useful; the problem arises when engineering knowledge is disconnected from the models, tests and decisions that give it meaning.

In this lab, executable engineering describes an approach in which suitable models, analyses, checks and workflow steps can be run, evaluated and improved. A requirements definition may connect to a model, an experiment, a verified interface and evidence of system behavior. That does not mean every engineering activity becomes executable. Stakeholder negotiation, model validity, physical integration, safety judgment and release authority still require suitable human and real-world processes.

Two connected feedback loops are especially important:

  • Fast executable feedback: make a bounded change, run a model or test, inspect a failure and refine the work. Automation and agents can accelerate this loop when its checks are dependable.
  • Whole-product feedback: ask whether the model, checks and change are appropriate for the actual intended use. Bring in physical evidence, integration results, operational constraints and authorized decisions.

A passing test is evidence about a stated check under specific conditions. It is not automatically evidence that the product is fit for use.

What this means for engineering leadership

The transformation changes the questions leaders should ask. Beyond measuring tasks completed or documents produced, they should examine what the teams can now demonstrate, which major uncertainties have been resolved, how quality is established and how often useful improvements can be delivered responsibly.

That means investing selectively in shared engineering information, simulation and test capability, integration practices, multidisciplinary interfaces and the skills to direct and evaluate AI-supported work. It also means allowing exploration where the design is uncertain and making stronger commitments when the evidence supports them.

The goal is neither a tool collection nor automation for its own sake. It is a better engineering system that can learn faster, build with greater confidence and improve products more continuously.

From the paradigm to a working example

The rest of the lab turns this broad argument into concrete engineering choices. We will work with a fictional four-way intersection, starting with uncertain needs rather than an assumed solution. We will follow how planning, engineering knowledge, models, data, specifications, agents, integration, evidence and release decisions build on one another.

Chapter 2, Introducing the Engineering Challenge, defines that shared example and its boundaries. The subsequent chapters develop the practices in progressively greater detail.

Engineering takeaway: Market expectations create pressure for speed, release frequency and quality. Software-inspired ways of working provide a foundation, and AI expands the opportunities. The enduring change is to develop the product and the engineering capability that improves it as two connected systems.

Published after initial author review. This fictional teaching case is not physical validation. Interactive V3 tools remain in development. Chapter source