Anti-Patterns

Hidden Validation-Work Amplification

Anti-pattern: an agent rollout shifts effort from doing the work to validating, monitoring, and recalibrating the agent — net productivity is negative because the hidden human evaluation burden exceeds the visible automation gain.

Problem

Total human effort across the team rises, not falls, because validation effort exceeds saved-execution effort. The work shifts from doers to validators without staffing for it. Productivity-impact dashboards show the automation but not the validation tax. Differs from existing review-bottleneck-migration (which is the where-it-lands view); this names the *aggregate productivity loss*.

Solution

Instrument total human-hours per business outcome (validation, recalibration, escalation handling) and compare to pre-rollout baseline. Reject or downscope rollouts whose total-hours metric is worse. Surface validation effort as a first-class metric on rollout dashboards. Use llm-as-judge selectively but track its own accuracy drift to avoid pushing validation upstream invisibly. Pair with three-tier-autonomy-portfolio so validation cost is sized appropriately per tier.

When to use

  • Never as a default state. Cite when reviewing agent-rollout productivity claims.
  • Measure total human-hours per business outcome, not tasks-automated.
  • Surface validation effort on the rollout dashboard.

Open the full interactive page

Diagram, neighbourhood map, code examples, related patterns and full provenance.

Related