Good enough for who?

Building a software business is a constant struggle. The struggle between making what's good enough for your customers and what's good enough for you, the maker.

This leads to overthinking and not shipping.

Sometimes we are building something that has a clear benefit to the customer. We're solving a real problem for them.

Sometimes we just want to build something that's beautiful, because we're creative and what's life without the appreciation of beauty?

I don't think there's a right answer for which side should win. I think the answer is in defining what's "good enough". And good enough for who?

Take the next thing on your to-make list - a new feature, a new piece of content, a new side project, whatever. Decide whom it's for. Is it for you? Do you just want to change the landing page style so you can be proud of it?

Or is it for your customer? Is it for something they've been requesting? Or an improvement to their user experience?

The clarity will help us focus. And ship faster. And ship regularly.

Good enough for our customers? Or good enough for us, the maker? They're both valid. We need to serve both.

We just need to decide. So we can focus, get it done, and ship it.