Topic starter
11/06/2026 11:15 pm
TL;DR: A panel at Enterprise Ready Conference said about 80% of companies using agentic coding tools see net negative value, highlighting a gap between AI productivity promises and enterprise implementation realities, according to WorkOS's ERC 2025 recap. The real issue is not model capability alone, but whether teams can define, measure, and govern productivity outcomes well enough to capture value.
Editorial analysis by NHI Mgmt Group, based on content published by WorkOS: “The Productivity Paradox: When AI Tools Make Things Worse Before They Make Them Better”.
Key questions
Q: How should enterprises measure productivity when using AI coding tools?
A: Measure productivity with a balanced model that includes delivery speed, review quality, defect escape, and downstream maintenance cost.
Q: When does an AI coding tool create more cost than value?
A: It creates more cost than value when faster output increases review burden, maintenance debt, or customer friction faster than it improves delivery.
Q: What are the signs that an AI coding agent is failing on a development task?
A: Common warning signs include repeated attempts with similar changes, hallucinated code, failure to resolve dependency errors, and inability to recover from timeouts or incomplete understanding.
Practitioner guidance
- Define productivity before expanding AI coding use Set a measurable definition of engineering productivity that combines delivery speed, review quality, and downstream impact so the tool is judged on outcomes rather than excitement.
- Create a governed usage model for AI-assisted development Document where the tool is appropriate, what conventions users must follow, and which tasks still require human review so adoption does not drift into inconsistent practice.
- Track future cost alongside velocity metrics Monitor rework, defect escape, maintenance burden, and customer friction so faster code generation does not hide operational debt.
Bottom line: Most enterprises are not failing because AI coding tools lack capability. They are failing because productivity is still poorly defined and inconsistently measured.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 5 days ago by NHI Mgmt Group
12/06/2026 7:52 am
Enterprise productivity has become a governance problem, not just a tooling problem. The panel’s 80 percent net-negative finding shows that capability alone does not create value when organisations lack shared definitions of productivity. In practice, this is a lifecycle and operating-model issue: teams can buy the tool, but they still need decision rules for how it is used, measured, and judged. The implication is that productivity tooling now belongs in the same governance conversation as access, workflow, and operating standards.
A question worth separating out:
Q: Should teams rely on AI coding tools for core engineering workflows?
A: Only if the team has already defined the workflow boundaries, the quality gates, and the success measures that separate useful assistance from noisy automation. For core engineering work, the question is not whether the tool can produce code, but whether the organisation can control how that code is reviewed, maintained, and judged over time.
👉 Read our full editorial: AI coding tools create net negative value for most enterprises
This post was modified 5 days ago by NHI Mgmt Group