How to Document Prototype Tests and Design Adjustments
A clear test record turns each prototype iteration into a traceable design decision.
The problem: testing without evidence
A prototype is useful when it answers defined questions. If observations remain in disconnected messages, unlabelled photographs or team members’ memories, it becomes difficult to distinguish a repeatable finding from a personal impression.
Documentation does not need to be bureaucratic. It needs to identify what was tested, which version was used, under what conditions, what happened, what was decided and what must be checked next.
What to record before testing
Purpose and criteria
- The question the test must answer.
- The variable to observe or measure.
- The acceptance or comparison criterion.
- Known limits and risks.
Version and conditions
- Prototype version and date.
- Material, process and configuration.
- User, environment and sequence of use.
- Tools, loads and measurement method.
An eight-step method
- Define a specific question.
- Identify the version and sample.
- Run a comparable sequence.
- Record facts separately from interpretations.
- Compare results with the initial criterion.
- Decide whether to keep, adjust or discard.
- Assign the next action and owner.
- Verify the change in the next version.
Educational example: improving a snap-fit
This is an educational example, not a client case. A housing opens slightly when pressure is applied to one side. The team records wall thickness, print orientation, load point and prototype version. Two alternatives are modelled: a longer retaining hook and a secondary support.
Both versions are produced under the same conditions. The support limits movement without making assembly harder. This does not guarantee production performance; it provides better evidence for the next validation using a representative material and process.
Frequently asked questions
Does every iteration require a full report?
No. Changes affecting function, safety, ergonomics, assembly, cost or process need greater traceability. Minor changes can remain in a concise log.
Which format should be used?
A table, test sheet or issue tracker can work. Consistency matters more than the tool.
When is a test complete?
When it provides enough evidence for the next decision, including the decision that more information is required.
Need to validate a prototype and organise its iterations?
Órbita connects product requirements, prototyping, testing and documentation for local and international projects.
