How is a proof of concept or an implementation of Anjana Data?

At Anjana Data, we aim to minimise time-to-market and time-to-value in the proof of concept or implementation of our data governance solution and to be able to demonstrate a real return on investment in a very short time.

We have suffered it in our own flesh many times throughout our professional career: acquisition of technology with huge initial investments, implementation plans with gigantic projects, hordes of consultants to configure and test that technology... and then, when you have to give the go-ahead for the switch to production, after many comings and goings, replanning and budgetary adjustments, the results are not as expected, nobody assumes responsibility and then the whole strategy is rethought.

For this reason, at Anjana Data we do not believe in this model of huge implementations that extend over time and seek a Big Bang that is very difficult to manage. On the contrary, we advocate pilots and implementation plans based on the same philosophy of agile methodologies, seeking to demonstrate real value in a very short time.

Furthermore, in order to demonstrate this real value, the implementation of Anjana Data is not limited to the technical tasks necessary to implement the solution, but we seek to cover the entire process, from the analysis of the need to the realisation of a first use case in production that allows us to obtain the first measurable results.

So how do we conduct a proof of concept at Anjana Data?

First of all, we try to understand as best as possible the customer's needs and their main pain points, and we start working together with them on a proposal to use Anjana Data tailored to their requirements, normally offering different alternative configurations and uses of the solution within the capabilities of Anjana Data.

Then, with the aim of drawing up a detailed work plan with defined activities, milestones and deadlines, we try to narrow down and define as best as possible the implementation scenario, also identifying a series of success metrics that can demonstrate quantifiably what has been achieved and the value achieved.

To achieve this goal, we follow a series of steps that can be grouped into the following blocks:

1.- We selected a case of limited application.

A use case or use case diagram is what is commonly understood as the description of the activities that someone or something must perform to carry out some process.

In this context, within this first point, we must select a use case where Anjana Data covers the identified needs and its incorporation into the technological stack represents a differential added value. The detailed description of the use case is very important because it will allow us to define the scope of the initial implementation and we will be able to measure what we have achieved to sell it internally.

Here are some examples of use cases:

• A specific information domain, for example customer contactability data or financial data related to contracts.

• A specific data initiative or project, for example the creation of a sandbox for advanced analytics or the creation of an MDM of product data.

• A regulatory case, for example related to GDPR or RDA.

• An end-to-end information exploitation process such as the generation of a recurring management report or the generation of the income statement.

• A specific technological environment such as a Data Lake, a Cloud environment or an Analytics area.

There is no single use case that is better than another; the selection of the use case will depend entirely on the needs of the organisation, the importance it may have for senior management, the complexity of its execution or the ease of involving stakeholders, among other variables.

2.- We define the technological scenario involved.

Based on the chosen use case, it is important to delimit the technological scenario involved in this use case, since the more delimited the proposed and fewer technologies involved, the less complexity we will incorporate into the initial implementation plan.

One of Anjana Data's distinguishing features is its extensive native integration with other technologies to incorporate the data governance solution as the central axis of the data ecosystem. This makes this point particularly delicate, and it is very important not to fall into the trap of trying to cover too many technologies in the initial phase, because there are many aspects of technological integration that can complicate and delay the pilot or implementation plan.

Among these, it is important to identify the following technologies: Repositories for data storage. 

• Systems for processing data. 
• ETLs and data services. 
• Exploitation tools and BI. 
• Systems for managing identities. 
• Systems for managing permits.

3.- We identified the key stakeholders.

At this point, the people involved must feel empowered to make decisions and see themselves as part of the process of change that is about to take place in the Organisation, perceiving the value of it and in turn, taking on a number of responsibilities around the data they may not have had until now.

It is very important to make stakeholders See that the governance of data does not consist of «putting sticks in the wheels» or «playing bad cop». It is about equipping the organisation with the necessary skills to generate value for the business through better use and processing of data. It is essential to provide them with the necessary tools and resources, because without them, their workload will increase and they will not see a quick return.

That is why during the pilot or implementation plan of Anjana Data it will be necessary to work on training and change management with the different stakeholders identified.

4.- We define the success metrics.

Success metrics will help us to demonstrate quantitatively what has been done and the value achieved. These metrics will also depend on the selected use case, but as a general rule we can classify them into the following groups:

• Reuse of data. 
• Satisfaction of the stakeholders. 
• Cost savings. 
• Improved efficiency and productivity. 
• Reduction of operational risk. 
• Regulatory compliance (if applicable). 
• Data monetisation (if applicable).

The Anjana Data pilot or implementation plan

With all this in mind, we outline a project plan with a specific duration (approximately three months), which is agreed upon with the client before commencement. This plan typically includes the following activities:

• Assessment of infrastructure and architecture and proposal of technical design. 
• Deployment of all services according to the chosen deployment model and configuration of connections with the client's systems. 
• Implementation of the selected use case and support in defining the configuration of Anjana Data to meet the customer's needs (governance model and metamodel). 
• Configuration of Anjana Data as defined. 
• Training and change management sessions. 
• Support during the initial stages of information gathering, functional testing, and execution of the use case. 
• Review of success metrics and generation of conclusions.

And what do we gain from this way of working?

Thanks to this approach, not only do we manage to minimise time-to-market and time-to-value in the implementation of our data governance solution, but this also allows us to demonstrate a real return on investment in a very short period of time.

On the other hand, we managed to empower both the organisation and the stakeholders so that they can evolve in their implementation of data governance according to their needs and requirements and so that they can also extend the coverage of Anjana Data to more independent use cases, resulting in a reduction to the maximum of the dreaded vendor lock-in, from which we try to flee as much as possible.

Furthermore, we always certify the implementations of Anjana Data, and until certification is granted, the licences for use of the solution do not become valid. This represents our commitment to our customers and our confidence that Anjana Data meets expectations and fulfils identified needs.