Skip to content

Comment on Approaching a Minimum Viable Product for a Startup

Comments

I've heard it before, and I'm sure I'll hear it again, but this, to me, is absolutely the sort of thing I need drilled in my head over and over and over again.

The current project I'm working on is simple. The idea is simple in general, the layout is simple, and while some of the technical glitches and implementation details may not be (they never are anyway) -- I keep overcomplicating things in my head.

I've gotten about 3 weeks worth of spare time thrown at it, which isn't much, but in that time, I've already wasted a ton of effort. I redesigned the layout yesterday. True, I made it simpler, and I think easier to use, and ultimately, it's a MUCH better layout for the product, but it was completely wasted effort to determine whether or not my product is even worth building, because I honestly don't know the answer.

I guess the main difference for me is that after a number of false starts (that later ended up as actual products, and profitable ones at that,) I have committed myself to finishing this thing, if only to say that I can build a project to completion without external motivators. That almost gives me an excuse to waste time because if it's rejected early, I'll assume it's due to a poor layout, or lack of features, etc.

So yeah, I needed to read that, and get back to square 1, and friggin stay there for a bit.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.