Back to notes

March 30, 2026 · 4 min read

Fixing ML Experiment Tracking Chaos With One Boring Tool

A model team's experiment history lived across spreadsheets, Slack threads, and someone's memory. One boring experiment tracking tool fixed more than a quarter of process documents ever could.

Case StudyMLOps

I joined a project where "which hyperparameters got us the best result last month" required asking the one person who remembered, and he was on vacation. Experiment results lived in a spreadsheet that three people edited inconsistently, a few Slack threads with screenshots of metrics, and a handful of notebook outputs that had since been overwritten by later runs. Nobody could reliably reproduce a result from six weeks earlier.

The problem wasn't discipline, it was tooling

The team wasn't sloppy — everyone individually tracked their own runs reasonably well. The failure was structural: there was no single place every run automatically landed, so reconstructing the full picture meant reconciling four different people's personal systems, each with its own gaps. Adding a process document asking people to log things more consistently would have added friction without fixing the actual gap, which was the absence of a shared source of truth.

You don't fix fragmented experiment tracking with a reminder to be more organized. You fix it by making the organized path the only path that takes less effort than the alternative.

What changed with one tool

We adopted a basic experiment tracking tool — nothing exotic, logging parameters, metrics, and artifacts automatically on every training run with a couple of lines added to the training script. The adoption cost was low enough that it beat the spreadsheet on convenience alone within the first week, which mattered more for actual adoption than any argument about best practices.

  • Every run automatically logged with full hyperparameters, no manual entry required.
  • Metrics comparable across runs in one dashboard instead of reconciling screenshots.
  • Model artifacts linked to the exact run that produced them, so reproducing a result became a lookup instead of an investigation.
  • New team members onboarded by pointing at the tracking dashboard instead of asking around.

Within a month, "what got us the best result" became a thirty-second lookup instead of a scavenger hunt dependent on one person's memory. The tool itself wasn't sophisticated. The fix was replacing a system that depended on individual discipline with one where the disciplined behavior was also the laziest option.