There’s a version of this everyone knows: “the elevator pitch.” But the kitchen conversation test is actually more useful, because there’s no performance pressure. Nobody’s expecting a pitch. You’re just talking. And if your idea can’t survive that, it’s not ready.
The kitchen test exposes something specific: whether you actually understand your own idea clearly enough to describe it to a normal human in thirty seconds. Most founders fail this test for months longer than they should.
Why Founders Overcomplicate Their Own Explanations
Usually it’s because the scope is too wide. The product tries to do too many things, or solve a problem that’s slightly too abstract, or serve a user that’s slightly too vague. When you can’t reduce it to a sentence, it’s almost always a product direction problem, not a communication problem.
The solution isn’t to practice your explanation more. It’s to narrow the product until the explanation becomes automatic.
One Problem, One User, One Action
The clearest MVPs share this structure: they solve exactly one problem for exactly one type of person in exactly one specific way. That’s it. When you can hold your product to that constraint, the explanation becomes a sentence: “It helps [X person] do [specific thing] without [specific obstacle].”
Every word beyond that sentence is scope that probably shouldn’t be in the first version.
The Casual Reaction Doesn't Lie
When you describe your product casually and someone immediately asks a follow-up question or connects it to a problem they personally have, you’ve passed the test. When they smile politely and change the subject, or ask a question that’s really just trying to be supportive — that’s useful information too.
This is why the informal conversations that happen constantly at Olivier hacker house are worth more than scheduled feedback sessions. Low stakes, honest reactions, people who think in product terms every day. Your idea gets tested in real conversation before you’ve committed too much to the wrong direction.