Best Practices

AI Output Can Look Productive While Making Teams Slower

October 21, 2026

AI Output Can Look Productive While Making Teams Slower

The trap has a name now, but the behavior is older than AI: teams start optimizing for visible output, then mistake activity for progress. With generative tools, that mistake gets easier to hide. More code ships, more prompts get logged, more dashboards light up, and yet the real system can be getting harder to maintain, review, and trust.

That is the productivity theater problem. The sources here point to the same pattern from different angles: leaders over-index on usage, teams overproduce low-value artifacts, and the work of verification quietly moves onto a shrinking number of humans. In one framing, the dashboard improves while durable output stalls. 1, 2

Why this trap shows up when AI scales

AI makes it cheap to generate more of almost everything: code, docs, tickets, tests, summaries. That is useful only if the organization can also absorb the downstream cost. Otherwise, generation outruns review, and the real bottleneck shifts from typing to judging.

That shift is visible in the data. Faros reports that AI adoption is associated with a 34% increase in task throughput and a 66% increase in epics completed per developer, but also a 54% rise in bugs per developer and a 242.7% increase in the incidents-to-PR ratio. In the same report, median code review time rose 441.5% and 31.3% of PRs merged without any review. 3

The pattern is even cleaner in the systematic review of 2024–2026 studies: short-term velocity gains are common, but by month six many teams see net negative outcomes as technical debt compounds. 4

"The throughput numbers measure what was shipped. They do not tell you what survived."

— Faros 3

That sentence is the right mental model for AI adoption. Volume is not survival. Throughput is not value.

The most common mistake: automating what feels annoying, not what matters

A lot of AI programs start with the wrong target. Teams automate inbox triage, note-taking, or other tasks that are personally annoying to a founder or manager but not especially important to the business. The result is a very polished form of distraction.

1 Minute Signal coverage of AI Founders describes this directly: most pilots fail because teams skip the diagnosis and mistake personally annoying tasks for high-impact professional requirements. 5 Another 1MS source adds that clients are often buying organizational relief and the appearance of an AI strategy, not necessarily a better system. 6

That is where vanity automation comes from. It creates the feeling of progress without a meaningful business edge. The work gets busier, the narrative gets cleaner, and the underlying workflow barely changes.

A better starting point is to classify work by impact and risk before you automate it. The sources consistently recommend separating low-novelty, low-risk tasks from high-consequence work such as authentication, payments, PII handling, and other areas where mistakes are expensive. 7, 8, 9

Why raw output metrics become a liability

The strongest warning across the sources is not “AI is bad.” It is that the wrong metrics will lie to you.

Lines of code, prompt counts, token usage, and AI acceptance rates are all easy to inflate. They can be useful for governance, but they are poor proxies for business value. Faros.ai is explicit that AI-generated code volume should be treated as a maintainability metric, not an ROI metric. Gorilla Logic says the same thing more bluntly: activity metrics measure effort, not value. 2, 10

Sparkey’s framework is especially useful here because it explains why a high acceptance rate can be ambiguous: it may mean the tool is excellent, or it may mean reviewers stopped reading. 11 Larridin adds a practical threshold, noting that acceptance rates above 45% warrant investigation rather than celebration. 1

"Lines generated, suggestions accepted and acceptance rate measure tool activity, not engineering outcomes. A high acceptance rate can mean the tool is good or that reviewers stopped reading."

— Sparkey 11

This is the heart of productivity theater. If leadership rewards usage, usage rises. If leadership rewards outcomes, the organization at least has a chance of learning whether AI is helping.

The hidden cost is usually review, rework, and debt

AI rarely eliminates work; it relocates it.

The most detailed empirical evidence in the sources points to technical debt and review strain. The IEEE/ACM study on AI-generated code found 484,366 distinct code quality issues across 302.6k AI-authored commits, with 22.7% of AI-introduced issues still present at HEAD and unresolved debt surpassing 100,000 issues by February 2026. 12 A separate systematic review found that code review time increased 35% for AI-generated pull requests, integration test failures grew 2.2x, and debt rose sharply in teams without debt gating. 4

New Relic’s 2026 State of AI Coding report shows the same pattern in operational form: leaders often rate AI-generated code highly at review, yet after shipping, 78% of organizations report more incidents and 86% report more senior-engineer firefighting. 13 That gap is not a paradox. It is the expected result of optimizing for apparent speed while underinvesting in verification.

