← Blog

The first one is for the trash

Christian HaslbeckChristian Haslbeck·

I once heard someone say: “The first one is for the trash.” And the more things I build, the more I realize how true that is. My first book? I wrote it…

I once heard someone say:

“The first one is for the trash.”

And the more things I build, the more I realize how true that is.

My first book?

I wrote it.

Finished it.

Then basically wrote the whole thing again.

The first version?

Trash.

My first fitness bootcamp?

The training wasn’t even the biggest problem.

The BUSINESS MODEL was trash.

Pricing.

Structure.

The way the whole thing worked.

I built it once…

learned what didn’t work…

then rebuilt the model.

The second version?

Way better.

It actually worked.

And then there’s BizBozz.

Same story.

The problem wasn’t that I had built too many features.

The foundation itself was wrong.

The architecture was too complicated.

Everything was too slow.

Things that should have been simple weren’t.

And eventually I reached the point where I had to admit:

I need to build this thing again.

Not improve it.

Not patch it.

Not keep adding fixes on top of a foundation I didn’t believe in anymore.

Rebuild it.

So I did.

And I’m starting to see a pattern here.

“The first one is for the trash” doesn’t necessarily mean:

Try something.

Fail.

Throw it away.

Start something completely different.

Sometimes the IDEA is absolutely right.

You just need to build it once…

to understand how to build it properly.

That’s a huge difference.

Because before you’ve done something for real, most of what you believe is theory.

You THINK you know what customers want.

You THINK you know what they should pay.

You THINK you know how the product should work.

You THINK you know how everything should fit together.

Then reality gets involved.

Customers behave differently.

Your pricing makes no sense.

Processes that looked good on paper don’t work.

Technical decisions that seemed reasonable become bottlenecks.

And suddenly you have something incredibly valuable:

Information.

That’s when you build version two.

The book gets rewritten.

The business model gets rebuilt.

The software gets rebuilt.

And suddenly you’re not building from assumptions anymore.

You’re building from experience.

I used to think rebuilding something meant the first attempt had been wasted.

I don’t anymore.

The first version might simply be the price you pay to understand the second one.

So if you’re building something for the first time and it’s not quite working…

don’t immediately assume the idea is wrong.

Maybe you’re just looking at version one.

And version one…

might be for the trash.

Christian