Proof of Concept
PoC
- Pronunciation
- PROOF uv KON-sept
In short
A proof of concept (PoC) is a small, quick experiment built to show that an idea or technology can work in practice before investing in building it properly.
What is a proof of concept (PoC)?
Before committing months to a new architecture, library or feature, a team can spend a few days answering the riskiest question: can we stream video to this device, will this database handle our query patterns, can the AI model extract invoice data accurately enough? A proof of concept answers that question with the minimum code needed and ignores everything else, such as polish, error handling or scale.
A good PoC starts with clear success criteria, such as "processes 1,000 documents with at least 95% accuracy" or "responds within 200 ms on our data", and a timebox. At the end, the team decides: proceed, change the approach, or stop. Stopping early is a success too, because it saves the cost of building the wrong thing.
It sits alongside related ideas. A prototype explores what a product should look like or how users interact with it; an MVP is a minimal but real product released to users to test demand; and a spike in agile teams is a timeboxed investigation similar to a technical PoC. In sales, a PoC can also mean a trial that shows a customer the product works with their systems.
A common misconception is that PoC code can simply be cleaned up and shipped. It was written fast to answer one question, often skipping tests, security and structure. Treating it as throwaway, and building the real version deliberately, avoids turning shortcuts into permanent technical debt.
Key takeaways
- A PoC is a quick experiment proving an idea can work.
- It targets the riskiest question with the least code possible.
- Clear success criteria and a timebox make it decisive.
- Prototypes test design, MVPs test demand, PoCs test feasibility.
- PoC code is usually throwaway, not the base of the product.
Readers ask
What is the difference between a PoC, a prototype and an MVP?
A PoC proves that something is technically possible. A prototype shows how a product could look and work, often without real functionality. An MVP is a minimal real product released to users to learn whether they want it.
How long should a proof of concept take?
As short as possible to answer its question, typically days to a couple of weeks. A fixed timebox helps keep it focused on feasibility rather than features.
Should PoC code go into production?
Usually not. It is written quickly without the tests, security and design production needs. Use what you learned, and rebuild the real version properly.
See also
- MVPTeams & Process, p. 13An MVP is the simplest version of a product that real users can use, built to test a key assumption and learn as much as possible with the least effort.
- SpikeTeams & Process, p. 25A spike is a short, timeboxed investigation an Agile team does to answer a question or reduce uncertainty before committing to build a feature.
- TimeboxingTeams & Process, p. 29Timeboxing is setting a fixed maximum time for an activity in advance and stopping when it runs out, keeping work focused and forcing decisions about scope.
- Technical DebtSoftware Architecture, p. 45Technical debt is the future cost of extra work created when developers choose a quick or limited solution now instead of a better approach that takes longer.
- AgileTeams & Process, p. 2Agile is an approach to software development that delivers working software in small, frequent increments and adjusts plans based on regular feedback.
- User StoryTeams & Process, p. 30A user story is a short, plain-language description of a feature told from the user's point of view, explaining who wants it, what they want, and why.
Spotted a mistake or something missing on this page?Suggest an edit