Sometimes it's hard to persuade founders to adopt the experiment-learn-adapt cycle.

In other words, build the smallest meaningful increment that allows learning via feedback and measurement. Then adapt based on these learnings and repeat.
​
I'm not sure exactly why it is but many are unable to break away from the idea that they must deliver a fully functional, almost perfect product.

Maybe it's fear of releasing a product that draw criticism.

Maybe they're putting off getting real feedback.

Maybe it's because they think that's how it's done.

The best way I've been able to explain it is by framing the benefit against cashflow.

Even well-funded startups eventually feel the fear of a seemingly never-ending development phase draining their bank account with no end in sight.

The antidote is to start bringing in revenue so that cashflow can cover at least some of the build.

The fastest way to do this is to find out the customers' biggest problem and provide a minimal solution.

The alternative is to guess what this is while you're building the perfect "solution".

Once you've found an engaged customer base, everything gets easier.

Yes, you have to be build with discretion but the desire for your solutions puts wind in your sails.