PoC, prototype or MVP: choose the question first
A proof of concept, a prototype and an MVP answer different questions. Choosing the wrong one can produce an impressive demonstration without reducing the uncertainty that matters.
A PoC tests a technical question
Use a proof of concept when the unknown is whether an approach works under relevant conditions. For example, can an external service return the records you need with the permissions available to the application?
Write down the test conditions and success criterion first. Use representative inputs and record shortcuts. A successful API request does not establish error handling, monitoring, maintainability or readiness for production.
A prototype tests an interaction
A clickable prototype lets people try a task before the team implements it. Watch where they hesitate, what they expect a control to do and which information is missing. Test the task rather than asking whether they like the design.
Use the result to change the flow or clarify the behavior. A polished prototype does not, by itself, show that anyone will adopt or pay for the product.
An MVP puts a limited product into use
An MVP needs a defined audience and a complete first task. It can leave features for later, but it still needs the access, reliability and support required for that task. Decide which usage and business evidence will justify another release.
End the experiment with a decision
Record what worked, what failed and what remains unknown. The next step may be implementation, a narrower test or stopping that direction. Our discovery, design and MVP work start with the question the activity needs to answer.
