The question is not only whether a human remains in the loop. It is whether the system continues to produce humans capable of meaningfully being there.
This is not a fourth Loop pattern and not a ninth HAL domain. It is a cross-cutting
condition of meaningful human involvement. For Human-in-the-Loop, Human-on-the-Loop and
Human-Accountable-for-the-Loop alike, the operating model assumes a capable human. The
method below asks whether that assumption will still be true after the work is redesigned.
It is also not an argument against automation, and not an argument for preserving
repetitive junior work because previous generations had to do it. Traditional professional
work often combined production and development in the same activity. AI allows those
functions to separate. Organisations therefore need to identify which developmental
effects remain important and deliberately reproduce, relocate or redesign them.
Two outputs of professional work
Work product is not the only product
For years, professional processes produced both work and workers capable of doing more
difficult work later. We measured the first because the second happened gradually in the
background. AI allows us to separate them.
Output A
Work product
The visible organisational output.
- Contract reviewed
- Advice produced
- Code written
- Account reconciled
- Research conducted
Output B
Human capability
The less visible output created through participation.
- Pattern recognition and exception judgement
- Understanding of normality
- Source scepticism
- Escalation judgement
- Calibration of confidence
Capability debt is the future human capability placed at risk when developmental experience is removed from a workflow without an alternative mechanism for producing or maintaining the capability it supported.
The analogy to technical debt is useful only if it forces a question that ordinary
productivity metrics miss. Automation does not necessarily create a debt; some repetitive
work adds little, and well-designed AI use can accelerate feedback. The point is that
organisations currently have poor visibility of whether it is happening.
The assumption underneath every Loop pattern
The human involved is capable of the judgement assigned to them
- Human-in-the-Loop
- Can the reviewer meaningfully challenge the system rather than merely approve its output?
- Human-on-the-Loop
- Can the monitor recognise abnormal behaviour, understand its significance and know when intervention is required?
- Human-Accountable-for-the-Loop
- Does the accountable person possess sufficient understanding and judgement to exercise authority over the system rather than merely carrying formal responsibility for it?
Will the organisation still be producing people capable of performing these roles five or ten years from now?
Competence is not capacity
Competence asks whether the person can make the judgement required. Capacity asks
whether they can give it enough time and attention under actual workload. A reviewer can
be highly competent but overloaded, available but incapable, both or neither. Automation
may increase capacity by removing volume while weakening competence if people no longer
practise the parts of the work on which oversight depends. Neither effect should be
assumed; both should be tested.
Existing competence
Can this person exercise the required judgement today?
Maintained competence
Does the role provide enough continued exposure, feedback and practice for that judgement to remain credible?
Future competence
Does the operating model continue to produce people able to perform the role later?
Where does the capable reviewer come from?
A reviewer who starts from an AI answer is not in the same cognitive position as someone
producing an independent answer. Finding the consequential 2% in a draft that is 98%
correct may require more judgement than producing the original first draft, not less.
- 01 AI does the work because humans can review it.
- 02 Humans develop the judgement required to review it through experience of the work.
- 03 Humans receive less experience of the work because AI does it.
Where does the capable reviewer eventually come from?
Signals worth investigating
These do not automatically prove capability loss. A low disagreement rate may show that
the system improved. Each is a reason to investigate, compare with outcomes, and test
the human role directly.
- ! Reviewers almost never disagree with AI, particularly as model use expands.
- ! Escalation and exception rates collapse without a corresponding change in outcomes.
- ! Review times become implausibly short.
- ! Reviewers cannot explain why an output is acceptable or why an error matters.
- ! People repeatedly miss planted or naturally occurring exceptions.
- ! Confidence remains high while independent performance falls.
- ! Exposure to variation, unusual cases and consequences declines.
- ! The pipeline of people eligible for consequential review narrows over time.
Definitions
- Capability sustainability
- The ability of an operating model to develop and maintain the human knowledge, experience and judgement required for meaningful oversight and accountability as automation changes the underlying work.
- Capability debt
- The future human capability placed at risk when developmental experience is removed from a workflow without an alternative mechanism for producing or maintaining the capability it supported.
Keep returning to the operating-model question: if your AI workflow relies on human
judgement, where does that judgement come from and what keeps it credible?