What is a proof of concept in digital product development?
Innovative digital products often rely on new ideas. Creating a proof of concept can help ensure your design and development process is viable and on the right track before it even begins. This article answers the question of what is a proof of concept in design and product development, including clarifying how a POC is different to a prototype or minimum viable product. Not every digital product development project will benefit from a proof of concept, but sometimes it’s a must. Read on to find out why.
Table of contents
What is a proof of concept in UX design and product development?
The phrase ‘proof of concept’ exists in various fields and industries, and its meaning varies depending on the context. However, in full cycle product development, a proof of concept (POC) is a way of checking whether your software or digital product idea is possible and verifying if the idea will work as it’s intended to. It doesn’t test whether it should be done; instead, the focus is on whether it can be done.
Creating a POC is a method to test a concept’s practical viability. “Will it function?” is the key question.
Not every digital product in development needs a proof of concept. For those that do, the POC often comes early in the product development process (after all, there’s little point in designing, building, or testing user needs if the idea won’t even work). However, in this sense, the word “early” relates to the life of the idea, not the product’s life.
You may have a well-established product on the market to which you’re looking to add new functionalities as part of a scaling process. If any of those new functionalities are genuinely new ideas or concepts, a proof of concept can be beneficial before you go any further.
What is NOT a proof of concept in UX design and product development?
Sometimes it helps clarify what something is by looking at what it isn’t. To that end, a proof of concept is not:
- a version of the product,
- a prototype,
- a minimum viable product (or MVP),
- a method of exploring market demand,
- a way of clarifying or validating user needs,
- a test of whether the idea or concept is a good one,
- an indicator of the right design or production method for the product.
How does a proof of concept differ from a prototype or MVP?
Prototypes and MVPs are either versions or partial iterations of the product you’re developing. Prototypes and MVPs are not proofs of concept. People often confuse these three terms, so let’s create a little clarity…
Different uses
A proof of concept has a distinct goal. It tests a product or feature’s technical possibility. A prototype tests the appeal of that product or feature with stakeholders (maybe users, maybe a client, maybe investors…) An MVP tests elements of your design: you know the idea can be built but you need to test whether building the way you intend to will appeal.
Different timing
As a basic principle, a proof of concept comes first, before the prototype and/or the MVP. It’s possible to create a POC at any point of the software development life cycle – you may by adding or radically updating features on an existing product. But, in the development of a specific feature or function, the proof of concept comes before the prototype or MVP.
To reiterate:
- A proof of concept answers the question, “Is it possible to develop this idea?”
- A prototype answers the question, “Is this idea a good one?”
- An MVP answers the question, “Are we developing this idea in the right direction for users?”
The benefits of PoC in UX design and product development
In essence, a proof of concept is a test. Like any test, it gathers or generates information (in the case of a POC, information about technical feasibility) with the aim of reducing risk, and saving time and money. If the idea or concept is genuinely new or untried, then creating a POC confirms it is possible (or not!) before you invest time, effort, and expense in creating a prototype or MVP. A proof of concept helps avoid unnecessary development.
The results of building a proof of concept are not always simple – you do not always get a simple ‘yes’ or ‘no’ answer. The idea may be technically possible but come with difficulties or particular development challenges. Perhaps the POC flags up some potential logistical difficulties that will arise later in production. Perhaps the idea is possible but you don’t have the necessary skills in-house to realize it in a full-blown product. A proof of concept can identify practical difficulties that must be addressed or worked around.
With investors in mind, a POC can be used to reassure potential backers that the basic technical challenges of the product can be surmounted. A successful proof of concept can reassure stakeholders that it’s worth proceeding to the next stage – perhaps a prototype to validate the business idea with users.
It’s also worth mentioning that although it is not a POC’s main purpose, creating a proof of concept can sometimes give you insights into how the product fits the overall business strategy, organizational goals, or other business requirements. Call it a bonus, or a positive side effect!
Developing a proof of concept
Naturally, how you approach creating a proof of concept depends on what it is you’re testing or trying to prove. Your POC plan is also influenced by issues such as the anticipated product’s intended use and users.
As a basic framework, any plan for a proof of concept should include:
- Discussion and agreement of what the proof of concept is aiming to test.
- Clearly defined success criteria.
- A method of evaluating success - including proper metrics that will allow evaluation of results.
- A potential next stage of development for when (or if) the POC is successful - when the POC is ready, and evaluated positively, we can decide what to do next - move to the next appropriate phase of the FCPD by creating a prototype or MVP, or implement the solution as part of another FCPD phase (such as ensuring product-market fit or scaling the feature in an existing product).
Proving your concept
If you think your digital product depends on a new idea or a new way of executing an established idea, then creating a proof of concept is likely to be a good strategy.
A POC in UX design and product development is the low-investment, low-commitment method of testing your potential product. If the result is negative, you can reconsider, re-ideate, and pivot. If the result is positive, you can move ahead with greater confidence all round.
A proof of concept is a tool that aids rational and evidence-based decision-making at critical stages of digital product development, saving you time and money in the process, and increasing the likelihood of a successful final product.
Share this article:
