The bottleneck isn’t the model.
In Gartner’s 2025 survey, 51% of software engineering teams using AI reported that new features reached market noticeably sooner. This 90-day playbook shows how to find what holds up a release and where AI can help.
Where should we send your copy?
Free PDF, 33 pages
Your developers got faster, and most delivery systems didn't.
+24%
more pull requests merged by engineers who adopted CLI coding agents in Microsoft's 2026 rollout, and the gain held.
Microsoft study of its Claude Code & GitHub Copilot CLI rollout (2026)
3×
the probability of a production incident as task output soared, with bugs per developer up 54% and review time up 91% on high-adoption teams.
Faros AI telemetry, 22,000 developers across 4,000+ teams (2026)
−7.2%
delivery stability for every 25% rise in AI adoption, a relationship DORA saw again in its 2025 study of nearly 5,000 professionals.
DORA, State of DevOps (2024) · State of AI-assisted Software Development (2025)
95%
of enterprise GenAI pilots show no measurable P&L impact, across an estimated $30–40B in spend.
MIT Project NANDA, State of AI in Business (2025)
The next AI gains will be bigger, if your delivery can take them.
By 2028
30–50%
lift in team productivity, from agents working in the background
up from 0–20% with today's code assistants
By 2027
40%
of platform teams will use AI across every phase of delivery
up from <5% today
By 2028
70%
of code vulnerabilities will be fixed by AI agents
up from 10% today
98%of engineering leaders in Gartner’s 2026 survey said at least some of their teams used AI in software engineering.
Gartner asked about delivery in a separate 2025 survey. Among software engineering teams using AI, 51% reported that new features reached market noticeably sooner.
Free PDF, 33 pages
Projections: Gartner, “How to Maximize the Impact of Agentic AI in the SDLC” (2026). Survey figures: 2026 Gartner Software Engineering Survey, 2025 Gartner AI in Software Engineering Survey.
Read the whole argument before you download it.
Get the whitepaperA developer can finish a task sooner while a feature still spends days waiting for review, testing or release. Measuring both task time and time to release shows where the gains go.
DORA’s 2024 research associated a 25% increase in AI adoption with an estimated 1.5% decrease in delivery throughput and a 7.2% decrease in delivery stability, and MIT’s 2025 State of AI in Business study found 95% of enterprise GenAI pilots produce no measurable P&L impact. The sharpest single result of the period: a randomized trial found experienced developers were 19% slower with AI assistance, even as they estimated they had been 20% faster.
Look at the whole path from request to release. When work piles up in review, writing code faster adds to the queue.
Manufacturing learned this the expensive way in the 1980s, and left behind a mature, unglamorous toolkit for exactly this problem. The paper applies it to AI adoption in three moves, plus the loop that restarts them: map the delivery value stream, aim AI (and plain automation) at the constraint, manage the flow with lean tools — and re-map, because a fixed constraint doesn’t disappear. It moves, and your AI strategy has to move with it.
By the end you’ll have a way to find your constraint this month, a rule for where AI goes next, a 90-day arc for the first pass, and the metrics that survive a board meeting. None of it requires a transformation program. All of it requires giving up the most comfortable assumption in the industry right now: that buying speed for individuals is the same thing as building speed into a system.
You get three moves and a 90-day plan to run them.
Map the stream, aim AI at the constraint, then manage the flow, with the metrics that show your board it worked.
- 01Executive summary
- 02The illusion of speed
- 03We’ve seen this movie before
- 04Move 1: Map before you automate
- 05Move 2: Aim AI at the constraint
- 06Move 3: Manage the flow
- 07The 90-day playbook
- 08Measure what the board can bank
- 09The people system
- 10Your move


