Proof of Concept

With the advent of new technologies, many organizations are embarking on proof of concept projects to learn and explore new capabilities, and conduct feasibility assessments of proposed concepts. A proof of concept (POC) is an important first step in cultivating business innovations.

A proof of concept is a scoped, time-bound exercise with specific, measurable goals and metrics of success. Ideally, it should have some basis in business reality so that the results are meaningful.

High Level POC Architecture

Keep in mind that you are developing a proof of concept to validate whether a concept is feasible. Therefore, in order to keep the goal of your project achievable within your well-scoped timeline, when you create your high-level architecture, you must decide which essential components will be part of the proof of concept and which non-essential components should be excluded from it.

As a rule of thumb, the more components you include in your proof of concept, the more complicated your project will become and the longer it will be for you to achieve your success criteria.

There is no need to be perfect. It is tempting to try and architect a perfect proof of concept, which will mirror the eventual product if it is rolled out to production. However, for a proof of concept project, this would be counterproductive. The closer you attempt to get to perfection, the more time and effort you will have to exert from start to finish. That would be undesirable. As you recall, the purpose of the proof of concept is to quickly prove a certain well-scoped concept. It is to allow you to make the correct decisions in a timely manner. Therefore, the focus of the should always be on selecting the smallest essential dependencies and associated workloads that meet specific measurable goals, to help guarantee a
swift victory.

Building POC Team

For a small one-off, simple, non-critical experimental proof of concept, a one-person team might suffice. However, for most typical proof of concept projects where the results are critical and could influence the decision of a bigger project, you should identify the mandatory team members needed and the commitment required to support your proof of concept. The team that you are assembling must reflect the scope of your project.

With the goal, timeline, budget, and scope defined and your team assembled, you can begin implementing your proof of concept project based on the high-level architecture. To maximize execution success, follow modern DevOps processes with iterative development and testing throughout your implementation.

POC Success and Failure

If your proof of concept is successful, present your successful results to key stakeholders.

When presenting to key decision makers about your successful proof of concept, try to extrapolate financial success to business return on investment. Here are some examples:

  • Our proof of concept demonstrated that we can save USD X per month in Azure spending due to the optimization in the new implementation. We recommend implementing this concept in production.

  • Customers have been asking for this new functionality, which has proven to be successful in the proof of concept. If we implement this concept in Azure, we estimate that revenue will grow by X% per quarter.

If your proof of concept failed, there are two possible decisions:

    • Retry the proof of concept by redefining the goal, timeline and budget, scope, and architecture.

    • Conduct a post-mortem review on the failure to see if there is any insights or lessons learned during the proof of concept.

OUR POC Approach

Business & Financial

Plan your POC in terms of the business goals with a pre-detemined financial investment and budget. Save 10x compared to the big 4 consulting companies.

Global TimeZone

We can help with POCs in North America, Europe, Middle-East and Asia-Pacific guaranteeing same time-zone staff to be part of the POC team.

Dashboard Ready

Our POCs are between 4-12 weeks long and include all the key aspects to provide dashboard ready results within that stringent timeframe.

Mobility Optimized

Design for mobility is a key design pillar of our POCs enabling you to be ready with mobility optimized end-user experience in the roll out.

Community Management

Many POCs fail due to lack of the stakeholder and community participation. Our POC methodology guarantee community participation.

Data-Driven Decisions

At every stage in the POC, the decisions we make together will be based on data. Taking this approach enables fast progress and convincing results.

Trending POC Areas

Serverless Apps
Intelligent Chatbots
Cloud Migration
Intelligent Edge
Industrial IoT
Hybrid Storage