tool 5 of 12 · working prototype

what you make

A clickable version of your core experience, built with AI design-to-code tools, that a stranger can try without you explaining it.

A prototype is the fastest way to find out what you actually believe about the product. Building it forces every vague idea to become a decision.

Five people, one script, three tasks, and a page of what broke. The prototype is not a tool until someone other than the team has touched it.

At the midterm check-in, someone will ask 'has anyone used it?' This is the page that answers yes.

01
The prototype covers the one journey step you marked as most broken, end to end.
02
A stranger can complete the main task without help. If they cannot, that is the finding.
03
Five test sessions are logged with the same three tasks each.
04
The results page lists what broke, ranked by how many people hit it, and what you will change.

01
Pick the one step of the journey the prototype has to prove. Not the whole product.
02
Build it with your AI tools. Write down every bad default you had to fix.
03
Write a test script: a one-line scenario and three tasks, in the customer's words.
04
Run it with five people. Watch, do not help. Note where they stall.
05
Write up the results: what broke, how often, what you will change before the midterm.

Print this page, or copy the structure into your Venture Book. Every line is meant to be filled in.

Scenario

Imagine you are… (one sentence that puts the tester in the customer's situation)

Task 1:

Task 2:

Task 3:

What broke, ranked by how many people hit it

What we will change before the midterm

What we will not change, and why