how do I find a partner for prototyping and pilot production runs?
effective prototyping addresses open questions before major investments are committed. a pilot production run also examines how the product and the intended manufacturing process interact. when selecting a partner, you should ask which assumptions are being tested, how representative the samples are, and how any identified deviations are fed back into the development process.
scope of services and delimitation
prototyping addresses open questions at early stages of product development. a pilot production run can also test how the product interacts with planned manufacturing and assembly processes. when selecting a partner, it is important to ensure that the supplier clearly describes the purpose and level of maturity of the samples. a single functioning prototype does not prove that repeatable mass production is possible.
depending on the project, individual functions are examined first, followed by their integration, and finally conditions closer to mass production. ask for the corresponding test plan and documentation of deviations. the prototypes should enable a concrete decision to be made, rather than merely demonstrating visible progress.
a prototype is a learning tool
a single prototype can demonstrate a function yet still be far from being reproducible in production. therefore, the level of maturity must be explicitly described. the materials, processes, and assembly methods may differ from those of the final product. document which of these differences are acceptable for the current test. only then can the results be meaningfully applied to the next stage of development.
four criteria for choosing a partner
- relevant references: evaluate the team’s actual contribution to the project.
- methods appropriate to the question: workshops, models, or tests are means to an end.
- practicality: results must be transferable to the next phase of development.
- clear boundaries: design, engineering, production, and other specialized roles require clearly defined responsibilities.
project process and decisions
a test plan links requirements to appropriate prototypes. early prototypes examine individual functions; later prototypes test how these functions interact. a pilot series can then be used to test the intended manufacturing process. after each phase, the team decides whether to make changes or proceed based on documented findings. unresolved issues should remain visible, even if a presentation prototype already appears convincing.
example of a product with different pattern variations
suppose a core function works in an open test setup. after integration into a compact enclosure, accessibility and installation requirements change. a new prototype setup must now address different issues than the original functional test.
for the subsequent pilot phase, it is determined which materials and processes already comply with the planned mass-production process. deviations are documented and incorporated into change decisions. this hypothetical example illustrates why prototypes should not be evaluated solely based on their external level of finish. what matters most is which properties are actually representative.
common mistakes in selection and contracting
avoid using the term “near-production” without providing a specific explanation. materials, processes, or manual rework can influence the result. another issue is a pilot production run whose findings cannot be clearly traced back to the product’s current status. ask who documents defects, investigates causes, and approves changes. a compelling presentation sample must not obscure known outstanding issues if the next investment decision is based on it.
compare costs and schedules effectively
costs arise from research, variations, prototypes, testing, and iterative refinement. have each phase and result reported separately. this will help you determine whether quotes cover the same scope of work.
the briefing for an initial meeting
describe the open questions and the current product development status. provide existing data, earlier prototypes and documented findings. specify the planned manufacturing processes, suppliers and test conditions. define which properties must be representative and where deviations are permissible. clarify who will build, test and evaluate the prototypes. the number of samples should be determined by the required investigations.
frequently asked questions about prototyping and pilot production runs
when should a design partner get started?
early enough that fundamental decisions can still be influenced. at the same time, enough constraints should be known to be able to develop realistic alternatives.
how important are prototypes?
they are useful when a specific hypothesis needs to be tested. simple models can often facilitate learning sooner than a single, elaborately developed model.
how are partners compared?
compare references, the actual role in the project, the team, the methodology, the deliverables, and the support provided through implementation. also ask which specialized services need to be supplemented by external providers.
how are results documented?
decisions, options, open issues, and approvals should be documented in a way that allows for traceability. the format of the documentation must be appropriate for the subsequent development phase.
when are external specialists needed?
whenever the required expertise or formal responsibilities fall outside the agreed-upon scope of the design. these interfaces should be identified early on.
how to avoid unnecessary loops
through clear decision-making criteria, timely coordination among experts, and prototypes that specifically address the greatest uncertainties.
the perspective of f/p design
we support the product design process by creating prototypes and making adjustments for production. the types of samples or pilot tasks your project requires are determined based on the outstanding review questions and the manufacturing partners involved. you can find additional work in the industrial-design-portfolio.
