How do you decide a feature is "done" vs just shippable?
by•
Last week I spent two days polishing an edge case in a settings panel maybe 2% of users would ever hit. Meanwhile my onboarding flow still has a broken redirect I've been ignoring for a month.
I think it's a comfort thing, polishing a small, contained feature feels productive and safe. Fixing the core flow means touching stuff that's scary to break, so it keeps getting pushed down the list.
Lately I've been trying a dumb gut-check before every commit: "would a user even notice if I stopped right here?" If the honest answer is no, I stop and move to something that actually blocks someone.
Curious how you all draw that line, is it a rule, a gut feeling, or do you just ship when you're sick of looking at it?
37 views
Replies
I've learned that users usually notice broken flows way more than the tiny details I spend hours perfecting.
Same boat. I've learned "done" is usually a feeling, not a checklist and that feeling lies. Now I just ship once the core flow works end to end, warts and all.