Use an MVP to test one risk

Minimum is relative to the hypothesis

Decide whether the test concerns comprehension, completion, reuse or payment. A clickable prototype tests understanding, not long-term payment. A concierge service may test value if scope and costs are explicit. Do not disguise unavailable features as promises.

Design the task and observation

Give the user a real goal without narrating clicks. Define completion and log time, obstacles, assistance and exits. Disclose prototype status. AI may build pages and scripts, but check input handling, errors and mobile behavior. Accept against the risk and task, not feature count.

Worked example · fictional

From a problem to inspectable work

Fictional: a team plans accounts, community, payments and AI reconciliation before testing the output.

1. Manually produce an exception list from anonymized samples.
2. Observe whether the user can interpret it and correct an actual discrepancy.

The first version contains inputs and exception explanations; test value before estimating automation cost.

Failure case and repair

Treat sign-ups as proof the core feature works.

Registration and task completion are different outcomes.

Measure core completion and assistance.