"Software generation can scale faster than human review, shifting the verification bottleneck downstream."

— TechTarget 14

This is where many teams get surprised. They thought they were buying speed. They actually bought more review debt.

The cultural failure mode: teams learn to game the system

Once AI usage becomes a target, behavior changes. The data stops being clean, and the organization starts rewarding optics over substance.

Snowman Labs warns that mandated adoption produces trivial usage. 9 Sparkey warns that if engineers think the data ranks them individually, they will route work around capture or stop using tools openly. 11 Organizational research points to the same problem from a different angle: when AI is stigmatized as “unprofessional” or when formal controls are weak, usage becomes concealed and superficial. 15, 16

That is how productivity theater becomes self-reinforcing. Teams optimize for whatever the dashboard appears to reward, not for what the business actually needs.

The result can look lively from the outside. Inside, it often feels like more work, less ownership, and less trust in the codebase. 1 Minute Signal coverage of Nate Herk’s AI automation work captures that bluntly: clients often want the relief of saying they have an AI strategy, while the organization absorbs the real labor of making the system safe and useful. 6

What serious teams measure instead

If you want to avoid the trap, shift the scoreboard.

Several sources converge on the same replacement set: cycle time, lead time, defect rates, rework, rollback signals, production throughput, review latency, and developer satisfaction. 8, 9, 10, 17 The important part is not that these metrics are perfect. It is that they are closer to outcomes than raw activity.

Two especially useful rules emerge:

  1. Establish a baseline before rollout. Without a dated pre-AI record, improvement is a feeling, not a finding. 8, 11
  2. Pair every speed metric with a quality counterweight. Faster is only better if stability, rework, and incidents do not deteriorate alongside it. 8, 9

Tempo’s guidance is particularly practical: if adoption rises while review time and PR size worsen, the cause may be reviewer capacity, smaller batches, or better prompts—not necessarily the tool itself. 8 That is the kind of ambiguity mature teams should welcome, not flatten into a simplistic “AI made us faster” story.

What to do next

Before you scale AI-generated output, diagnose the workflow first.

  • Start with one repository or team, not the whole org.
  • Define the outcome you care about in business terms.
  • Classify tasks by impact and risk.
  • Track one or two speed metrics, but always pair them with quality and rework signals.
  • Treat acceptance rate, prompt count, and generated volume as governance data, not proof of ROI. 9, 10, 11

If the best evidence you have is that AI is making the dashboard look better, you probably have productivity theater, not productivity.

Share this

Tags

Sources

[1] More Code Is Not More Value: The Engineering AI Measurement Problem | Larridin

[2] Measuring AI Value in Software Development: What Shipped, Not What Was Generated - Gorilla Logic

[3] AI Engineering Report 2026 - The Acceleration Whiplash - Faros

[4] The AI Productivity Paradox in Software Engineering: A Systematic Review of Code Quality, Technical Debt, and Organizational Throughout (2024–2026)

[5] The AI Service That 95% of Businesses Desperately Need (We Sell This The Most) | 1 Minute Signal

[6] The Playbook for a $100M AI Agency | 1 Minute Signal

[7] When Your IC Says AI Made Them 3× Faster: An EM's Guide to Reading the Real Signal | LeadAI Editorial

[8] Measuring the impact of AI coding tools · Tempo

[9] How to Measure AI Developer Productivity: A Field Guide

[10] Why Lines of Code Is a Misleading Vanity Metric for AI Impact

[11] How to Measure AI's Impact on Engineering: Start With a Baseline | Sparkey

[12] Debt Behind the AI Boom: A Large-Scale Empirical Study of AI-Generated Code in the Wild

[13] The 2026 State of AI Coding report

[14] The risks of AI overreliance in software engineering | TechTarget

[15] Organizational Barriers to Implementing Artificial Intelligence Technologies in Engineering Team Workflows

[16] Diagnosing resistance, designing adoption: a systematic review of human and organizational factors in artificial-intelligence implementation in engineering organizations

[17] How to Measure AI Coding Tool Impact on Development Velocity – Exceeds AI Blog

Written by: 1 Minute Signal Editorial Team