Problems First, Ideas Second

The Most Expensive Mistake a Founder Can Make

Almost every failed business starts the same way: with a clever idea. A founder is in the shower, on a train, or scrolling their phone, and a thought lands — wouldn't it be brilliant if there were an app that… From that moment on, they're hooked. They sketch logos. They register a domain. They tell their friends. They quietly start building. Six months and £15,000 later, they launch to a chorus of crickets.

This is the founder's original sin, and it has a name: solution-first thinking. You fall in love with a product, then reverse-engineer a problem to justify it. The problem feels real because you made it up to fit your idea. But the market doesn't care what you imagined in the shower. The market only cares about one thing: making a problem it already has go away.

The single most important reframe in this entire course — the one that will save you years of wasted effort if you internalise nothing else — is this: a business is not an idea you have. A business is a transaction in which someone hands you money to remove a specific pain from their life. Your job, before you build anything, before you spend anything, before you even name the company, is to find that pain.

Why Solution-First Thinking Feels So Right

Solution-first thinking is seductive because it's pleasurable. It rewards your ego, your creativity, and your need to feel clever. You get to be the visionary. You get to imagine a world in which your idea changes everything. Friends and family — who love you and don't want to crush your enthusiasm — will tell you it's brilliant. This is the warmest, most affirming part of being a founder, which is exactly why it's the most dangerous.

Problem-first thinking, by contrast, is uncomfortable. It requires you to sit with the messy, boring, sometimes embarrassing realities of how people actually live and work. It demands you ask awkward questions and accept unflattering answers. It forces you to admit, repeatedly, that the customer's problem isn't quite what you assumed. It is, in short, work that doesn't feel like work — it feels like investigation.

But here's the trade: uncomfortable problem-hunting up front saves you from catastrophic product-building later. The founders who succeed are the ones who treat the discovery phase as the most important part of the business, not the inconvenient prelude to building the thing they already decided to build.

The Anatomy of a Problem Worth Solving

Not all problems are created equal. Some problems are minor annoyances people have learned to live with. Others are screaming, daily, expensive sources of pain that customers are already actively trying to solve. The first kind will bankrupt you. The second kind can build an empire.

To separate the two, evaluate every problem you encounter against four ruthless criteria:

1. Frequency — How often does this problem occur?

A problem that strikes daily is worth far more than one that strikes once a year. Frequency creates habit, habit creates retention, retention creates compounding revenue. A founder solving "I need to send invoices every week" has a structurally better business than one solving "I need a tax accountant once a year" — even if the second problem feels bigger in the moment. Hunt for the daily, the weekly, the unavoidable.

2. Pain Level — How much does it actually hurt?

This is where the vitamin vs painkiller distinction matters enormously. A vitamin is a nice-to-have: "It would be lovely to have a better way to organise my photos." A painkiller is a now-have: "My payroll is broken and I can't pay my staff on Friday." Vitamins get deprioritised the moment a budget tightens. Painkillers get paid for in cash, today, often without negotiation. If your customer wouldn't describe the problem with words like urgent, stressful, frustrating, or costly, you're probably selling a vitamin.

3. Willingness to Spend — Is there already a budget?

The most overlooked criterion. The question isn't "would they pay?" — it's "what are they already paying?" If your prospect is currently spending money — on a competitor, a workaround, a manual process, a consultant, a duct-taped spreadsheet — then a budget exists. You're competing for an existing line item, which is enormously easier than creating one from scratch. If nobody is spending anything to solve this problem today, that's a red flag, not a green field.

4. Existing Alternatives — What do they do right now?

Every problem worth solving already has a workaround. Customers are resourceful; they don't sit in agony waiting for you. Understanding the current alternative — whether it's a competitor product, a manual process, an Excel sheet, hiring an assistant, or simply suffering through it — tells you three things: the price ceiling (what they currently pay), the differentiation needed (where the workaround fails), and the switching cost (what you have to overcome to win them). If you can't describe in detail what your customer does today to solve this problem, you don't understand the problem yet.

The Compliment Trap

Here is a hard truth that will save you tens of thousands of pounds: compliments are not data. When you describe your idea to a friend and they say "that's brilliant, I'd definitely buy that" — you have learned nothing. You have learned only that your friend likes you and doesn't want to upset you. Hypothetical future buying behaviour is the cheapest currency in the world. People give it away by the truckload because it costs them nothing.

