The gap between AI capability and product-market fit is not a technology problem. It's a design problem. After two decades of building consumer products and now building our own AI tools, we've seen the pattern repeat: brilliant models wrapped in experiences nobody wants to use.
The capability trap
Most AI products start with what the model can do, not what the user needs done. The team builds an impressive demo, raises funding on the strength of the technology, and then discovers that users don't care about capabilities — they care about outcomes. A model that can analyze 10,000 data points is useless if the user needed three specific answers and a recommendation.
Consumer experience teaches the opposite approach: start with the job to be done. What is the user trying to accomplish? What does their workflow look like today? Where does it break? The AI is the engine, not the product. The product is the experience that surrounds it.
The trust deficit
AI products face a unique challenge: users don't understand how they work, and that creates anxiety. Twenty years of CX research tells us that anxiety kills adoption. The solution isn't explaining the model architecture — it's building interfaces that communicate confidence, show their work, and give users appropriate control.
Transparency isn't a feature. It's a design principle. Every AI output should come with enough context for the user to evaluate it. Not a technical explanation — a human one. "Here's what I found, here's why I think this, here's what I'm less sure about."
The iteration gap
Traditional software ships features. AI products ship behaviors. And behaviors are harder to evaluate, harder to test, and harder to improve incrementally. Most AI teams aren't set up for the kind of rapid, research-driven iteration that consumer product teams take for granted.
This is where having built consumer products for 20 years becomes a genuine advantage. We know how to run tight feedback loops, how to instrument for behavioral data, and how to iterate on experiences — not just models — based on what users actually do.
The best AI products feel like they were designed by someone who has spent years watching people use software — not by someone who has spent years training models.
What we're learning building The Lathe
As we build The Lathe, our CX evaluation tool, we're starting with the simplest possible interaction: paste a URL, get a score. No onboarding, no account creation, no configuration. One input, one output. The AI does enormous work behind the scenes, but the user experience is as simple as a Google search.
That simplicity will be the product of 20 years of consumer experience, not 20 months of AI development. The model is the engine. The experience is the product. And the experience is what people will pay for.