0 to .1

1 minute read

Building things is easy. Anyone can put a button on an html page.

It takes time to make something great. Building the correct things is hard. That involves attention to details which are unknowable at the start.

What actually matters and what doesn’t?

Progress for a builder is a differentiable function that can be measured when you release a product, get users, and see how they use the product and whether it grows.

So much of my life was spent thinking that I needed to go from 0 to 1 with the perfect product, instead of realizing that launching some .1 prototype gives me the confidence and courage to keep going.

That initial jolt from 0 gives you a glimpse into how much your project could grow. And lets you know whether you’re solving the right problems.

0 to .1 doesn’t mean being lazy or dropping projects. It’s a deliberate strategy that healthily acknowledges the time investment to build something beautiful.

It’s really easy to cram more features in. But it’s almost impossible to rip everything out, even things you labored over, in order to get the .1 out the door.

Updated: