Proof of Concept vs Prototype

How often have you been asked to create a POC and reflexively cringed?   Your reaction is most likely due to lack of clarity around the desired result.  Proof of concept and prototype are often used interchangeably, but have different implications on the scope of work.  

proof of con·cept

noun
​evidence, typically derived from an experiment or pilot project, which demonstrates that a design concept, business proposal, etc., is feasible.​

A proof of concept is focused on proving the viability of a principle idea in the context of a larger system.  Technical knowledge is the primary outcome, while user interaction and design elements are typically out of scope or limited.  As the product progresses, learnings from a proof of concept may be applied to a prototype.

pro·to·type  /ˈprōdəˌtīp/

noun
​a first, typical or preliminary model of something, especially a machine, from which other forms are developed or copied.

A prototype is an working set of features intended to demonstrate how a consumer would interact with a product, gather feedback and generate interest.  Prototypes can be low fidelity, but they present an end-to-end concept of a user goal including design and  navigation.  The outcome of a prototype may be used to refine the product or feature.

The key difference between a proof of concept and a prototype is a proof of concept demonstrates a concept is possible while a prototype demonstrates how it may be executed.  Both are important tools to inform product decisions while using development resources efficiently.