How to tell if your idea solves a real problem

One of the most common reasons new products fail is that nobody needed them. The builder had an idea, fell for it, and built it before checking whether the problem was real. Here's how to check first, without building anything.

Start with the problem

Write the problem down before you think about a product. Name a specific person, the moment it bites and what they do about it today. "Freelance designers lose hours every month chasing late invoices, and most track them in a spreadsheet" is a problem. "An app for invoices" is a product.

Look for workarounds

The best sign a problem is real is that people already try to solve it: a spreadsheet, a paper diary, paying someone, or putting up with it and complaining. If nobody does anything about it today, it may not hurt enough for them to change their habits.

Score it three ways

• How much does it hurt?
• How often does it happen?
• Do people already spend time or money on it?

A problem that scores high on all three is worth a closer look.

Talk to people about the past

Find five to ten people who had the problem recently. Ask what they did the last time it happened. Skip "would you use this?" questions: what someone did last week tells you more than what they say they'll do. And keep your idea to yourself. Once you pitch, you get compliments in place of facts.

Then ask them to act

Opinions cost nothing, so they prove very little. A small test, like a one-page offer with a sign-up, asks real people to do something. Sign-ups are a good signal. Time is stronger. Money is strongest.

Where AI fits

AI tools can sort your notes, spot themes across interviews and write a test page fast. They can't tell you which problems real people feel. Only the people with the problem can.

The Idea region of Zero to One with AI covers all of this in lessons 1.3 to 1.5, with one example running through every step.