The Label Problem

MVP became a branding word. It signals seriousness without forcing discipline. Teams say “MVP” the way people say “quick chat” for a meeting that eats the afternoon.

The label invents false comfort: we are being lean. Meanwhile the scope document keeps growing because every stakeholder adds the thing they personally cannot imagine living without.

If everything is required for the first release, nothing is minimum. You have a v1 with worse honesty.

Fear of Looking Incomplete

The emotional engine is embarrassment. Founders worry the market will laugh. Agencies worry the client will compare screens to a polished competitor. Engineers worry peers will judge the rough edges.

So the team pads the MVP until it looks like a product that already knows the answer. Learning slows. Cost rises. The hypothesis gets buried under features meant to impress instead of test.

Incomplete is not the same as careless. Incomplete on purpose is how you learn.

Feature Creep Dressed as Ambition

Ambition is healthy. Ambition without sequencing is just creep with better storytelling.

Watch for these tells:

• Admin panels before a single customer workflow works end to end
• Role systems for teams that do not exist yet
• Analytics for decisions nobody is ready to make
• Mobile apps when the desktop loop is still soft
• “Platform” language for a tool with one job

Each item can be right later. Bundling them into the MVP is how “minimum” becomes a nine-month build.

What Minimum Actually Means

Minimum is the smallest surface that can falsify or confirm the bet.

Not the smallest surface that looks like a SaaS homepage. Not the smallest surface that matches a competitor's nav. The smallest surface that answers: will someone do the core job here, repeatedly, maybe even pay?

That often looks awkward. Manual steps behind the curtain. Ugly UI. Limited accounts. A founder doing ops that software will eventually own.

Awkward and informative beats polished and mute.

Viable Without the Fat

Viable does not mean “has every expected feature.” Viable means someone can get value without heroic workarounds that destroy the signal.

If users cannot complete the job, you went too thin. If you built three adjacent jobs “while we were in there,” you went too wide.

The skill is holding both edges: enough to create a real outcome, little enough that the calendar still belongs to learning.

A Cutting Practice

When a scope list arrives labeled MVP, I run a cut:

1. Write the single sentence hypothesis.
2. List features that directly test that sentence.
3. Move everything else to a dated “after proof” list.
4. Challenge any item that exists to reduce embarrassment, not risk.
5. Keep cutting until the remaining set feels slightly uncomfortable.

If the room is comfortable, the MVP is probably still fat. Discomfort is a signal you are near minimum.

Write the cut list where everyone can see it. Hidden backlog items crawl back into the build under softer names. Public cuts create shared memory: we chose not to build that yet, on purpose.

Manual Is Allowed

A real MVP can include human effort behind the curtain. Emails sent by hand. Approvals done in a spreadsheet. Onboarding via a call. That is not cheating. That is buying information before you buy architecture.

The mistake is automating theater — building polished subsystems for steps you have not proven matter — while the core value loop still needs a human to babysit it anyway.

Automate what you have repeated enough to trust. Keep manual what is still a hypothesis. Software should compress proven work, not speculate at full production cost.

Founders sometimes resist this because manual feels unserious. Markets do not grade seriousness by how many services you deployed. They grade whether the job got done.

Permission to Be Small

Teams need explicit permission to ship something that looks unfinished on purpose. Without that permission, ego fills the gaps with scope.

Give that permission in writing if you have to: the release is allowed to look incomplete as long as the hypothesis is testable and the core job works. Make incompleteness a success criterion, not a shame.

Real MVPs are ruthlessly small and deliberately incomplete. Minimum is a discipline, not a vibe. Feature creep dressed up as ambition is still creep — and it still delays the only thing an MVP is for: contact with truth.