“The proof is in the pudding”, was my customers endorsement of my decision to proceed with a proof of concept (POC). As discussed in my previous article “Proof is in the pudding!”.
A proof of concept tests key elements of a solution in a simulated environment that mirrors a proposed operational environment. It typically occurs early on in the lifecycle, certainly before a pilot.
PC Magazines Encyclopaedia of Terms defines POC as “The evidence that a product, technology or an information system is viable and capable of solving an organization’s particular problem. A proof of concept is often developed for new products that have not yet come to market. Evidence which establishes that an idea, invention, process, or business model is feasible.” Whereas Businessdictionary.com defines POC as “A proof of concept is a short and/or incomplete realization of a certain method or idea(s) to demonstrate its feasibility. The proof of concept is usually considered a milestone on the way of a fully functioning prototype. These proofs of concept demonstrated ways for the team to accomplish difficult technical tasks, or proved that a particular creative concept “worked” (or didn’t work).” Hopefully you get the idea.
Basically a POC tests the viability of the concept, idea, technology. What one is about to embark on is uncertain, until it has been tested directly. As it is unproven then there is uncertainty as to the outcome of the POC and the project as a whole.
A POC is a common idea in the business world. It can equate to a feasibility study, but focuses on the evaluation and analysis of a specific area of a project or venture.
In the field of new businesses; entrepreneurs and start-ups frequently use POCs to demonstrate that a new venture, product or service is viable.
In the field of engineering and industrial design; rough prototypes of new ideas are constructed to prove conceptual ideas. In car design, life-size prototypes are manufactured. These concept vehicles are made to showcase new styling and/or new technologies and are often used to gauge customer reaction.
In the field of filmmaking; POCs are routinely used to test new techniques. Pixar has a history of creating short animated films that use unproven or untried techniques, such as “new techniques for water motion, sea anemone tentacles, and a slowly appearing whale in preparation for the production of Finding Nemo”. POCs give an opportunity perform early validation, such as 1) demonstrate the capabilities of something in a controlled manner, 2) demonstrate whether something is appropriate for use, 3) perform analysis on optional solutions, 4) resolve alternative solutions, 5) serve to inform without large investments.
Prior to execution of the POC, the success criteria relevant to outcomes of the project must be identified. Additionally the stages necessary to achieve the criteria must be clearly defined (plus explicit identification of those project requirements being tested, plus those excluded).
What is important about POCs is that they afford an excellent risk mitigation strategy. POCs help risks to be identified, mitigation plans to be formulated and evaluated ahead of time. Of course, when risks are realised during the POC, then shifts in project approach and/or changes to the overall project can be made earlier ion in the project.
As discussed in my previous article, using a POC to assess the viability of implementing unproven software is a good case of risk mitigation. Obviously any credible project manager would identify this as a risk and manage accordingly. The POC just proved it earlier in the project.
Interestingly, one aspect I uncovered during the POC was the need to develop new skills within the organisation. Earlier on in the project there was an understanding (and resounding belief) that there already existed sufficient skilled individuals, who possessed not only the requisite knowledge BUT the necessary experience to perform the crucial activities in the project. Executing the POC proved that this was not the case. The organisation therefore needed to acquire those skilled individuals before any actual implementation was performed.
When exploring lessons learned and “best practices” I hope future project managers utilise the POC approach to assess whether their solutions should be deployed.
I hope this article illustrates how POCs can help projects succeed in the real world. I would love to learn more, so please share your experiences.
NOTE: A “pilot” refers to an initial roll out of a system into production. The purpose of a pilot project is to test, often in a live environment, whether the system works as intended while limiting the extent of the exposure to the organisation. It may have limited scope compared to that of the final agreed solution (with functions disabled). It is typically limited by other factors, such as the number of users who can access the system.