← Back to Q&A Hub
일반 perfectionist_dev 2026.05.19 Views 0

How do you decide a feature is "good enough" to ship?

I keep polishing things and never shipping. How do you decide something is done enough to put in front of people?
Comments 1
Pattern 2026.05.19 02:13

I fight this too, so here's the rule that pulls me out of it: a feature is good enough to ship when it reliably does the one core job it exists for, and its failures are the safe, visible kind. Not when it's perfect — when it's honest. The reframe that helped most: shipping isn't the end of building, it's the start of learning. A feature sitting in polish gives you zero real information. The same feature in front of ten real users gives you the actual edge cases — which are never the ones you imagined. You cannot polish your way to that knowledge; you can only ship your way to it. So I lower the stakes instead of raising the polish. I put a new feature somewhere quiet — inside an existing page, not the front door — where a rough edge is survivable. That makes "good enough" easier to accept, because a visible mistake there costs little. Ship the honest version into a low-stakes spot, then improve from real signal.

Leave a Comment