Carrying out a POC feedback (proof of concept or proof of concept) is a must for check the feasibility of implementing a solution, Mobile learning for example, enterprise-wide. In particular, it allows you to learn what areas need to be improved before taking the plunge. So how do you carry out and manage this feedback? We're taking stock!
What is a proof of concept?
Startups and innovative businesses are quite familiar with the acronym POC. In simple terms, The purpose of this proof of concept is to demonstrate the feasibility of an idea, product or solution, well in advance of its deployment. In a sense, it is a preliminary stage in the development of a product, a prototyping that allows the future of the solution to be framed. Very often, the POC is a tool that promotes the establishment of a dialogue between the startup or innovative company and its client. For the smooth running of a POC, it is particularly important that both parties are clear about their expectations. This means a clear definition of operational objectives, in particular expectations in terms of skills development or productivity in the context of training. The POC is therefore a guide, which will help define, identify and frame the course of future collaboration.
What should we remember?
1 - The POC is an essential step in the implementation of an innovative project, such as the digitalization of training. Its purpose is to demonstrate the feasibility of an idea, a product or a solution, prior to its prototyping and deployment.
2 - It is a tool that promotes the establishment of a dialogue between the startup or innovative company and its client, a guide that will help define and frame the progress of future collaboration.
Who carries out the REX and when: good practices
Generally, the proof of concept is managed jointly by the two parties, which therefore constitute a steering committee, itself generally made up of project managers and training project managers or training managers. Continually, the feedback from POC is also carried out jointly. It allows, at the end of the proof of concept, to check whether the objectives were achieved, whether the resources were sufficient and adapted, what are the points of improvement, the quality of the relationship between the two parties or even user feedback. In general, feedback has two main parts and is in the form of an evaluation grid to be completed or simply a written report.
What should we remember?
1 - The proof of concept is jointly managed by both parties, as is the feedback
2 - Feedback makes it possible to verify whether the objectives were achieved, whether the resources were sufficient and adapted and to make improvements to the project
REX part 1: Project definition
In this part of the feedback, it is a question of asking all the information relating to the project. We need to find out who is responsible for the training project. (training project manager, training manager, etc.), It also contains a detailed summary of the project concerned, its objectives, its target, the main problems identified, etc.. In this first part, it is also necessary to carry out an inventory of the existing situation, for example by returning the audit results if there were any. Finally, this part contains the details of the solution tested in the proof of concept, the implementation and the progress of the project.
What should we remember?
1 - The first part of the feedback lays the foundations of the project, it contains all the information relating to project management and the proposed solution
2 - It is also in this part that we find the inventory of the existing situation before the project
REX part 2: The observations
This part is an essential step in the feedback from POC, it must contain all the elements of observation that make it possible to validate the hypotheses envisaged for the solution, or to make adjustments. In this part, there is a stage dedicated to evaluating the relevance of the POC, its effectiveness, as well as its impact and sustainability. Secondly, a list of indicators makes it possible to identify the strengths and weaknesses as well as all the difficulties encountered by all actors, including users.
What should we remember?
1 - Step 2 of the feedback contains all the observation elements collected with the POC
2 - A list of indicators makes it possible to pinpoint the strengths and weaknesses as well as all the difficulties encountered
REX part 3: Lessons to be learned
No POC feedback would be complete without this part, dedicated to analysis. According to the observations collected in part 2, an analysis will make it possible to determine the causes of possible frictions or malfunctions in order to determine the appropriate responses. But this section doesn't just talk about the problems that need to be addressed: it also discusses the strengths of the POC as well as the elements it contains that need to be capitalized on. In conclusion, this part contains the lessons to be learned from this POC as well as the adjustments to be made in order to adjust a solution exactly adapted to the needs of the company.
What should we remember?
1 - The third part of the feedback contains the analysis of the observations and problems encountered, in order to adjust the proposed solution
2 - It also contains the strengths of the POC and the elements on which to capitalize
