Part 2 of 3 — The Problem Detective Series
In Part 1, we talked about where ventures actually start: not with a clever idea, but with sustained attention to a problem. The idea comes later. The problem comes first.
Here is where most founders get into trouble.
Once they find the problem (or what they believe is the problem), they fall in love with their solution. They call it an idea. They build a story around it. They share it at dinner and gauge reactions. They attach to it. They defend it.
And the moment they do, their odds of succeeding drop significantly.
Not because the idea is bad. Because it has become personal.
The Problem With Calling It an Idea
Language shapes how we think. The word “idea” is doing something specific to you: it is telling you this thing is yours. It came from your mind. It reflects your taste and your judgment. It is an expression of how you see the world.
That is a beautiful thing, actually. It is also dangerous.
Because when your solution is an idea, feedback becomes a verdict about you. When the market does not respond the way you expected, it feels like rejection. When someone points out a flaw, you find yourself explaining why they missed the point. You push a little harder. You tell yourself they just need more time to understand it.
You stop reading the results. You start debating them.
I have watched founders carry a version of the same idea for three years, iterating endlessly, burning through savings and goodwill, because letting go of it felt like admitting they were wrong about something fundamental. The idea had become identity.
This is not a character flaw. It is human nature. It is also the thing that kills more ventures than funding gaps or bad timing or any of the other reasons founders tell themselves later.
What a Hypothesis Actually Is
A hypothesis is not a guess. It is a structured claim about the world that you intend to test.
Every idea you have ever had is already a hypothesis. You just have not framed it that way yet.
When you say “I think people would pay for a tool that does X,” you are making a set of claims: that people have the problem you identified, that they experience it frequently enough to care, that they would pay rather than solve it another way, that they do not already have a solution they are satisfied with, and that you can build something better than what exists.
Each one of those claims is an assumption. Some of them are probably right. One or two of them might be catastrophically wrong. And until you run the right experiments, you do not know which is which.
The people who built successful ventures did not avoid this problem by being smarter or luckier. They avoided it by treating their assumptions as things to be tested, not things to be defended.
The Assumption Stack Under Every Idea
Here is a useful exercise. Take your idea – whatever it is you are working on or thinking about building – and write down the three or four core claims it depends on.
Not the features. The claims.
“People have this problem” is a claim. “They have it often enough that they would change their behavior to solve it” is a different claim. “They would pay what we need to charge” is another. “We can reach them without spending more to acquire them than they are worth” is yet another.
Most ideas rest on five to seven core assumptions. A few of them are probably safe; you may have first-hand evidence that they are true. One or two of them are genuinely uncertain, and your business will either work or fail based on those.
Your job, before you build anything significant, is to figure out which assumptions are which.
This is not complicated. It is also not what most founders do. Most founders start building and hope the assumptions resolve themselves as they go. Sometimes they do. More often, they find out twelve months and a hundred thousand dollars later that assumption number three was wrong – the one that seemed obvious – and that everything built on top of it has to be reconsidered.
A Tool for Making Your Assumptions Visible: The Serving Statement
Most businesses have a mission statement and a vision statement. I have never found either of them particularly useful for founders in the early stages, because they tend to be aspirational rather than structural. What I find useful is something I call a serving statement.
It follows this format:
I serve [who you serve] so they can [the outcome they gain] by [the mechanism you provide].
That single sentence forces you to make three decisions that most founders leave fuzzy for far too long: who exactly you are serving, what specific outcome they get, and what your business actually does to deliver it.
Here is an example. A founder building a scheduling tool for independent therapists might write:
I serve independent therapists so they can spend more time with clients by automating the administrative work that currently fills their evenings.
That is a real statement. It commits to something. And as soon as it is written down, the assumptions underneath it become visible almost immediately: Do independent therapists actually lose significant time to admin? Is that the friction they feel most acutely, or is it something else? Would they change tools for this, or have they already adapted? What does “automating admin” mean specifically, and can we build it?
Every word of the serving statement is an assumption. The ICP is an assumption. The benefit is an assumption. The mechanism is an assumption. Writing it out does not answer those questions, but it makes clear which questions need answering before you build anything.
If you cannot write your serving statement in a single sentence, that is itself information. It usually means you have not yet made the decisions that would let you test your idea rigorously. That is the work to do first.
Why the Reframe Changes Your Behavior
When you shift from “this is my idea” to “this is a hypothesis I am testing,” something real changes in how you operate.
You stop trying to convince people. You start trying to learn from them. A customer who tells you the product does not quite work for them is no longer a dissenting opinion to be managed – they are data. A competitor with more traction is no longer a threat to be rationalized away – they are evidence about what the market values.
The market is always right. It may be early. It may not yet have encountered your product. But if you put something in front of enough of the right people and they do not respond the way you expected, that is information. It is not a verdict on your intelligence. It is a result from an experiment that told you something useful.
The founders who build lasting things are not the ones who had the best ideas. They are the ones who stayed curious longer. Who ran the experiments. Who let the results land instead of explaining them away.
Disassociating from your idea – genuinely seeing it as a set of claims to be validated rather than a vision to be realized – is one of the most practically useful shifts a founder can make. It is also one of the hardest.
The Question Worth Sitting With
If you are working on something right now – or you have been thinking about something for months without moving forward – try this.
Write down your idea in one sentence. Then ask: what would have to be true for this to work?
Not “what do I believe is true.” What would have to be true. There is a difference.
Once you have the list, ask yourself which of those things you actually have evidence for, and which ones you are assuming because it feels reasonable. That gap – between what you know and what you are assuming – is exactly where your attention should go next.
In Part 3, we will walk through exactly that: the specific questions to ask for each type of assumption, and how to structure a real experiment around each one without spending months or a fortune doing it. The fastest path to a real business almost always runs through one uncomfortable question: what would prove me wrong?
