Nzubechukwu.
← All posts
Product building5 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.

By Nzubechukwu Cyprian · Pharmacy student at UNN, full-stack developer

Generative cover art for the post “The MVP is not a bad product — it's a question”

I used to think MVP meant "the janky version." Then I watched my janky versions get accurate, deserved verdicts: nobody wants a janky thing. The confusion is in the name. Minimum viable doesn't mean minimum effort — it means the smallest version that can ask a real question and receive a real answer.

Reframing the MVP

An MVP is an experiment instrument. It exists to answer: will anyone use this? will they come back? what do they actually do with it? The "minimum" is the fastest honest path to those answers — and honesty is the binding constraint.

A broken thing answers nothing; people bounce and you learn only that broken things bounce. A gold-plated thing answers too late. The MVP is the sweet spot: ugly is fine, lying is not.

What "viable" means in practice

  • the core flow works end to end, on a bad phone, on a bad network
  • the value is legible in the first minute: what this is, what it does for you
  • nothing fake: no fake testimonials, no fake users, no fake numbers — self-respect is data hygiene
  • measurement exists from day one, or the experiment produces no result

The part nobody mentions

The MVP's most important output isn't the product. It's the answer. Sometimes the answer is "no" — and shipping the question means you get to hear it before you spent a year.

Nzubechukwu Cyprian studies Pharmacy at the University of Nigeria, Nsukka and builds software, products, and AI experiments in between.