Evaluate Prototype Fit and Testing Rigour
Dissect the fidelity of the prototype against the core hypotheses being tested, evaluating whether a lower or higher fidelity build was required. Assess the methodology of the user test, the signal-to-noise ratio of the feedback gathered, and the logical strength of the proposed iteration plan. Pinpoint whether user responses were actionable behavioural signals or merely polite, non-binding opinions.
Isolating these four dimensions establishes whether the testing setup was capable of generating true validation or false positives. This granular focus prevents the venture from committing engineering resources based on flawed user signals or mismatched prototype fidelity.
The venture must produce an analytical matrix evaluating prototype fidelity, user test environment, feedback validity, and proposed sprint backlog items. The output must clearly differentiate between stated intent ('I would buy this') and observed user behaviour ('I clicked here').
Five questions an expert would ask when reviewing your output
Use these to challenge assumptions, pressure-test your logic, and check the quality of this action's output in the context of the parent task and wider venture development.
- 1
Why was this specific prototype fidelity chosen, and did it inadvertently constrain the user's ability to give structural feedback?
- 2
How much of the collected feedback consists of polite approval versus concrete behavioural commitment?
- 3
In what ways did the test environment introduce artificial friction or unnatural user guidance?
- 4
How directly does your proposed iteration plan address the most severe usability failures identified in the test?
- 5
What evidence proves that changing the prototype based on this feedback will actually drive core metric improvement?