Run the first pass in 90 days.
Weeks 1–2
Map & baseline
Value-stream-map one product stream. Baseline the DORA four keys plus flow time, flow load and flow efficiency from tools you already run, and pick the business number the stream feeds. Exit with one map, one baseline and one named constraint, before any tooling decision.
Weeks 3–6
Exploit the constraint
Relieve the constraint with the cheapest tool that works, which is often plain automation before any AI. Where AI fits the constraint, put it there first: review triage, test generation, spec drafting. Exit with one win that moves a number on the baseline.
Weeks 7–12
Subordinate & systematize
Turn on the flow policies: WIP caps for people and agents, batch-size ceilings, pull discipline. Pave the winning pattern into the platform, start a weekly flow review, then map again, because the constraint has moved. Exit with an operating rhythm your team runs without you.
Free PDF, 33 pages
Check every number on this page.
The paper combines public research with Sigao's engagement experience applying value stream mapping and constraint management to AI adoption. The research includes the DORA reports, the MIT NANDA business study, the METR randomized controlled trial, 2026 telemetry and rollout studies from Faros AI and Microsoft, developer surveys, and the lean and Theory of Constraints literature. The Gartner projections on this page are strategic planning assumptions and survey results from Gartner's published research, which is available to Gartner subscribers.
Where the evidence stops
Survey figures reflect their respondent populations, not the market as a whole. The operational numbers in the paper's value-stream figures are labeled illustrative composites, not client data. The METR result is specific to early-2025 tools in high-context settings and is cited as evidence about perception versus measurement, not as proof that AI slows all work. Projections are planning assumptions, not guarantees.
Written by Chris Sims, Managing Partner, Sigao. Published August 2026.
References
- 01Gartner, “How to Maximize the Impact of Agentic AI in the SDLC”, 2026
Subscription research. The three projections above are its strategic planning assumptions.
- 02Gartner, “A Journey Guide to Successful AI Utilization in the SDLC”, 2026
C.A. Swan reports the 2026 Software Engineering Survey on page 1 and the 2025 AI in Software Engineering Survey on page 4 (G00844726, subscription research).
- 03
- 04DORA, Accelerate State of DevOps Report, 2024
A 25% increase in AI adoption associated with −1.5% delivery throughput and −7.2% delivery stability.
- 05MIT Project NANDA, “The GenAI Divide: State of AI in Business 2025”, 2025
Directional finding, corroborated by the DORA results; its interview-based methodology has drawn critique.
- 06Microsoft, “Adoption and Impact of Command-Line AI Coding Agents”, on the early-2026 Claude Code and GitHub Copilot CLI rollout, 2026
Tens of thousands of engineers over four months; adopters merged ~24% more pull requests.
- 07Faros AI, “Acceleration Whiplash”, telemetry across 22,000 developers and 4,000+ teams, 2026
Vendor telemetry rather than peer-reviewed research; cited for its scale and direction.
- 08
- 09METR, “Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity”, 2025
Randomized controlled trial: 16 experienced maintainers, 246 real tasks; also at arXiv:2507.09089. Measures early-2025 tools and is cited for the perception-versus-measurement gap, not as a current capability estimate.
- 10
- 11
- 12Goldratt & Cox, The Goal: A Process of Ongoing Improvement, 1984
The Theory of Constraints and the Five Focusing Steps.
- 13Rother & Shook, Learning to See: Value-Stream Mapping to Create Value and Eliminate Muda, 1998
- 14Reinertsen, The Principles of Product Development Flow, 2009
Queues as the dominant, invisible cost in product development.
- 15Forsgren, Humble & Kim, Accelerate, 2018
The DORA four key metrics and their link to organizational performance.
The full 23-source bibliography, with per-claim citations and method notes, is in the PDF.
Short answers from the paper.
Why isn’t AI making my team faster?
Because your delivery speed is set by your slowest stage, and AI is almost certainly accelerating a different one. Individual gains become queued inventory at the bottleneck, typically code review, which is why adoption can rise while lead time doesn’t move. Map the stream, find the constraint, aim there.
What is value stream mapping in software?
A one-page drawing of every step a feature takes from idea to production, annotated with process time (being worked) and wait time (sitting in queues), plus rework loops. Its output is flow efficiency (touch time ÷ lead time) and the location of your longest queue. It takes about a week using timestamps from tools you already run.
What is the Theory of Constraints in software delivery?
Goldratt’s principle that, at any moment, one constraint sets a system’s throughput. Applied here: improvement at the constraint improves delivery; improvement elsewhere is a mirage. Its Five Focusing Steps (identify, exploit, subordinate, elevate, repeat) double as an AI deployment algorithm.
Where should we apply AI first in the SDLC?
At your current constraint: the stage with the longest queue on your value stream map. For most organizations right now that’s code review and verification, not code generation. If your constraint is deciding what to build, aim AI at prototyping and spec drafting instead of codegen.
How do we measure AI ROI in engineering?
Baseline first, then claim ROI only at the flow layer (lead time, deployment frequency, change-failure rate, flow efficiency) and business layer (time-to-market, cost per shipped feature), never from task metrics like acceptance rates or “hours saved.” A throughput-accounting check keeps it honest: did throughput rise, inventory fall, operating expense hold?
Does this mean the AI tools are overhyped?
The tools are genuinely powerful; the deployment doctrine around them is what’s broken. The same assistants that produce the adoption-up, delivery-flat paradox in a queue-blind organization produce compounding gains in a flow-managed one. The difference is the operating system, not the model.
The full argument, with the data and the 90-day plan, is in the PDF.
Find where your work waits.
The paper ends with ten questions to find your constraint. In a value-stream assessment, our coaches work through them with your team.
