The 8 feedback loops of AI delivery and the 3 teams forget

In this lesson you'll learn:

• what the eight loops are, where each opens and closes, and who owns it;
• the precise difference between a loop that is closed, open and absent;
• how to close the three loops that nobody is waiting on.

Sound familiar?#

• The bill doubled, a budget increase was approved, and the same thing happened next quarter.
• The postmortem produced eleven action items in a tracker, and the incident recurred with a different name.
• Numbers reach the steering committee only when the steering committee asks for them.

Each is a loop that was never closed, handled as a conversation instead of as a change to the design.

What are the eight loops?#

The four phases of the agentic PDLC are a line. The loops are what make the line a ring: each one carries something learned in a later phase back to the artefact it should change.

Five close forwards or inside a phase, and they look after themselves: somebody downstream is waiting and will chase. Three have nobody waiting. Cost closes backwards into design, incident closes backwards into framing, and governance spans the whole line and belongs to no delivery role.

How to run the loops, step by step#

Step 1 · Agree what "closed" means#

A loop is closed when something learned at the far end has changed an artefact at the near end, and you can point at the change: not a discussion, not a ticket, not a lesson learned.

"Informal" is not one of the three. A loop that closes when somebody happens to remember is absent with better manners.

Step 2 · Name one person for each loop#

For each of the eight, write a name: a person, not a team. The five forward loops usually already have one. For the three loops nobody waits for, the honest first answer is often that nobody owns them, and "absent" is the right word for that.

Step 3 · Close the cost loop into the design#

A bill that left its estimate is a design question, not a finance question. At SkyWays, the fictional airline this manual follows, the day-75 bill was 4.4 times its estimate on flat traffic. Handled as a budget question, it recurs next quarter with a different multiple. Handled as a loop, the per-call log traced it to four habits, and the model-tier decision record got a second version: classification moved to the cheap tier, judgement stayed on the capable one, and cost per case became a monitored number. It closes when a decision record has a new version with a diff.

Step 4 · Close the incident loop into framing#

One question runs the whole incident loop: which enforced control, if it had been present, would have made this impossible? On day 82 SkyWays' agent issued a $2,000 refund that was not owed. The postmortem found five layers of defence claimed and none enforced; two lived only in the prompt. What left the room was a typed $400 cap, a confirmation token, refunds dropped one autonomy level until a fourteen-day shadow run re-earned it, and six new golden cases. It closes when a brief for the next P0 exists, with an owner.

Step 5 · Give governance to the sponsor#

Governance is the only loop the delivery roles do not own: a minimum set of artefacts at each hand-off, hard gates that halt and soft gates that do not, one accountable name per artefact, and two numbers reported together every cycle (the saving and the spend). It is the loop most often absent, because nobody downstream is waiting for it.

Where you'll use it#

• In a quarterly health check: mark each of the eight closed, open or absent, with the evidence.
• After every bill anomaly and every incident: ask which artefact at the near end should change.
• When onboarding a sponsor: the governance loop is the part of the lifecycle that is theirs.

Why it matters#

A programme that runs the phases but not the loops ships once and then drifts. The two loops that close backwards are what turn a project into a practice: the first time a bill changes a design, or an incident changes a frame, the team stops paying for the same lesson twice.

Key takeaways#

1. Eight loops, eight owners: each opens in one phase and closes when evidence changes an artefact in another.
2. Closed means a diff, open means an owner and a date, absent means you cannot name a person.
3. Cost, incident and governance have nobody waiting: close them on purpose, or they do not close.

FAQ#

What is a feedback loop in software delivery?#

A path by which something learned later in delivery changes something decided earlier. In the agentic PDLC a loop only counts as closed when the earlier artefact (a spec, a decision record, a brief) has actually been changed by the evidence, and the change can be shown.

Why do the backward loops matter most?#

Because nobody is waiting for them. A forward loop closes because the next person cannot start without it; a cost anomaly or an incident has no downstream customer, so it is resolved as a budget or a ticket unless someone owns the return path. Those are the loops that stop a failure from recurring.

Who owns the incident loop?#

Every role. The postmortem asks which enforced control was missing, and the answer usually belongs to several roles at once: the architect's authority budget, the engineer's tool signature, QA's injection suite. The product manager then owns the brief it produces for the next P0.

How is this different from the Lean Startup build-measure-learn loop?#

Build-measure-learn is one loop about whether a product meets a market need. The eight loops are narrower and more operational: each has one owner, a phase where it opens, a phase where it closes, and a test (the diff) for whether it did.

Apply it in your role#

Across the enterprise. Across a portfolio, the backward loops need a central owner, usually the platform or governance lead, because no product team is waiting at the far end of them.

The ten-minute workflow. Find the loops nobody is closing:

Here is our last quarter (incidents, bills, drift alerts and decisions): <paste>. For each of the
eight loops (requirements, spec, decision, delivery, trust, cost, incident, governance), say whether
it closed (which artefact changed?), is open with an owner, or is open with nobody. List the ones
with nobody first.

Sources and credits#