Gather Prototype Feedback and Testing Assets
Collate all raw user testing logs, prototype versions, feedback forms, and session recordings from recent testing cycles. Organise these inputs alongside the current product hypotheses and iteration notes into a single accessible repository. Ensure all qualitative comments and quantitative engagement metrics are fully documented without selective filtering.
Assembling these assets creates a complete, unfiltered repository of user testing outputs for rigorous interrogation. This ensures the review is grounded in verified user interactions rather than memory or optimism, maximising the validity of subsequent venture decisions.
The founder must present a structured feedback repository containing full session transcripts, prototype spec sheets, user cohort metadata, and raw metric dashboards. Every claim about user behaviour must link directly to primary session records. Selective exclusion of negative or passive user responses is strictly disallowed.
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
What proportion of your testing sessions had full audio or visual recordings versus memory-based notes?
- 2
How did you ensure the raw user feedback collected was not filtered or softened by the interviewer during collation?
- 3
Which specific version of the prototype was used for each user cohort, and how are those differences tracked?
- 4
Where is the evidence that the user cohort tested truly reflects your target early-adopter profile?
- 5
How have you accounted for confirmation bias in the selection of positive quotes for this review?