When we prepare an industrial design prototype, we start by asking what this version needs to help us understand. It may need to show several things at once: how a mechanism moves, how someone uses it, or whether the design asks for more complexity than the function deserves. The priorities depend on the product, the stage of development and the time available.
That focus can change between versions. Something that needed close attention in the first build may become a supporting concern in the next, while another question becomes more important. I find it useful to keep the decisions in view throughout the work, from choosing what to build to discussing what should happen after the review.
1. Define what this version needs to make clear
A model made to assess appearance might be empty inside, with careful attention given to the outer surfaces, colours and finish. Its purpose is to let us see the lines and volumes as physical forms, with our own eyes, beyond the 3D model on a screen.
For EGO, we also worked with prototypes focused on the sliding mechanism: how it moved, how the force felt and whether it returned to its original position. In that situation, the mechanism needed to be represented closely enough to examine those interactions, even when the exterior was not the main concern.
Terms such as proof of concept, aesthetic prototype and functional prototype can help describe the emphasis. In practice, we still need to explain what a particular version is meant to do. The same label can suggest different levels of completion to different people, and a project does not always fit a neat sequence of prototype types.
Before building, we want everyone on the team to understand which questions matter now, which requirements must be respected and which parts of the design are still open to change. That gives us a basis for deciding how much work this version needs.
EGO (charging dock) aluminum prototype in open position
2. Choose what needs to be represented closely
The material and making process follow from what we need to assess. For a large product, it may be useful to work with a smaller model first, or a rough full-size model made with simpler materials. The point is to make the relevant parts of the design available for examination within the resources we have.
On Wash & Roll, the paper and foam models of the whole machine were made at full scale to assess proportions, layout, reach and access. The bag dispenser was a separate prototype, made with FDM 3D printing in PLA to test its function without investing too much in the sample.
The dispenser's parts followed the completed design for that version; they were not temporary substitutes for unresolved details. We were still using a prototype material and process, so the sample had to be understood within that scope. A detailed design and a representative production sample are different things to establish.
This distinction matters when presenting any model. People need to know what has been designed in detail, what is represented by a substitute and what the sample is actually ready to demonstrate.
3. Let the physical sample challenge the requirements
The bag dispenser on Wash & Roll helped us reconsider how much complexity a secondary function needed. The original design involved several plastic parts, including the opening cover and its supporting and mounting elements. It addressed the functions we had asked for, but looking at the assembled sample made the work involved much more tangible.
The team and the client could see how many components had to be made and assembled simply to let someone take a bag. That brought the production investment into the discussion. For a supporting function on a much larger machine, did all those requirements justify the complexity they created?
We revised the design into a single plastic part with a canopy-like form. It still protected the roll and incorporated the features needed for the roll to turn, the bag to feed out and the user to tear it off. The essential functions remained, while the larger set of features was reduced.
What mattered to me was that the physical sample helped us reconsider the requirements themselves. A design can satisfy the original brief and still lead everyone to ask whether that brief needs adjusting. Seeing and handling the assembly gave us a more concrete basis for that conversation.
one old versions of the bag dispenser
one old versions of the bag dispenser
one old versions of the bag dispenser
one old versions of the bag dispenser
one old versions of the bag dispenser on Wash & Roll Proof of Concept (PoC) prototype
one old versions of the bag dispenser on Wash & Roll Proof of Concept (PoC) prototype
Final version, the protective - canopy-like cover over the bag dispenser on the assembled Wash & Roll machine.
4. Agree on how the functions will be assessed
To decide whether a prototype is ready to move forward, we need an assessment alongside it. For each function or objective, we need to understand what counts as acceptable, what still needs work and what deserves a higher level of refinement. I think of this as a scorecard, with the criteria and priorities agreed by the team and the client.
Those priorities are not equal. A feature that gives the product its main value may need more attention than a supporting one. The acceptable level also depends on what the product is meant to achieve. A score only helps when everyone understands what it refers to and how it was assessed.
Wash & Roll made this particularly clear because it involved a group of functions. For the suction head used on stroller fabric, we needed to consider different kinds of dirt, including dry and wet material, as well as how the head moved across the surface. It needed to remove the dirt without pulling the fabric into the head and making the user's movement difficult.
That meant assessing cleaning performance together with the experience of operating the tool. We also needed to look at the functions in combination. Someone might use only part of the machine's available functions, so the result of that sequence mattered too: how clean the surface was afterwards, and whether any smell remained.
Checking each function separately gave us part of the picture. Assessing the result of using them together helped us understand what the user would actually get from the machine.
The cleaning tools on the assembled Wash & Roll machine, each with a different role in the overall cleaning process.
5. Make the scope and evidence clear to the people reviewing
I often think of a prototype as an agreement about the work. Everyone involved needs to understand its objectives, how it will be made, the materials being used and which parts are finished, temporary, bought in or still being developed. We also need a shared expectation of what the review can tell us.
Before a client review or trial, we explain the status of the relevant parts and functions, including which are ready for testing. This takes coordination within the team. Clover led Product Design and also handled project and product management in our work; keeping the client informed was part of that broader effort.
Clear expectations help people assess the sample fairly. If an unfinished feature is presented without explanation, the person reviewing it has to guess what they are seeing. I would rather explain the scope in detail beforehand, even if that means spending more time talking through it.
The same care applies when presenting test results. Saying that we tested a function and it was fine leaves too much unexplained. For Wash & Roll, we described how we simulated the dirt, how we carried out the cleaning and what happened afterwards. We took before-and-after photographs and recorded the tests on video so the client could follow the process as well as see the result.
The evidence gives the assessment context. It lets us discuss what was tested, under which conditions, and why we reached a particular conclusion. That shared understanding becomes more useful as the project continues and further decisions depend on earlier work.
Cleaning trials with different strollers and tools, documenting how each test was carried out so the process could be reviewed alongside the results.
A hands-on review of Wash & Roll by the client, assessing how the cleaning tool is held and moved across the stroller fabric.
6. Carry the important checks into the next version
After a review, we look at what is working well and what still needs attention. The next version can focus on the weaker areas, while keeping track of the relationships between functions. Improving one part can affect something that seemed satisfactory before.
Across updates, we check the hard requirements and critical performance again. Repeating every test from beginning to end for every function at every update would take a great deal of time. The important thing is to keep checking the performance that the product must retain as the design changes.
We also carried out additional checks from time to time during development. On Wash & Roll, these sometimes revealed smaller issues or interactions that had not been apparent in the earlier tests. They were another way to examine the product within the time and resources available.
For me, a useful prototype leaves us with a clearer understanding of what to keep, what to change and what still needs evidence. That understanding shapes the next build: its priorities, the detail it needs and the checks we should carry forward.
↑Back to Top