StoryC

The CTO Augmentation Line™

Engineering is the one place we have to get this right.

It is the function where AI adoption is furthest along, where the evidence is clearest, and where everyone else in the business is watching to see whether it works. It is also the function where the value is most visibly stuck, and not for the reason most boards assume.

Code is no longer the bottleneck, the human-speed steps around it are. Anthropic, The AI-Native SDLC Playbook

The model is not what is holding you up. What is holding you up is a lifecycle built for a world where writing the code was the expensive part: approval queues sized for weekly output, review capacity sized for what a person could type, and security checkpoints that assume a human is waiting at both ends. Those policies were correct when they were written. They are now the constraint.

The Line, drawn across the lifecycle

Every engineering function has a line between what a bounded agent runs and what a named human signs. It is not one line, it sits in a different place at each of the six stages, and the honest answer differs at each.

01

Plan

Intent captured in the originator's own words, in version control, before anyone opens a ticket. If intent lives only in a meeting, everyone downstream is guessing, agents included.

The agent runsDrafting the problem statement, surfacing prior art, spotting the intents that contradict each other.
A human signsWhat the business actually wants, what it is worth, and whether it should be built at all.
02

Design

Requirements and design collapse into one working session, bounded by the organisation's own standards, which means those standards have to exist in a form a machine can read.

The agent runsOptions against the constraints, the trade-offs written down, the decision recorded where the next person will find it.
A human signsThe architectural choice, and anything that commits the organisation for years rather than weeks.
03

Build

The plan is reviewed before the code is written. That single inversion, approve the approach, not just the diff, is what makes the volume reviewable at all.

The agent runsImplementation against an approved plan, in an isolated workspace, several streams at once.
A human signsThe plan, before it runs. And the moment the work turns out to need a different plan.
04

Test

Work verifies itself before a person is asked to look. Your test suite stops being a safety net and becomes the thing that makes delegation defensible.

The agent runsWriting and running the checks, closing its own loop, arriving with evidence rather than a claim.
A human signsWhat "good" means, and whether the tests test the thing that actually matters.
05

Deploy

Governance enforced as code rather than as a paragraph in a policy document. A gate that depends on someone remembering it is not a control, it is a hope with a process diagram.

The agent runsThe mechanical review passes, the control checks, the release mechanics inside declared permissions.
A human signsProduction, at the value and risk thresholds you set, and nothing below them.
06

Maintain

Monitoring that does not merely alert but writes the next problem statement, which closes the loop back to Plan and makes the whole thing a cycle rather than a pipeline.

The agent runsDetecting the breach, drafting the fix intent, turning each incident into a permanent check.
A human signsWhether it is a defect, a design decision or a change of mind, and what the organisation learns from it.

Where the value is actually stalling

In most functions it is none of the six stages. It is the policy layer wrapped around them, written for output at human speed and never revisited.

Approval cadence

Weekly or monthly gates become intractable when the build finishes in an afternoon. The queue, not the work, sets the delivery date.

Review capacity

Reviewers sized for what people could type cannot absorb what agents produce. Quality does not fall, throughput does, and then quality follows.

Estimation ritual

Ceremonies that exist to forecast human effort keep running after the effort has moved. They now cost more than the work they estimate.

Security checkpoints

Correctly non-negotiable, wrongly implemented as a queue. The control is right; its position in the flow is what is expensive.

Knowledge in heads

Conventions no one wrote down cap how consistent anything can be, human or machine. This is the cheapest one to fix and the most often skipped.

Tooling policy

Rules written for a previous generation of tools, enforced by people who cannot say what today's risk actually is.

The failure to avoid is symmetrical. Removing a gate because it is slow, without rebuilding the control it carried, is not modernisation, it is deregulation with extra steps. Every gate in that list was written for a real risk. The work is to rebuild each control at the speed the work now moves, not to delete it and hope.

What we do about it

Four moves, in this order. The order is the method.

1

Score the function

Thirty questions across the six stages plus the policy layer. You get your band, your gaps and the shape of a 90-day sequence on the spot, free, and yours whether or not we ever speak.

2

Find the drag

Measure where the time actually goes between an idea and production. In most functions the answer surprises the people who own the process, which is the point of measuring rather than asking.

3

Rebuild one control

Take the single heaviest gate. Establish what risk it was written for, then rebuild that control so it runs at delivery speed. One, done properly, is worth more than a programme.

4

Draw the line

Agree stage by stage what an agent runs and what a named human signs, written down, enforced where it can be, and reviewed on a date that is in the diary.

How you will know it is working

Not lines of code, and not seats deployed. The measures that matter are about elapsed time and what survives contact with production.

  • Idea to written intent. How long before a problem is stated well enough to act on.
  • Time between artefacts. Where the work sits waiting, and for whom.
  • First-pass merge share. How much gets through without a second round.
  • Intent survival. How much of what was accepted still stands after the build.
  • Rework after build starts. The cost of settling requirements too late.
  • Escaped defects. The one that keeps everyone honest about the others.
Start the assessment →

Where this sits

The CTO line is one altitude of the same method. The others are already published, and the pattern is deliberately identical, score the function, find the drag, rebuild one control, draw the line.

The CFO line

Finance, where there is no tolerance for a hallucinated number.

The CPO line

Procurement, where the evidence has to survive a contested process.

Internal audit

Assurance, where the standard is what you can show, not what you did.

The injection demonstration

What happens when an agent takes its authorisation from a message. Worth ten minutes of any engineering leader's time.