liveBook · Manning

Chapter 3: AI as a partner and problem

What you will learn in chapter 3 of Build High Value Software Systems

The chapter introduction shows how AI can speed up useful work or quietly introduce unchosen business rules, and frames Lean thinking as a way to distinguish the two.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The chapter introduction shows how AI can speed up useful work or quietly introduce unchosen business rules, and frames Lean thinking as a way to distinguish the two.

Key terms: business logic, AI output, API contract, value, waste, inventory, assumptions, Lean lenses, intent, scaffolding

3.1 Keeping the human above the loop

Introduces why treating AI as a development peer can misplace the human in the workflow, and defines the value stream used to examine that concern.

Key terms: teammates, pair programmers, junior developers, execution flow, above the loop, value stream, intent to outcome, adds value

3.1.1 The problem with being in the loop

The section shows how treating the human as a step in an AI-assisted development loop can hide whether the work creates value or merely produces output.

Key terms: executor, inside the loop, value, inventory, waste, AI as pair programmer, better outcomes, more output, smallest viable step

3.1.2 Positioning the human above the loop

The section explains how a developer can stay above AI-driven execution by setting intent and boundaries, judging outputs, and watching the flow of work.

Key terms: above the loop, in the loop, flow, inventory, constraints, boundaries, intent, handler skeleton, temporary scaffolding

3.1.3 What this means in practice

This section explains why humans must retain judgment over AI-assisted development while AI executes bounded tasks, and how failing to make intent explicit creates downstream waste.

Key terms: above the loop, within the loop, value, correctness, sufficiency, intent, decision points, motion, waiting, over-processing

3.1.4 From collaborator to power tool

This section reframes AI as a power tool whose Lean benefits depend on a human retaining control and watching its effects on value, flow, and waste.

Key terms: power tool, human above the loop, value stream, flow, waste, overproduction

3.2 How AI helps you stay lean

The section explains that AI supports Lean development when it reduces effort on necessary, non-differentiating work rather than merely increasing coding speed.

Key terms: Lean, value stream, human judgment, boilerplate code, mechanical refactors

3.2.1 The API service example

The API service example shows how a team uses AI to remove setup and review friction while keeping intent, design, and implementation decisions with developers.

Key terms: intent, API contract, success criteria, Lean lens, mechanical delay, decision to feedback, scaffolding from contracts, handler skeleton, 501 (Not Implemented), TODOs

3.2.2 The Lean principle at work

This section explains how AI supports Lean development by reducing effort and speeding feedback without taking over human judgment or creating costly long-term commitments.

Key terms: human judgment, cognitive overhead, responsibility, high commitment, low commitment, generated code, generated artifacts, feedback loops, early feedback, predictable

3.3 Where AI creates waste

The section explains how a prompt that names an activity but leaves its outcome unconstrained can turn AI-generated code into waste.

Key terms: vague prompt, constrain the outcome, inventory, value stream

3.3.1 The unconstrained prompt

An underspecified, one-shot AI prompt for an API endpoint can produce polished code that includes unrequested rules and assumptions.

Key terms: unconstrained prompt, invented validation, business rules, assumptions

3.3.2 Breaking down the waste

This section shows how plausible AI-generated code creates multiple forms of waste and why reviews miss that waste when the code’s connection to the original intent is invisible.

Key terms: overproduction, inventory, defects, abstraction, indirection, extra processing, value stream context, API contract, lineage to decisions, skills underutilization

3.4 Establishing your AI standard work

The section explains how shared standard work makes AI-assisted development predictable enough to spot deviations and improve.

Key terms: standard work, stable baseline, deviations, standard work for AI, variability, human judgment, constraints

3.4.1 What the API service team established

The API service team replaces inconsistent individual AI practices with a shared prompt baseline and judges it by whether it reduces downstream work.

Key terms: shared AI persona, architectural values and constraints, development-practice needs, downstream work, stable baseline

3.4.2 Making AI boundaries explicit

The section shows how explicit, accessible AI standards keep human responsibility clear while allowing teams to improve their practices as AI changes.

Key terms: standard work, human-authored statement of intent, bounded, reversibility, scaffolding, final behavior, semantics, contracts, existing tests, review

3.4.3 Standard work as flow protection

AI standard work protects delivery flow by filtering out avoidable variability before AI-generated changes reach review and integration.

Key terms: AI standard work, flow protection, upstream filter, review and integration pipeline, form validation, foobar, standards.md, downstream friction

3.5 Exercise: Compare handwritten vs AI-generated code

The exercise compares handwritten and AI-assisted versions of the same small change to reveal how AI affects waste, effort, and where understanding happens.

Key terms: baseline, AI coding assistant, Lean criteria, overproduction, inventory, defects, motion, extra processing, standard work, constraints

3.6 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 2: Value and waste in software Chapter 4: Writing Lean code →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.