Proof of concept
A proof of concept is a small, quick experiment that shows an idea can technically work, before significant time and money are spent developing it properly.
What it means
It answers a single question: can this be done? It need not look like the final product, use final materials or be built to cost. A rough rig that shows the mechanism works is enough. A proof of concept should not be confused with a prototype, which looks and behaves more like the final product, or with a trial of customer demand, which tests whether anyone will buy it.
Example
A Bhiwandi powerloom owner wants to test whether a cheap sensor can stop a loom when a warp thread breaks. He fits it to one loom with a relay and a timer, and records 30 shifts. It correctly stops the loom in 28 of 30 breaks, enough to justify a proper design for 12 looms.
Records and checks
- Record the question being tested, the set-up, the number of trials and the results.
- Verify the success measure was fixed before the test began, and that results were counted honestly.
- The owner or engineer runs it; another person reviews the data before spending more.
Common mistakes
- Judging it by appearance or finish, when the only aim is to show the principle works.
- Treating a success on one lucky trial as enough, without repeating it.