Home
About
Approach
For Founders
Contact
How to validate ideas before you build them

I've learned that the biggest mistake in product development is building something before you know if anyone actually wants it. Validation isn't about proving your idea is right, it's about finding out if it's wrong before you waste time and money.

The best products I've seen were the ones where we validated our assumptions early and often. When you know what you're building actually solves a real problem, everything else becomes easier.

Validation Methods
Four proven ways to test your ideas quickly

Talk to Users

The best way to validate an idea is to talk to the people who would use it. Ask about their problems, their workflows, and what they're currently doing to solve the problem you're addressing.

Build a Prototype

Create the smallest possible version of your idea and get it in front of real users. A simple prototype can reveal more about user needs than months of planning.

Measure Behavior

Look at what people actually do, not what they say they'll do. User behavior is the most honest feedback you can get about whether your idea solves a real problem.

Test Assumptions

Every idea is built on assumptions. Identify your key assumptions and find ways to test them quickly and cheaply before investing too much time or money.

Key Questions to Ask
Questions that help you validate your idea
?
Are people willing to pay for this solution?
?
Is this a problem people actually have?
?
Are there existing solutions that work well?
?
Can we build this with our current resources?
?
Will people actually use this regularly?

The Validation Mindset

Validation isn't about proving your idea is right, it's about finding out if it's wrong as quickly and cheaply as possible. The goal is to fail fast and learn fast.

The best founders and product teams I've seen are comfortable with uncertainty. They know that most ideas will be wrong, and they're okay with that. What matters is learning quickly and adapting.

A Personal Reflection

I used to think that good ideas were obvious and that validation was a formality. Now I think that good ideas are rare and that validation is essential.

The most successful projects I've seen were the ones where we validated our assumptions early and often. When you know what you're building actually solves a real problem, everything else becomes easier.

Exploring new ideas? Me too.

I’m always curious about early-stage projects, especially the ones that move fast, test early, and aim to solve something real.