"AI" is the most diluted word in software. We forced ourselves for 30 days to replace it with whatever we actually meant. It changed how we think about products.
Earlier this year we ran an experiment on ourselves. For 30 days, nobody on the team would use the word "AI": not in writing, not in meetings, not in product specs. Every time we caught ourselves reaching for it, we had to substitute whatever we actually meant.
It was harder than we expected, and more illuminating than we deserved.
Here's what we ended up saying instead, ranked by how often:
"We need an AI strategy" became "we need to figure out which model goes where and why." Considerably less inspirational, considerably more actionable. The strategy meeting got 40 minutes shorter.
"AI will change everything." Couldn't even substitute this one. It just dissolved. Without the word "AI" doing the heavy lifting, the sentence had nothing in it. Which suggests the sentence had nothing in it to begin with.
"Powered by AI." Every time someone tried to write this in a product spec, they had to explain what was actually powering it. Sometimes the answer was "a fine-tuned 7B model running on Together." Sometimes the answer was "five if-statements." The fine-tuned model usually deserved the marketing copy. The if-statements never did.
Three things, in order of impact:
1. Our specs got better. When you can't say "AI does X," you have to say what specifically does X, with what input, with what fallback when it fails. The act of writing that out caught at least four design problems we would have shipped through.
2. Our estimates got more honest. "We'll add AI to the dashboard" is a quarter of work. "We'll fine-tune a small model on these 4,000 labeled tickets and serve it through a queue with a fallback to a frontier model when confidence is low" is also a quarter of work, but you can argue with it.
3. We noticed how much of "AI" is vibes. Maybe a third of the times someone reached for the word, what they actually meant was "something that sounds futuristic." That's a useful thing to notice in your own thinking.
We stopped the experiment after 30 days, but we kept most of the substitutions. "AI" sneaks back into casual conversation; we don't fight it. But in writing, in specs, in product decisions, we try to say what we mean.
It turns out a lot of the work in software is figuring out what you actually mean. Words are a load-bearing part of that. A word that does too much, eventually, does nothing.
Three years ago we had AGI timelines on a whiteboard. Today we keep a Notion doc tracking which of our predictions were wrong, and why the boring takes keep beating the spectacular ones.
Read Enterprise AIMost enterprise AI postmortems blame poor planning. Ours blames good planning. We rolled out without a strategy and accidentally found the right one.
Read EducationHalf the students we meet use ChatGPT for everything; the other half refuse to touch it. Both groups are wrong, in different ways.