Intelligent Enterprise Engineering Doha · Riyadh · Amman
Research BriefEvaluation Science

Measuring silent drift in production LLM systems.

A study of 40 enterprise deployments finds that most quality loss in production LLM systems is invisible to launch-time evaluation — and quantifies how quickly it sets in.

Abstract

Across 40 enterprise LLM deployments observed over six months, measured output quality declined a median of 14% within twelve weeks of launch, with no corresponding change to the model. Launch-time evaluation detected none of it. Continuous evaluation against a blended golden-plus-production sample detected the decline a median of 9 weeks earlier than user-reported issues.

Key findings
  1. Median measured quality fell 14% within 12 weeks of launch, with the model unchanged.
  2. Launch-time evaluation detected none of the observed decline.
  3. Continuous evaluation flagged drift a median of 9 weeks before users reported issues.

Why drift is silent

Drift is rarely a model event. It is the slow divergence between the distribution a system was evaluated on at launch and the distribution it actually faces in production as inputs, users, and upstream data change. Because the model file never changes, nothing triggers a re-test — and the decline accrues unobserved.

The result is a system that appears stable on its launch metrics while degrading against the only thing that matters: the live traffic it serves today.

Figure 1 — Launch-time metrics stay flat while production-sampled quality declines.

Method

We instrumented 40 deployments with a continuous evaluation harness scoring a blended sample: a fixed golden set plus a rolling sample of real production traffic. Scores were collected weekly and compared against both the launch baseline and user-reported issue rates over a six-month window.

What the harness watched
  • Output quality against a blended golden-plus-production sample, scored weekly.
  • Divergence between launch-baseline metrics and live-sample metrics.
  • Lead time between harness-detected decline and user-reported issues.

Put a drift harness on your system.

A short engagement instruments one production workflow and shows you the drift you cannot currently see.