1. Preparation phase
-
Set up the NDA: Aim for one or two pages in which both parties agree to work together in confidentiality. The goal is to build trust while also allowing the project to move quickly.
-
Work on the project scope definition: This step represents a major foundation for ensuring the PoC provides value. In short, it involves devising a clear outline of its objectives and deliverables. It’s important to be as specific as possible: the PoC shouldn’t try to solve all of the company’s problems but focus on one issue at a time. More on this below in this article.
-
Define success criteria: Alongside the scope, take time to set clear, measurable indicators of what success looks like. These criteria will serve as the benchmark during the validation phase and help determine whether the PoC was effective, worth pursuing, or requires iteration. Align success metrics with the business need the PoC is meant to address — whether that’s time saved, cost reduced, accuracy improved, or any other relevant value.
-
Establish the project plan definition: This document determines the timelines, resources, and specific tasks that will be activated as part of the proof of concept. It’s yet another key preparation step, as it allows all involved parties to set priorities, have resources ready when needed, and not drain them. Set flexible timelines and adopt a continuous validation approach so that adjustments to the planning can be made during implementation.
The CIO Innovation Index found that the typical timeline of a PoC is longer than three months. However, shorter timelines are usually more capable of gathering momentum. At Plug and Play, we can mention proof of concept examples that are weeks long, so a typical timeline is reaching the wrap-up in week 11.
Companies should ensure the “people side” is ready during this process. For this, consider the following typical team profile for PoC projects:
To facilitate this stage, the Plug and Play Innovation Checklist is worth reviewing. This tool analyzes an organization’s readiness to engage with startups in PoC or pilot initiatives.
-
Plan the test environment: This step involves considering what type of testing environment is needed (will you need a sandbox or a certain location? Are you testing it on the startup’s or the company’s side?) and ensuring it is ready for the PoC.
-
Budget: Ensure the PoC is presented with a budget that sets the right conditions for success, including its alignment with the set timelines. Additionally, whether financing comes from the innovation department or the relevant Business Unit, the budget’s origin should be considered to align the PoC with the department’s expectations.
Once the above are aligned, it’s time to move into the contract phase, where both parties formalize the terms and ensure legal protection. Again, keeping the contract as simple as possible is advisable to avoid disrupting the project’s rhythm.
2. Execution phase
It’s time for the proof of concept to be set in motion.
Start with a kick-off meeting involving all stakeholders, and aspects such as timelines and ‘who’s doing what’ are determined.
Keep in mind the goal is to see if the project really fits the business’ needs. To do so, data is your best ally. For every test you run, you should be collecting data. This is a crucial best practice to help organizations keep an eye on the next stage: validation.
As a wrap-up for execution, collect all data and gather teams in order to:
-
Understand the results, simplifying complex data through tools like charts, and converting it to valuable, actionable insights
-
Create a demo
-
Present the PoC results involving the business unit and management to gather support for the project and innovation opportunities.
3. Validation phase
It’s time to evaluate whether the PoC successfully met its goals. Compare the real-life, data-based results to the project scope while reflecting on potential market interest.
At this stage, all involved can learn about the innovation’s benefits: Are we getting an ROI? Does it lower costs? Does it help attract new customers?
Based on these insights and together with management, it’s now time to decide what comes next. The outcomes of PoCs can be multiple:
-
Rejection: After running a PoC, the company may find arguments to label the technology as uninteresting to meet their needs. This common scenario must be acknowledged from the beginning as part of managing expectations. In fact, as a reference, the CIO Innovation Index cited above found that 61% of CIOs mentioned how “less than a third of their PoCs convert into productive implementations and purchase of the startup’s technology.”
This doesn’t mean the proof of concept was unsuccessful: it allowed the company to try a new idea in a fast-test environment with low risk while potentially uncovering other needs and opportunities.
-
Iteration: Another outcome could be establishing the need to try a different testing approach. In this scenario, the process is activated repeatedly but from a different perspective (e.g., a different scope, a different environment).
-
Investment: The company might discover that, while the technology is not the right fit for their needs, it still has great potential in the market. As such, the PoC can open a new business opportunity for the company.
-
Ready for implementation: In this case, the testing has proven its value for the company, which is ready to explore it further. Again, there are several formulas for this: while buying the technology and acquiring the startup are valid approaches, a common strategy is to develop a long-term corporate-startup partnership, where both parties continue taking the next steps together.
4 common pitfalls to avoid in the PoC phase
1. Straying from core principles
It’s key to focus on the PoC as a tool to test viability, not as a strategy for designing a complete solution. If approached from the latter perspective, the project typically involves introducing unnecessary complexities that make the PoC more complex and less agile, ultimately diverting resources from the core goals.
Examples of this problem include adding extra features to the PoC or trying to build an overly sophisticated solution. Instead, ensure the project doesn’t lose sight of the essential features that need validation.
2. A vague project scope
By expanding the project scope, the proof of concept often results in a diluted focus that cascades into issues such as delays and increased costs, largely contradicting its aims.
As mentioned above, the project scope should be as granular as possible. Understand that the goal of the PoC is not to solve every problem or provide answers to broad questions, but to test a particular and tailored solution for a specific issue.
3. Poor data collection
Not collecting data during testing prevents us from fully assessing the PoC’s value.
Poor data collection can happen for various reasons: Some might see data collecting as a delay; others might underestimate the need for data (a type of ‘if it works, it works’ mentality). Another scenario involves collecting data, but data that is irrelevant due to a lack of well-defined metrics for success in the preparation stage.
The lack of valuable data implies difficulties in proving the PoC’s value, thus making it more difficult to secure investment or move on to production. But that’s not all: data provides insights not only on whether the innovation works but also on how it works. As such, missing out on data means missing out on a number of useful learnings for moving on.
To avoid this issue, start at the preparation phase: ensure the PoC has measurable success metrics and that the resources are there to collect data during execution.
4. Neglecting the validation phase
The validation stage is largely the step where companies can extract the main value from the proof of concept, so it is a mistake not to understand its importance and provide it with the right space.
In fact, even if the project is not continued, it’s at the validation stage, where the PoC can be activated as a learning opportunity.
Again, the validation phase allows a full circle moment, returning to the PoC’s central premise: establishing whether an innovation is valuable or not.
Looking to start your own innovation journey? At Plug and Play, we can help you.
Practice the art of corporate innovation through our training sessions designed by our experts, or talk to our innovation experts directly and discover how we can help you achieve innovation success.