Development
Prototypes
A prototype is a physical test of a design question—shape, size, appearance, fit, handling, or another requirement—not automatic proof that the final part is ready for every use.
Define the question before the prototype
A useful prototype has a job. It may need to answer whether two features line up, whether a shape is comfortable to handle, whether the scale looks right, or whether a part fits the surrounding object. Clear questions make the test more valuable.
Use the simplest test that gives useful information
Not every prototype needs the final finish, full detail, or complete assembly. A partial test piece can be enough to check a hole pattern, slot, clip, clearance, or mating surface. Simplifying the test can make iteration faster without pretending the prototype is a finished product.
Record what changed between revisions
When a prototype reveals a problem, the next revision should address that evidence. Measurements, photos, notes, and version identifiers help prevent an old assumption from slipping back into the design.
Know what the prototype does not prove
A successful fit test does not establish structural, electrical, thermal, medical, food-contact, or other safety-critical performance. Those questions require their own evidence and appropriate validation.
Explore the next step
Review the full project workflow, see material considerations, compare functional parts, or describe the question you need to test.