The first question I ask every founder I work with is the same: “What problem are you solving?”
The response I get most often is some version of: “Well, we built this really cool tool that…” followed by a description of features, technology, and vision. That’s not a problem. That’s a solution looking for a problem. And solutions looking for problems almost always fail.
Problem-first thinking flips the entire process. Instead of starting with what you want to build and hoping someone needs it, you start with what people actually struggle with and build the minimum necessary to address it. It’s less exciting. It’s less glamorous. And it produces dramatically better businesses.
The Solution-First Trap
Most aspiring founders start with solutions because solutions are exciting. You imagine the product, the features, the launch, the growth. You picture yourself on stage talking about what you built. The vision is vivid and motivating.
Problems, by contrast, are boring. They’re about other people’s frustrations, inefficiencies, and unmet needs. There’s no glamour in understanding why freelancers hate chasing invoices or why restaurant owners can’t predict their weekly food costs.
But here’s the thing: customers don’t buy visions. They buy solutions to their problems. And if you don’t deeply understand the problem, your solution will miss the mark no matter how elegant it is.
I watched this play out repeatedly at the Startup Burgenland accelerator. The teams that started with “we want to build X” spent months building something beautiful that nobody needed. The teams that started with “these people have this specific pain” built something ugly that people immediately wanted. The Pixar principle applies: great things start terrible, as long as they start with the right problem.
How to Think Problem-First
Problem-first thinking is a discipline, not a talent. Here’s how to practice it:
Step 1: Observe Before You Ideate
Before generating any ideas, spend a week just observing. Watch how people work. Listen to what they complain about. Notice where processes break down, where people waste time, where money leaks out of systems.
Keep a running list of observations. Not solutions — observations. “My colleague spends 30 minutes every morning organizing emails.” “The restaurant owner I talked to manually counts inventory every night.” “Parents in my neighborhood can’t find after-school activities without checking four different websites.”
Each observation is a potential problem. The richest ones come from your own daily frustrations, but observing others expands your field of view.
Step 2: Qualify the Problem
Not every observation is a business-worthy problem. Qualify each one by asking:
Frequency: How often does this problem occur? Daily problems beat monthly problems beat annual problems.
Intensity: How much does it bother the person experiencing it? “Mildly annoying” doesn’t drive purchasing behavior. “This costs me three hours every week” does.
Current spending: Is anyone already spending money or significant time to address this? If yes, there’s a budget you can redirect. If no, you’ll need to create willingness to pay from scratch — much harder.
Addressability: Can you realistically build something that meaningfully improves this situation? Some problems are too systemic, too regulated, or too entrenched to solve with a startup.
Step 3: Talk to Ten People
Once you’ve identified a qualified problem, validate it with real people. Talk to ten who fit the profile of people who’d have this problem.
The conversation structure is simple:
- “How do you currently handle [problem]?”
- “What’s the most frustrating part?”
- “How much time/money does it cost you?”
- “Have you tried any solutions? What did you think of them?”
If 7+ out of 10 confirm the problem and describe it with emotional intensity, you have a real problem. If fewer than 5 confirm it, either the problem isn’t widespread enough or you’re talking to the wrong people.
This validation step is non-negotiable. Your assumptions about what people need are almost always wrong in some important way. Only real conversations correct them.
Step 4: Define the Problem Precisely
After your conversations, write the problem statement: “[Specific group] struggles with [specific problem] because [reason existing solutions fail].”
This sentence becomes the foundation of everything you build. Your product solves this problem. Your marketing describes this problem. Your sales conversation starts with this problem. Everything traces back to this one sentence.
If the sentence is vague (“people need better tools”), your understanding is insufficient. Go back to Step 3 and have more conversations until you can be precise.
Step 5: Only Now, Think About Solutions
With a validated, precisely defined problem, you’ve earned the right to think about solutions. And the solution you generate will be fundamentally better than one generated without this foundation, for three reasons:
- It targets the real pain point, not your assumption about the pain point.
- It uses the customer’s language, making marketing and sales dramatically easier.
- It’s already pre-validated, because you built it on evidence rather than speculation.
The solution doesn’t need to be complex. In fact, the simpler it is, the better. Your first version should embarrass you slightly — that’s how you know you shipped early enough to learn from real usage.
Problem-First in Practice: A Real Example
Let me walk through how this works with a real scenario from my experience.
Observation: Startups in the accelerator I directed kept struggling with investor pitches. They’d spend weeks preparing and still get basic questions they couldn’t answer.
Qualification: Frequent (every startup does multiple pitches), intense (failed pitches mean no funding), existing spending (founders were buying courses and hiring consultants), addressable (the core issue was specific and coachable).
Conversations: I talked to 15+ founders who’d been through pitch processes. The consistent pain: “I don’t know which questions investors will actually ask, so I prepare for everything and still get caught off guard.”
Problem statement: “Early-stage founders prepare for investor pitches inefficiently because they don’t know which questions are most likely for their specific stage and industry.”
Solution: A structured framework matching common investor questions to company stage, delivered as a workshop. Not an app. Not a platform. A workshop. The simplest possible thing that addressed the core problem.
That problem-first approach meant the workshop landed immediately. I didn’t have to convince anyone the problem existed — they already knew. I just had to show them the solution.
The Counter-Argument: What About Visionary Products?
Someone always asks: “What about the iPhone? Nobody knew they wanted a smartphone. Wasn’t that solution-first?”
No. It was problem-first, but the problems were well-understood: people wanted internet access on the go, they wanted music without carrying a separate device, they wanted better phone interfaces. Apple didn’t invent those problems. They observed them and built a single device that addressed all of them.
Even the most “visionary” products are rooted in existing problems. The innovation is in the solution, not the problem identification. You don’t need to be visionary to find a good problem. You just need to pay attention.
Building a Problem-First Habit
Like any thinking pattern, problem-first becomes easier with practice:
- Keep a problem journal. Every time you notice a frustration, inefficiency, or complaint — yours or someone else’s — write it down. Review weekly.
- Read reviews critically. When you read negative reviews of products in your domain, extract the underlying problem. The product failed, but the problem remains.
- Ask better questions. In every conversation, practice asking “what’s the hardest part of your week?” instead of “would you use a product that does X?”
- Resist solution mode. When your brain jumps to “I could build…” pause and ask “but do they need…” first. Train yourself to stay in problem mode longer.
The more problems you identify and understand, the better your business instincts become. Problem-first thinking is the foundation skill of entrepreneurship. Everything else builds on it.
Takeaways
- Solutions looking for problems almost always fail. Start with what people actually struggle with, not what you want to build.
- Observe before you ideate. Spend a week noticing frustrations, inefficiencies, and complaints before generating any ideas.
- Qualify with the four filters. Frequency, intensity, current spending, and addressability. All four need to be present.
- Validate with ten conversations. Your assumptions are wrong in important ways. Only real conversations correct them.
- Write the problem in one sentence. “[Who] struggles with [what] because [why].” This sentence becomes the foundation of everything you build.
