FAQ: “define an MVP”
Define an MVP
Among the landing FAQ’s “no obvious answer” decisions is the first product you can ship. An MVP fails in two ways: too narrow to learn, or too wide to finish.
What to hold together
Who the first user is, which behaviour you want to observe, what you are willing to do by hand. Without those three, “MVP” becomes a euphemism for “everything except the design system.”
Thinktree makes assumptions explicit: “if we drop X, what can we no longer learn?” is a better question than “which features do they want?”
How to use the workspace
One thread on the job-to-be-done, one on scope, one on the nos. Clarify shows the cuts. Journal catches the “we should also…” from standup so they do not sneak into the perimeter.
What it will not do
It does not estimate story points and it does not replace a backlog. You leave with a decision: this is the first cut, these are the reasons, this is what we refuse for now.
