Shipping is a skill, and I practised it badly for years
Finishing things is not a personality trait — it's a practice with techniques. The ones that turned my graveyard of half-projects into shipped products.
By Nzubechukwu Cyprian · Pharmacy student at UNN, full-stack developer
For years I had a graveyard: brilliant starts, abandoned at 80%. Every one died at the same distance — close enough to work, far enough from done. I thought shipping was a character flaw I couldn't fix. It's a skill, and like any skill it has techniques.
The techniques that worked
Define "done" before you start. Not in your head — written. Three sentences: what exists, what it does, what's explicitly out of scope. Without this, done retreats forever as taste improves mid-build.
The 90% cut. When I feel finished-but-exhausted, I list what's left and cut until only what blocks a stranger's first use remains. Onboarding polish can come after ten people use it. The tenth user doesn't exist if the first never can.
Ship to one real person. A deadline that's a human being waiting is stronger than any calendar. I tell someone the date, then live with the shame of rescheduling or the joy of sending the link.
What shipping actually is
It's a muscle memory of small completions. Every finished thing trains the pattern; every abandoned thing trains the opposite. The graveyard wasn't a failure of talent. It was a training routine — in the wrong direction.
Keep reading
- Product building
Nobody told me product decisions are reversible or not
The single question that unblocked my decision paralysis: is this door one-way or two-way? Everything else is noise.
- Product building
The pricing page taught me more about users than the analytics did
Data told me what people clicked. The pricing page told me what they believed. Convincing beats tracking.
- Product building
Every product I've shipped taught me to delete more
My best products have fewer features than my first drafts. Subtraction is the quality signal nobody markets.