FOUNDERS
With an idea but no single sentence
for what belongs in the first product
NEWON STORE STORE · MVP
Starting to build the moment you have an idea
usually grows scope and delays learning.
Name the problem,
name the user,
and lock what belongs in version one —
in sentences, before code.
MVP Planning Kit puts hypotheses and scope
ahead of implementation.
OVERVIEW
MVP is not “build less.”
It is choosing which hypothesis to test.
Problem → user → value → core flow →
priority → scope → validation criteria —
that order keeps version one from drifting.
This kit locks that sequence into worksheets
so the team agrees before build starts.
WHO IT'S FOR
With an idea but no single sentence
for what belongs in the first product
Balancing stakeholder feature requests
and needing a fair way to cut scope
Building alone but still wanting
hypothesis, scope, and validation
written down
Wanting “what we build”
to read like a clear brief
before implementation starts
Where prototype, MVP, and V1 blur
and the current stage goal is unclear
Rewriting a new hypothesis and scope
when direction needs to change
MODULES
Write the problem users actually want solved
as a sentence — not a guess.
Blurry problems make blurry features.
Clarify early users and the situations
where the product is used.
A product for everyone rarely ships as a first MVP.
State why someone should use this product
in one sentence.
Differentiation is a promise, not a feature count.
Design only the essential path
through the product.
Secondary screens wait.
Rank work as Must / Should / Could
so cuts follow criteria, not mood.
Decide explicitly what ships in v1
and what does not.
The exclusion list is a deliverable.
Define hypotheses and signals
to observe before and after launch.
Separate “we built it” from “we learned.”
Outline Prototype → MVP → V1
in one line of stages
so the current stage stays visible.
INCLUDED
Core items in this product. Exact formats may refine before release.
OUTCOMES
The team debates features
while pointing at the same problem.
What stays out of this MVP
stays written — fewer re-litigated debates.
What you are trying to learn
is written separately from build goals.
You can see whether you are in Prototype or MVP
and what must be true before the next stage.
HOW TO USE
Before any feature list,
lock the user problem as one sentence on Problem Definition.
On Target User, remove “later customers”
and keep the people needed for the first test.
Anything that does not serve the Value Proposition
or Core Flow leaves the Must column.
On MVP Scope, write what you are not doing now
so stakeholders see the same boundary.
List behaviors and feedback to watch on Validation Plan,
then mark the current stage on Build Roadmap.
PREVIEW
Preview · sample data only
FORMAT
FAQ
Yes. Re-list in-progress features on Scope and Priority to decide what still belongs.
No. This kit is the planning layer for scope and hypotheses.
Yes. Problem, user, and validation structure are shared. Adapt customer definition and GTM language to your context.
MVP Planning Kit decides what to build. App Launch Kit covers shipping a defined product to the store.
GET NOTIFIED
We only publish finished products. Leave your email and we'll notify you at launch.
This resource is currently being built at Newon.
We only publish finished products.
COMING SOON