How is the MVP cutline decided?

A deterministic decision tree checks outcome impact, dependency readiness, and uncertainty. The explicit Now limit keeps the first release small; there is no hidden magic score.

Why can a highly uncertain feature land in Now?

When it directly affects the core outcome and is ready to start, testing it early prevents the team from building around a false assumption.

Product decision tool

MVP Cutline

Weigh features by impact, dependency, and uncertainty, then draw a defensible Now / Next / Later / Remove cutline.

Decision: what is the smallest set that tests the core outcome, and what should stay out for now?

Approximate completion time: About 6–10 minutes

Front-end experience at HiWeb and Tat Bikeran
Public portfolio source on GitHub
Independent web products documented in the résumé
Persian and English portfolio

Outcome, features, decision0%

What must this MVP prove?

Now limit

A hard cap, not a quota to fill.

Feature 1

Feature name

Outcome impact

Dependency status

Uncertainty

Dependency detail (optional)

Why it matters — what must be true?

Feature 2

Feature name

Outcome impact

Dependency status

Uncertainty

Dependency detail (optional)

Why it matters — what must be true?

Feature 3

Feature name

Outcome impact

Dependency status

Uncertainty

Dependency detail (optional)

Why it matters — what must be true?

Start with the outcome this MVP must prove.

MVP Cutline

Feature 1

Feature 2

Feature 3

Frequently asked questions

How is the MVP cutline decided?

Why can a highly uncertain feature land in Now?