Return on investment compares the value produced by an investment with its cost. For AI coding tools, the tempting shortcut is to ask developers whether they feel faster. That shortcut can produce trust debt: experienced developers predicted a 24% speed gain, estimated 20% afterward, yet took 19% longer in a randomized trial. section 9.4.2
A defensible ROI assessment should:
- Start with the full cost picture, then compare it with additional value rather than assumed productivity gains. section 9.4.2
- Treat self-reported productivity as a hypothesis, not evidence; project complexity, morale, technical debt, and requirements clarity can distort attribution. section 9.4.2
- Measure observable proxy metrics such as cycle time, defined as the interval from task start to merged pull request. section 9.4.2













