Proof Of Concept
A proof of concept is not meant to impress. It is meant to uncover. At Move we use the POC phase to test the biggest technical risks early, so we can find out what works, what needs to change, and whether the project is ready to move on towards an actual prototype and a manufacturable product.
Proof Of Concept
Uncover the biggest technical risks before they become expensive
In a product development process, it is important to distinguish between a mock-up, a proof of concept and a prototype. They serve different purposes, and if you mix them up, you risk spending both time and budget on the wrong things.
The critical first
Test the crucial principle early
Answers over finish
Development boards and temporary software
An early no
Cheaper than a late no
Gate to prototype
The next decision on an informed basis
The mock-up makes the idea concrete
A mock-up usually comes first. It is used to explore quickly the form, size, user experience and mechanical principles, or how the product may be experienced by the user. It does not necessarily have to work technically. Its job is to make the idea concrete and create a better basis for dialogue and decisions.
Proof of concept: do the principles work?
Next comes the proof of concept, or POC. Here the focus shifts from what the product looks like to whether the crucial technical principles actually work.
The biggest technical risks first
The purpose is simple: the biggest technical risks must be uncovered as early as possible, while they are still cheap to deal with. If the product's entire value depends on a particular sensor measuring accurately enough, that should be tested before the enclosure, the app and the production tooling are developed. If the solution requires heavy data processing, we should investigate early whether the chosen processor can handle the data stream. If several modules need to communicate reliably, that connection must be validated before the whole architecture is built around it.
It does not have to look good. It has to give answers
It takes discipline. There is a natural temptation to quickly build something that looks like a finished product. But a good POC may well consist of development boards, cables, breadboards, 3D-printed brackets and temporary software. It does not have to look good. It has to give answers.
Questions a POC should answer
These might be questions such as: Does the measuring principle work? Does the sensor have the necessary precision? Can the processor keep up? Is the latency low enough? Can the radio achieve the necessary range? Is the power consumption realistic? Can the mechanical function move precisely enough? Can the algorithm find what we expect? The earlier those questions are answered, the better.
The facilities to build and test quickly
At Move we have the facilities to build and test this type of solution quickly. We can combine development boards, existing electronics, embedded software, 3D printing, laser-cut parts, sensors and mechanical test rigs to get a critical function into your hands as quickly as possible. The goal is not to build the whole product. The goal is to build enough to make the next decision on an informed basis.
An early no is cheaper than a late no
The POC phase therefore acts as an important gate in the project. Once it is complete, we should have significantly greater confidence in the central technical assumptions. In some cases the result shows that the project can continue as planned. In others the technology has to change, the requirements need adjusting or an entirely different architecture has to be chosen. And sometimes the most valuable conclusion is that the idea should not be pursued in its current form.
That is precisely the value of a POC. An early no can be far cheaper than a late no.
Next step: the prototype
After a successful proof of concept, the project normally moves on to a prototype. Here the validated technologies are brought together into a more integrated solution, in which electronics, mechanics, software and user experience begin to resemble the final product. The focus shifts from “can it be done?” to “how do we build it right?”
A stronger foundation for the next phase
A good POC should therefore reduce uncertainty. When the phase is complete, the most important technical risks should be understood, and the project should have a far stronger foundation for investing further towards prototype, certification and production.
Frequently asked questions
What is a proof of concept?
A proof of concept is an early technical demonstrator used to investigate whether the most important technical principles of a product actually work.
What is the difference between a mock-up, a POC and a prototype?
A mock-up is used primarily to explore form, size or user experience. A POC tests technical feasibility. A prototype brings the validated solutions together into a more complete version of the future product.
Does a POC have to look like the finished product?
No. A POC must first and foremost provide technical answers. It can therefore consist of development boards, cables, temporary software and simple mechanical parts.
What should be tested in a POC?
That depends on the biggest risks in the project. It might be sensors, processing power, communication, battery life, algorithms, mechanical principles or other functions the product depends on.
When is a POC finished?
When the most important technical questions have been answered well enough to make a qualified decision about the next phase and move on towards an actual prototype.
Can a POC show that the project should not continue?
Yes. And that can be a good result. It is far cheaper to discover a decisive technical limitation early than after investing in an almost finished product.
Shall we turn your idea into reality?
Technical development takes more than good ideas — it takes the right skills. We have gathered hardware, software and engineering expertise under one roof, so you get from prototype to production quickly and safely.
Reach out to us →