Skip to content

Blog

Morgan Stanley saved 280,000 hours by reading old code

Most teams point AI at code generation. Morgan Stanley pointed it at code understanding, the step where developer time actually went.

Written by

Measuring AI impact

Published: 9 March 2026 Updated: 2 min read

Most teams point AI at code generation. The biggest wins come from code understanding.

Morgan Stanley saved 280,000 developer hours. Not by writing new code, but by reading old code.

The time went into understanding

Developers spent days reverse-engineering legacy systems before they could safely change a single line. Undocumented modules. Code written by people who left years ago. Institutional knowledge trapped in files nobody dares to touch.

That’s where the time went: not into coding, into understanding.

What their AI tool does

  • Reads the existing codebase across multiple files
  • Gathers context from interconnected modules
  • Generates detailed specifications automatically
  • Documents what the code actually does
  • Turns tribal knowledge into structured context

This is Context Engineering applied to legacy systems.

In our experience, the pattern holds at every enterprise client we work with. The first thing we do is map where developer time actually goes. It’s never coding. It’s reading, understanding, and reverse-engineering what’s already there. Morgan Stanley just put a number on it.

An hour saved off the bottleneck is worth nothing

Eli Goldratt’s insight applies: “An hour saved on something that isn’t the bottleneck is worthless.”

Most AI tools target code generation. But if your bottleneck is understanding existing code, faster code generation is like buying a faster car and parking it in traffic.

Map the constraint before automating anything

What goes wrong:

  • Asking “How can AI help with coding?” is the wrong question.
  • Targeting the fastest part of the pipeline is wasted investment.
  • Optimizing code generation when developers spend days on comprehension is expensive theater.
  • Deploying AI without mapping where time actually goes is flying blind.

What works:

  • Map where time actually goes first.
  • Find what blocks the most people.
  • Identify what causes the most rework.
  • Target AI at that constraint, not at what’s easy to automate.

Ask what slows your developers down

Morgan Stanley didn’t ask “How can AI help with coding?” They asked “What slows our developers down most?”

Different question. Better answer. 280,000 hours saved.

Are you pointing AI at your actual bottleneck, or at whatever’s easiest to automate?

(Source: Mike Pizzi, Morgan Stanley’s global head of technology and operations, in The Wall Street Journal, June 2025, on the bank’s own tool DevGen.AI.)

Further reading

  1. AI inflates the metrics that don't measure value AI pushes up every number that is easy to measure: code volume, pull requests, velocity. Four metrics show whether the value went up with them. 1 min readShort post
  2. Another company's AI success story won't transfer to yours DORA research shows AI returns vary widely between organizations using the same tools. The variance is the signal: measure your own baseline and your own bottlenecks before copying a playbook. 1 min readShort post
  3. The highest AI returns come from automation, not time savings Data from more than 2,500 self-reported use cases shows time savings as the most common goal and the most modest return. Risk reduction, agentic automation and broad adoption pay off more. 1 min readShort post

All 16 posts on Measuring AI impact

ClientsClient work

Test the constraint in your system

The Factory Readiness Assessment connects this research to your value stream, your data, and the next decision.

Training on this topic: Agentic Engineering for Engineering and Product Leaders
See the assessment

Want to check one team first? The self-check: twelve yes or no questions, three minutes, instant result, no account. Take the self-check