Use the prototype to discover the right spec
Precise requirements can still rest on untested assumptions. Use low-risk prototypes to discover what the product needs to do, then test whether the implementation meets those requirements.
By the EWOR Team3 min read
A product specification can look perfectly clear on paper and still be wrong. You might set an exact size, weight or response time without knowing whether it matters to the people who will use your product.
In the EWOR Fellowship, we explore how to use prototypes to challenge these assumptions before investing in the final build. The goal is to discover what the product needs to achieve first, then test whether your implementation delivers it.
Find out what actually matters
Words like “portable”, “easy to set up” and “compact” sound useful, but they do not tell an engineer what to build. Adding a specific measurement does not solve the problem if that number is based on a guess.
Imagine designing a desk organiser for people who move between shared workspaces. Before investing in tooling, you need to understand what matters most: the footprint on the desk, the size when folded or how quickly it can be set up.
Start with the properties you are least certain about. A prototype can help you find the answers before those assumptions become expensive design decisions.
Build to learn, not impress
You do not need a finished product to explore an uncertain requirement. An adjustable cardboard model, for example, could help participants compare different organiser sizes alongside their usual desk equipment. A simple folded model could reveal whether the design fits into their everyday carrying arrangement.
Keep each test focused on one property. If you change the size, layout and setup method at once, you will struggle to understand what drove someone's preference. Watch how participants use each version, then ask what worked, what felt awkward and why.
Remember that a rough model is for learning, not proof that the final product will work. Use safe, non-functional materials, get permission to use the workspace and avoid testing hazardous loads or safety-critical functions with improvised prototypes.
Write the requirement with its evidence and limits
Use your observations to define requirements that reflect real needs rather than initial guesses. Record the dimensions or ranges tested, the difficulties participants encountered and the conditions in which they occurred. Note whose needs you tested and whose perspectives are still missing.
You may find that the organiser's folded size matters more than its footprint when open. That is valuable progress: you have discovered that the original design was optimising for the wrong thing.
Write down the requirement, the evidence behind it and any questions that remain. If your findings support a range rather than one exact number, keep the range. Consider accessibility and practical constraints, too, rather than designing only for the easiest use case.
Test the build separately
Once you have enough evidence to justify the next investment, test whether the actual implementation meets your requirements.
A cardboard prototype might help you establish useful dimensions, but it cannot prove durability, manufacturing tolerances, production cost or regulatory compliance. Those questions need appropriate engineering tests and, where necessary, qualified review.
Keep these two activities distinct: prototyping helps you discover what to build; implementation testing checks whether you built it correctly. A polished-looking mock-up is not a substitute for either.

No comments yet.
Be the first to comment on this signal.