Stop Validating. Start Building.

There is a piece of startup advice everywhere right now:

Validate before you build.

Interview customers. Test the market. Make sure people want it.

Yes, validation is useful.

But taken too far, it becomes terrible advice.

Angry Birds was Rovio’s 52nd game.

They built 51 games before it. They were close to bankruptcy when they made Angry Birds.

They built it anyway.

It became one of the biggest mobile game franchises ever, passing 5 billion downloads.

Slack is another example.

Its founders were building a game called Glitch. Slack started as an internal communication tool they built to make their own work easier.

Glitch failed.

The internal tool became Slack.

Imagine validating that idea first:

“We already have email.”

Maybe Slack never happens.

You don’t always know what you’re building until you build it.

How can you learn what works if you never try?

You build. You learn. You pivot. You try again.

I’ve seen this repeatedly in startups and businesses I’ve worked with.

Failure isn’t an exception to the process.

It’s part of it.

A lot of the people who now talk about what they should have validated first are talking from their failures.

And that’s exactly the point.

You don’t throw away the part that failed.

It becomes part of you.

You learn from it. You grow through it. And one day, you may realize that you couldn’t have reached where you are without it.

Even the current version of you would never exist without all the previous versions of you who failed, learned, and grew.

We didn’t come here to come out untouched.

We came here to learn and grow.

From the outside, success looks like one brilliant idea followed by one big win.

It rarely is.

Usually, there were many attempts nobody remembers.

AI makes this process even more accessible. Today we can build and test things faster, cheaper, and with far less pain. We can put something in front of users without spending months and hundreds of thousands before learning anything.

So yes, validate your assumptions.

But don’t turn validation into an excuse for never building.

Sometimes the only way to validate an idea is to make it real.

And customers don’t always know what they want.

Steve Jobs put it simply:

“A lot of times, people don’t know what they want until you show it to them.”

The most successful ideas often look crazy at first. That’s what makes them new.

If an idea sounds completely normal, there is a good chance someone is already doing it.

The crazy ideas are the ones that can change how people live, work, or think.

Airbnb sounded strange. Why would you stay in a stranger’s home?

The internet was once dismissed as a fad for computer nerds.

People laughed at ideas before they became obvious.

That’s normal.

And this is where I have a problem with people saying you should always validate before you build.

Some of these people have never built anything. Some have never seen how things are actually built or how startups operate.

And some are people who neglect failure as a part of the process.

Failure is part of building.

I’ve been part of startups. I’ve built products. I’ve watched ideas fail, change direction, and become something completely different.

Building is not a straight line.

You might start with one idea and end up somewhere you never expected.

That’s not failure.

That’s building.

So if you have an idea that genuinely excites you, and your gut keeps saying do it, then do it.

You might fail.

Good.

Learn from it. Build again. Pivot.

One-day success only happens in movies.