The only signals that count as evidence are signals that cost the customer something to give:

• Money — a pre-order, deposit, paid pilot, or signed contract.
• Time — a calendar booking, a long unprompted conversation about their pain, attendance at a demo.
• Reputation — an introduction to a colleague, a public endorsement, a referral.
• Detailed past stories — "Let me show you the spreadsheet I built" or "Here's the invoice from the consultant I hired last month."

Everything else — "sounds great," "I'd love that," "you should totally build it," survey ticks, applause at a pitch night — is what we call fluff. Fluff is psychologically rewarding and commercially worthless. Train yourself to notice it, smile politely, and discount it to zero.

Hunting Backwards: A Practical Method

So how do you actually find a real problem? Not by sitting in a room brainstorming "business ideas." That's solution-first thinking with a clipboard. Instead, work backwards from observed pain. Three hunting grounds tend to be richest:

1. Your own working life. What did you complain about this week? What workflow made you swear at your screen? What did you pay too much for, or wait too long for? Founders who scratch their own itch have a built-in feedback loop — you are both the maker and the customer.
2. Industries you know intimately. If you've worked in hospitality, healthcare, logistics, or law for five years, you've accumulated a library of frustrations that outsiders will never see. Insider problems are gold because the market is opaque to competitors but transparent to you.
3. Conversations with strangers. Pick a customer segment that interests you and book fifteen exploratory conversations. Don't pitch anything. Ask only about how they currently spend their time and money on the area you're curious about. Patterns will emerge within ten calls. By call fifteen, you'll be able to recite their workflow back to them in their own words.

Notice what's missing from this list: thinking really hard. Problems are not discovered by introspection. They are discovered by contact with reality.

A Worked Example: The Meal-Prep App That Wasn't

Let's run this through a realistic scenario. Imagine you're a fitness coach with an idea: a meal-prep app for busy professionals. You mention it to forty friends and clients. Thirty-eight say "oh that's a great idea, I'd definitely use that." You're elated. You start sketching screens. You quote a developer at £8,000 for an MVP. Your finger hovers over the "confirm" button.

Stop. The forty enthusiastic responses are fluff — they cost nothing to give. You have zero evidence of a real, painful, expensive problem. Here's what a problem-first founder does instead:

• Interview fifteen busy professionals about how they actually fed themselves last week. Not what they wish they did. What they actually did. Listen for friction, embarrassment, money spent on takeaways, abandoned meal kits in the fridge.
• Calculate the existing spend. Maybe they're already spending £80/week on Deliveroo, £40 on supermarket lunches, £25 on a half-used HelloFresh subscription. That's £145/week already flowing — a clear budget signal.
• Run a £100 smoke test. A simple landing page offering a £39/month done-for-you meal plan, with a "Reserve your slot — £10 refundable deposit" button. Drive 500 visitors via paid ads. Measure how many strangers part with £10.
• Only build once five strangers have paid. Five paying strangers tells you more than five hundred enthusiastic friends. If nobody pays, you've spent £100 and a weekend — not £8,000 and six months.

The mathematics of this approach is brutal and beautiful. Problem-first founders fail cheaply and often. Solution-first founders fail catastrophically and rarely recover. Over a career, the difference compounds into entirely different outcomes.

Reframing Your Entire Approach

From this point forward, I want you to adopt a new identity. You are not an inventor. You are not an ideas person. You are a problem hunter. Your weapon is the question "walk me through the last time that happened." Your currency is observed behaviour, not stated preference. Your sworn enemy is the compliment.

This reframe will feel uncomfortable at first, because solution-first thinking is so culturally celebrated. Movies romanticise the lone genius with the brilliant idea. Pitch competitions reward slick decks about products that don't exist. LinkedIn is full of "visionary founder" posturing. None of it matters. What matters is whether, on a Tuesday afternoon, a stranger will hand you money to make their pain stop.

In the next lesson, we'll dive into the single most important skill in problem-hunting: the customer interview, taught through Rob Fitzpatrick's brilliant framework The Mom Test. You'll learn the exact questions that surface truth and the exact questions that surface flattery — and why the difference between them will determine whether your business survives its first year.