"Done is better than perfect." Do you agree?
by•
When we started building @ProdShort , our first instinct was to make the product "ready" before showing it to anyone. Then we started seeing founders launching much earlier. Sometimes with nothing more than a landing page, just to see if people were interested enough to sign up... or even pay.
It completely changed the way we thought about validation. On one side, launching early gives you real feedback much faster. On the other, launching too early can make people leave before they see the real value of your product.
We're still not sure there's a perfect answer.
From your experience:
Would you rather launch an unfinished product early... or wait until you feel it's truly ready?
82 views
Replies
@amraniyasser My point of view is different , because every one's thinking different and ,things varies .
@amraniyasser I've started leaning much more toward launching early, but with one condition: The core promise has to work. People don't expect a new product to have every feature , but they do expect the main problem to solved . If that first experience is confusing or broken, it's hard to earn a second chance .
I think the sweet spot is shipping an MVP that delivers one clear outcome really well , then letting real users shape everything eles. Some of the most useful product decisions I've seen came from feedback we never would have predicted internally.
but still thinking , what was the first piece of feedback on Prodshort that made you rethink the product ?
Validation before perfection. Real users teach what planning can't .
I think there's a sweet spot between too early and too late. If your MVP can solve one real problem well , launch it. People forgive missing features much more than they forgive a product that doesn't deliver on its core promise . Early feedback is valuable , but only if users can actually experience the value you're trying to validate.
I'd rather ship a simple product that people can actually use than wait months chasing perfection. Real feedback usually changes the roadmap anyway.
I’d rather launch early, but only when the core product works and delivers real value. I think that the feedback from actual users is more useful than endlessly polishing in isolation.
For me done means someone gets value without needing a walkthrough. Everything else can improve later. That's usually my launch signal. What was yours?