The decision
A small product is not just a large product with fewer features. It is a complete answer to one task. A one-page scope should name the buyer, trigger, input, output, quality rule, permissions, cost limit, and exclusions. If the output cannot be tested, the scope is still too vague.
A worked example
An update-writing MVP accepts one plain-text note, produces one draft with cited source excerpts, and requires a human to approve it. It excludes meeting recording, CRM sync, bulk generation, and automatic sending. An acceptable result contains no unsupported factual claims and reduces editing time on a defined test set.
How to put it into practice
- Write the output before selecting the stack or model.
- Define one measurable acceptance rule and one unacceptable failure.
- List explicit exclusions that protect the first release from adjacent tasks.
- Set maximum input size, processing time, daily spend, and retention period.
A failure to plan for
“Simple dashboard” is not an exclusion. Dashboards often introduce accounts, permissions, history, exports, and support obligations. State exactly what a person can do and what durable data the workflow requires.
Try it on your project
Take your existing feature list and sort it into required for the first complete task, needed after evidence, or excluded. Rewrite the scope so a developer can build a test without asking what “good output” means.
Keep the next step small
Use the free demand scorecard or planning tools to make your assumptions explicit. The $19 launch kit brings the blueprint and seven editable worksheets together.