The opening claim
Everyone quotes "ship the MVP." Almost nobody tells you what to cut.
So founders cut the wrong thing. They hear "minimum" and ship something half broken, then wonder why nobody trusts it. Or they hear "viable" and polish for six months and never ship at all. Same three words, two opposite graves.
The word doing the damage is "minimum." It has two meanings, and they point in opposite directions.
The two cuts 🧠
When you strip a product down, you can cut in exactly two ways.
A scope cut removes a whole feature or use case. You decide the first version does not do wishlists, does not do reviews, does not support five payment methods. What you keep still works completely, it just does less. Scope cuts are healthy. They are the entire point of an MVP.
A quality cut keeps the feature but ships it broken, ugly, or slow. The checkout is there, but it fails one time in five. The page loads, but in four seconds. The order goes through, but sometimes it never reaches the seller. Quality cuts feel like speed. They are not speed. They are debt with a customer's name on it.
The founders who die shipping ship quality cuts and call them MVPs. The founders who die polishing refuse to make scope cuts. Eric Ries, who coined the term, said it plainly: an MVP is not permission to build in a "sloppy or undisciplined way." Minimum scope was always the idea. Minimum quality never was.
Here is the test for any decision on your build: am I removing a feature, or am I shipping a feature badly? The first is a scope cut, do it without guilt. The second is a quality cut, and you will pay for it.
Scope cut vs quality cut
| Scope cut | Quality cut | |
|---|---|---|
| What it is | Remove a whole feature or use case | Keep the feature, ship it broken or slow |
| Example | v1 has no wishlist and one payment method | The one checkout you kept fails sometimes |
| Feels like | Discipline | Speed |
| Actually is | Focus | Debt the customer pays |
| Verdict | Do it ruthlessly | Never |
The Algerian reality
In a high trust market you can ship a rough thing and get a second chance. A user in San Francisco has a hundred apps that worked, so a bug reads as "early product," not "scam." Here you do not have that cushion.
People judge a page in about 50 milliseconds, before they read a single word. And roughly 90 percent of Algerian orders are still cash on delivery, which is not a payment preference, it is a trust verdict: people will not pay before they hold the thing. So when you ship something broken into a market that already assumes it might be fake, you are not "learning in public." You just handed them the proof they were looking for.
The trust tax means the quality floor is higher here, not lower. You can cut more scope than a Western founder, because nobody needs your v1 to do everything. But you can cut less quality, because the little it does has to be undeniable. Small and solid beats big and shaky, every time, in a market that starts from suspicion.
What to actually do 🛠️
- List every feature you imagined. Cut two thirds of it. Wishlists, reviews, filters, dark mode, the admin analytics, the five payment methods, the animations. Gone from v1. That is scope, and scope is free to cut.
- Name the one flow that IS the product. For a store it is: a buyer sees a product, orders it, and the seller receives that order. That flow is not allowed to be a quality cut. It works end to end, on a real phone, on real data, every single time.
- Make the kept things undeniable, not fancy. Undeniable means it loads fast, it never lies about money, and it does exactly what it says. That is not polish, that is the floor. Polish is the fifth animation. The floor is the checkout completing.
- Watch your own reflex. If you cut features easily but cannot stop refining the one you kept, you are the polisher, and your enemy is scope you should have deleted, not a rough edge. If you ship fast but leave a trail of half working things, you are the sloppy shipper, and your enemy is the quality cut. Know which one you are. (I am the polisher. I have shipped clean scope and then lost a week making a feature beautiful that I should have deleted outright. The system I trust is the one above: cut hard, then protect the little that is left.)
TL;DR 🧾
Minimum viable, not minimum effort. Cut scope until it hurts. Never cut quality at all. An MVP is the smallest thing that works completely, not the fastest thing that mostly works.