Episode 7 · 2026-08-14

Measuring Anything, Before the LLMs

Douglas Hubbard wrote the book people hand you when you say something cannot be measured. This interview is from 2016, before there was an AI budget anyone had to defend, which is exactly why it holds: the three reasons people call a thing immeasurable are the three ways an AI value case still falls over. The conversation is audio; the video is a visualizer.

Host Sam Rogers · guest Douglas Hubbard · 30 min

Also watch and listen

Watch the episodeYouTube: 30 minutes Read + listenSubstack: the episode, in your inbox PodcastApple Podcasts PodcastSpotify ReadFull transcript

A choice this episode can help with

What result would actually change your AI investment decision?

The signals

The subtractions

About this episode

The conversation is audio. It is a 2016 tape and no footage of it exists, so the video on YouTube is an audio visualizer: listen rather than watch, and nothing is lost either way. There was no livestream this week.

Recorded in 2016 for an interview podcast Sam made then, and recut here with a present-day introduction and close. That podcast was Sam's own, so weigh the sourcing accordingly. Douglas Hubbard invented the Applied Information Economics method and wrote How to Measure Anything: Finding the Value of Intangibles in Business.

The interview predates LLMs entirely. That is why it is worth playing now: everything in it about measuring intangibles was said before there was an AI budget to defend with it, which makes it a cleaner test of the argument than anything recorded since.

The episode opens on the clearest example. Hubbard asks Sam how he would measure collaboration, Sam gives the answer everybody gives, and Hubbard takes it apart using a question that works unchanged on every AI productivity dashboard shipped since. That exchange is why this tape came out of the archive rather than staying in it.

Want to bring your own signal and subtraction? Find yours.

Start here

Douglas Hubbard turns measurement into uncertainty reduction: name the decision, find the threshold that would change it, then learn only enough to cross it.

Topics: measurement · uncertainty · AI business cases · calibration

Key moments

Continue with

Put it to work

What outcome would make you expand, alter, or stop the pilot?

The newsletter

Read the newsletterMeasuring 500 Nuclear Engineers

One signal, one subtraction, one analogy, in five minutes. It draws on this episode but stands on its own. Every issue.