The advantages of going through a POC (Proof of concept) before launching a large scale DAM project
You may be convinced of the pertinence of implementing a DAM (Digital Asset Management) solution in your organization. However, you are about to undertake a large-scale project which will require the involvement of many individuals and departments. You need success guarantees.
How do you make sure you choose the best software partner to support you? How can you be sure that your project is not going to end up blowing the budget?
Take a page from the playbook used by the Orange Group, La Redoute or Valeo Service by doing a POC!
What is a POC?
A POC or Proof of Concept is a demonstration of feasibility. It is the implementation of a solution, usually a partial one limited to a small scope. Its goal is to ensure that what you want to implement is possible with the intended solution.
Originally, it referred to just technical feasibility to ensure that we really managed to solve complex technical problems. Today, we might consider the acronym POC a malapropism as the term has taken on a different meaning and rather designates a prototype, a project on a limited scope, without there necessarily being a big technical challenge.
How does a POC actually work?
A POC is a very short and rather intense project, which involves the implementation of the solution on a limited scope. The most important aspects to be verified are identified and partially or completely included in the POC.
Thus, a POC DAM solution may include a data configuration, a customized portal, a partial recovery of data, an integration of the SSO (active directory), and specific strategic developments for the company (the implementation of a CDN for example).
The POC will guarantee that the solution can integrate effectively with your information system, for example (PIM, website or E-commerce site, business tools, etc.) or that the migration of assets and data from your old system is possible.
How long does a POC last?
The POC generally takes place on a schedule short enough to quickly obtain a concrete result (usually between one and six months maximum).
What is the difference between a POC and a test environment?
With a test environment, you can test the features in real conditions, with one or more users.
A POC goes further: experts support you at each stage of the project: data expert to define the best structure to optimize searches, project manager to coordinate the various stakeholders, technical expert for integration with your Information System, etc.
Your DAM contacts will study your needs, identify issues you had not necessarily considered and suggest the best solutions.
When should you avoid having a POC?
A POC is not necessary for a simple DAM project. If your needs are covered by the basic features of a DAM solution and if your project does not require any specific developments, it will be faster, easier and cheaper to directly launch your project, without going through a POC first.
This type of strategy only pays off when the scope of the DAM project is large, with complex issues to address.
What are the advantages?
The POC will help to remove all the inherent risks of a large IT project:
1. Verify the functional scope of your future solution
Choosing software on paper, after a demo or a few tests, does not always give you the opportunity to verify that the chosen software will best suit your needs. By setting up a POC, you will be able to test the possibilities and the limitations of the solution(s) you have chosen, in real conditions.
2. Ensure the reliability of your service provider
Check whether the service provider’s project management methodology is suitable for your organization. Are your contacts efficient, professional, and proactive? Is the POC schedule met? Is the solution delivered consistent with the expected result?
By implementing a POC, you ensure that your software provider is up to the task of supporting you on a large-scale project.
3. Provide management with proof of results
With the POC, you provide your decision-makers with proof of a result, one that, while partial, is concrete and measurable. This initial ROI will help you justify the cost investment of a large-scale deployment.
4. Onboard your user base
In just a few months, your users begin to see a concrete result and understand the benefits they can derive from a DAM solution. They will then be more inclined to support the project, participate in the implementation workshops and provide you with the assets they produce.
5. Reviewing the scope of your project
We see it every day at Keepeek: the scope of a DAM project can change very quickly. It is thanks to our agile methods and the flexibility of our solution that we can incorporate solutions for new issues even in the middle of a project.
Once your POC has been completed, present it to your organization: other departments might identify similar needs when witnessing more concretely what a DAM can offer. Sometimes it helps to identify other issues, leading to changes that impact implementation on a larger scale.
6. Comparing before you commit
If you can afford it, you can launch a POC on two separate solutions. This will allow you to compare all the aspects listed above: features, project management methodology, support from the users, etc.
At the end of their POC, companies such as Orange, La Redoute and Valeo Service chose Keepeek to deploy their DAM solution.
Are you ready to get started? Contact us to discuss the details of your project!