6 min read
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.
← All writing
Product building20 posts
Product building
What shipping teaches — deciding what to build, pricing, users, launches, deletion, and the discipline of finishing in public.
Written by Nzubechukwu Cyprian — Pharmacy student at UNN, full-stack developer and AI builder.
5 min read
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.
5 min read
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.
5 min read
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.
6 min read
Building for Nigerian users: what global tutorials don't cover
Data costs, payment rails, offline moments, and trust signals. The local realities that reshape every product decision.
5 min read
The MVP is not a bad product — it's a question
Minimum viable doesn't mean minimum quality. It means the smallest thing that can generate a real answer about real demand.
6 min read
How I do user research with no budget and no team
Five conversations beat five hundred survey responses. A solo developer's guide to hearing the truth without a research department.
5 min read
What I learned maintaining a product nobody pays for yet
Free products have users with opinions and none of the patience. The maintenance lessons that apply to everything I'll ever charge for.
6 min read
The launch that flopped taught me more than the ones that worked
I launched to silence: no crash, no users, no feedback. Diagnosing that silence was the most useful product education I've had.
5 min read
Features die quietly: recognising when to sunset something
Features don't announce their own death. The signals I watch for, and the discipline of retiring things with respect.
4 min read
Why I write the landing page before the product
One page of honest writing is the cheapest prototype. If I can't describe the product convincingly, I'm not ready to build it.
5 min read
The hidden cost of 'we'll add it later'
Technical debt isn't the code you wrote badly — it's the decisions you postponed. Every 'later' collects interest.
5 min read
Onboarding is a promise you make in the first thirty seconds
Users decide faster than your product loads. What the first screen must do — and the sins I stopped committing.
5 min read
Naming a product is positioning, not poetry
A good name does a job: it says what shelf the product lives on. My framework for choosing names that work.
6 min read
Building products while in school: an honest operating manual
Exams don't negotiate and neither do servers. The systems I use to build seriously without failing at either thing.
4 min read
The changelog is a product's memory and its marketing
A public changelog compounds: users see momentum, you see progress, and 'what changed' stops living in your head.
5 min read
Working with a distributed team across time zones
Async isn't a compromise — it's the design. What works for collaborating across countries without burning anyone's sleep.
5 min read
How I decide what to build next (when everything seems urgent)
Urgency is loud and importance is quiet. The scoring system that keeps my roadmap honest when every idea screams.
5 min read
Building with AI assistance without losing your engineering judgement
The convenience trap is real: muscle memory fades when a machine does the lifting. How I keep my own skills sharp.
6 min read
What a product ecosystem actually means (and why solo products are lonely)
One product is a bet. Several products that share users, lessons, and infrastructure are a portfolio of options. The difference is design.