Collibra Platform Reviews

Collibra Governance is used as a data governance tool to manage your business metadata and technical metadata from various systems. Customers also use the tool to provide a data cataloging option, create a data lineage, and automate some of the business processes.

The solution's most valuable feature is data cataloging. The solution's data cataloging feature is mainly used for data discovery. Nowadays, data cataloging enables the data marketplace to share data within enterprises. That's another enablement that Collibra Governance does.

When you have a huge amount of hierarchical data to manage, the solution's performance tends to decrease.

I have been using Collibra Governance for six to seven years.

Sometimes, when we face an issue, we resolve it by ourselves. On other occasions, we contact the solution's technical support team. I wouldn't say that the technical support is excellent. The support team struggles to resolve the issues 60% of the time. However, they are able to resolve issues the remaining 40% of the time.

Many of our customers I spoke to felt that the solution is a bit highly-priced.

I sometimes recommend Collibra Governance to our customers based on their requirements and environment. Most customers look forward to having a data lineage function, but I haven't seen any tool that satisfies the customer requirements, including Collibra Governance.

The solution has primarily enabled some of the compliance reporting through data lineage reporting. When you have data cataloging with complete metadata enrichment and identification of PII and non-PII, it helps customers control and manage them properly.

If a customer does not have the appetite to procure Collibra Governance because of the pricing models, we may recommend a different product with cheaper prices. Collibra is working on building a new product for AI governance. I want to see how Collibra's data governance and AI governance will relate to each other.

Most of the customers we deal with are looking for a tool to resolve the data lineage challenge. However, none of the products in the market seem to be resolving the customers' data lineage issues. Vendors like Collibra, Alation, and Informatica could work on it and provide a more comprehensible solution to the customer.

Overall, I rate the solution an eight out of ten.

We use the solution's Data Stewardship part. We tried to explore the policy management piece, but we were unable to get through it. We haven't worked excessively on that. It was just some POCs or MVPs, but this is something that we would like to explore in the future. This is something that will be our future requirement in six to seven months down the line.

We use the solution's Data Stewardship part.

We are not able to ingest all the data in Collibra, and that's why we cannot do element-to-element level data tracking.

I have been using Collibra Governance for two years.

I rate the solution's initial setup as medium because it's not very difficult. We have to look at a few nuances from the infrastructure and performance perspectives. We have to consider whether we would have the leverage capabilities for that. So, all these things need to be considered from the engineering side.

Collibra Governance is an expensive solution.

Our current focus is more on the solution's stewardship, cataloging, and reference data features. The one feature of Collibra Governance we would like to explore is the automated tagging of PII data. We do deal with such kinds of data within our organization. It would be helpful if there were any videos available for us to go through because this is something that will help us in the near future.

We are not extensively using the solution's data lineage functionality because we are simply building over it. The only challenge for us is from the connective side. We are not able to ingest all the data in Collibra, and that's why we cannot do element-to-element level data tracking.

The major Broadlock would be the integration piece. If that is done, we'll be able to have all our data in the Collibra. The data lineage functionality is a really good feature, and we would really love to leverage it. The challenge is that the connectors are not available in the pipeline.

Collibra Governance is deployed on the cloud in our organization.

Overall, I rate the solution a seven out of ten.

We've used it for cataloging or defining our business data entities and their associated attributes or data elements. Where appropriate, we are defining their sources and their modes of derivation. Rising above that, we are also using Collibra for the definition of our business metrics that are calculated from those data elements and the derivation definitions associated with them.

We have folks in the field doing our clinical research operations, and they have the opportunity to refer to Collibra when they are examining a particular report. When they have a question about how something in that report is derived, they can pull a metric that is defined fully in Collibra. They have the opportunity to drill back into Collibra to see that.

It is a big library. It has a long list of data assets and their descriptions and lineage. It's fairly two-dimensional. For my use, it just has lists of things. There might be others in my organization who are tying the data elements, metrics, and other things together, but I don't rely on that, and I don't leverage that. For me, it is a fairly flat library for information.

What I use it for is fairly rudimentary, and I don't have any complaints about it. I haven't tried to stretch the boundaries at all, but it would be nice if there were capabilities built within the system to somehow help enforce the quality and consistency across related elements that are built in the catalog. It could have intelligent capabilities built in to help maintain the quality of the data and information, such as natural language processing, machine learning, and so on. 

I've been exposed to it for about seven years, but I have been using it more heavily over the past couple of years.

I've not seen or heard of any problems with its stability.

I haven't seen any impediments there. So, I have no concerns about scalability. It could be because I haven't been this involved in pushing the boundaries, but I've seen it accommodate new layers without hearing of any issues.

It is open to everybody in our organization. We have more than a thousand users. So, there are more than a thousand people out there who have lately used Collibra, but most of them have used it in the reference mode or read-only mode. In terms of their roles, we've got everybody from data engineers, data analysts, and systems developers to business analysts and business end-users. 

I've never called them, and I don't hear anybody complaining about it.

As far as I know, this was our first venture about seven years ago into data cataloging and data governance.

I wasn't involved in the setup, but I can see that the maintenance of information within the system is quite straightforward.

My guess would be that we took care of most of the things in-house.

I'm only involved in the use of it. My advice would be to make sure that the content is of quality because it tends to mushroom into lots and lots of information that can easily get out of sync. It should only be entered into by an organization that has the discipline behind it to maintain the information at a high level of quality. Otherwise, you end up with a lot of information that seems useful, but in effect, it could be more harmful than it's worth if things get out of sync. It takes an organization to maintain this kind of solution. The content is dependent on the quality of the maintenance of the content.

I see a small chunk of it, and I would rate it an eight out of ten.

We use the product for classification based on the different regulations and compliance requirements.

The platform is customizable. In comparison, Informatica Axon has predefined facets. Meanwhile, Collibra lets us create custom assets. It helps us build a powerful workflow mechanism where there can be any stewardship, including issue management governing assets using policies, regulations, or business rules. They are integrated very well. It has a lot of connectors with different source systems and efficient cataloging features.

There could be more integration similar to Snowflake, for instance. They do support integration, but complete lineage is not possible. Certain implementations, including lineage maps, could be user-friendly. At the moment, there needs to be more lineage between data sources. It needs improvements in terms of attribute connectivity during data transformation.

We have been using Collibra Governance for seven or eight years.

It is a stable platform.

Collibra Governance is suitable for enterprise businesses. It is a SaaS product. Thus, the end users don’t have to maintain scalability or maintenance.

The technical support team is responsive.

Positive

I have worked with Informatica Axon and Data Catalog. In comparison, Collibra has better workflow management features. I recommend it for technical usage as well. However, Axon is more user-friendly for creating lineage diagrams. It has ready-to-use templates for deployment.

The initial setup process is complicated. However, once you get good training and understanding of the system, it is very straightforward. Some of the configurations require support. It takes around a week or two to complete all the configuration for the existing ecosystem.

For Informatica, we have to buy cataloging and governance separately. Meanwhile, Collibra offers one structure for both. We purchase its annual license. There is an extra cost for additional users.

I rate Collibra Governance an eight out of ten.

I use Collibra Catalog for cataloging various reports, data elements, and tables, along with schema, associated with all the various attributes of the element itself, like business rules and sensitive data.

The most valuable features of the solution are the ability to PnP with all the various DBs in the background and to ensure that the Tableau is updated and any changes are visual while notifying about the integration to various business rules, data rules, data quality rules, and systems.

The tool's overall functionalities need to improve since, nowadays, many tools, from a business perspective, are easy to use.

I have experience with Collibra Catalog. I am an end-user of the tool. My company is a customer of the product.

Stability-wise, I rate the solution a seven out of ten.

Scalability-wise, it is a good solution. I rate the solution's scalability a seven and a half or eight out of ten.

Collibra Catalog is continuously being used in our company in as many ways as we can incorporate from various partners on the data elements and data landscaping, so we are slowly building it out.

Though unsure, I feel that the initial setup of Collibra Catalog is pretty complex over the system.

I think Collibra Catalog is one of the better products out there. The ability to PnP in the back-end and get all the updates is amazing in the solution. Collibra has its own rules engines and has incorporated other rules engines as well.

Collibra Catalog is simple to use and user-friendly for those who are not technically inclined since it is easy to find while also easy to see data lineage diagrams.

I rate the overall product an eight out of ten.

We primarily use the solution for when the customer needs data governance to establish cases. We're choosing the product in order to meet the requirements of the customer. That includes requirements such as establishing a governance council if the customer does not have one. It's for data management and the solution handles data quality and metadata management, et cetera. 

Before implementing data governance, the customer had a pain point of identifying the data and providing data useful to their business. That was the biggest challenge. There were also many data quality jobs where the customer wanted to find and identify the data in terms of where the data is sitting and who was responsible for it, et cetera. We were able to identify data sources, which applications were available within the organization, the domain level, and more to clarify exactly what was happening, where reports were sitting, who was connected to what, where data was coming from, and more. It also helps clarify job roles and showed access to identify where pain points were to get an overall picture of the data of the entire organization. 

The ability to pull together data lineage is one of the most valuable aspects of the product. 

The transparency was great. the business was able to come in and see the data and what exactly was happening in a way they couldn't before. The company could see job roles, data sources, and policies. 

The quality and visibility of the data links are great.

They used to rely on third parties, however, now, for example, they've brought in their own data quality tool. 

The beauty of the solution is that you can customize it quite a bit.

The technical support could be better.

Previously, it was a challenge to integrate tools like MuleSoft into the product. However, they've gotten better. 

There needs to be more security and compliance embedded in the product in the future. 

I've used the solution for close to seven years. 

The stability is great. I'd rate it at around a nine out of ten in terms of reliability. There are no bugs or glitches, and it doesn't crash or freeze. 

The scalability is quite good. I'd rate the ease of expansion at an 8.5 out of ten. 

We weren't overly pleased with the technical support. They need to provide a better quality of service to the customer. 

Neutral

I'm also familiar with Informatica Axon. I find that it is a little stronger in the data quality department. However, it is not as easy to deploy. 

It's not too complex to set up initially. It's pretty easy if you are doing a basic setup. However, it does depend on the client's requirements. You can customize a lot of things, which is great. 

We handled the setup ourselves in-house. I mostly did the implementation myself. I have seven years of experience and am quite comfortable with it. 

We have witnessed an ROI while using this product. The customer typically sees huge returns. 

The solution isn't overly expensive for bigger customers. Typically, the cost is handled by the customer, not me, and therefore iI can't speak of the exact pricing. 

I'm not sure which version of the solution we are on right now. We're on the cloud deployment, meaning we are likely using the latest iteration.

I'd recommend the solution to others. It's a straightforward product. 

I would rate it nine out of ten overall.  

Collibra Governance has many use cases. I'm part of the enterprise data team and I also focus on other types of data enterprise, wherein governance is one of the workstreams. I'm working for a pharmaceutical company, so I try to onboard people on Collibra Governance from various verticals such as HR, vaccines, pharma supply chain, etc. Sample use cases for the solution include data quality for cloud stream software, automated data lineage, and other types of lineage. In general, I'm using it mainly for data governance.

The feature I like most in Collibra Governance is the lineage. It lets me do lineage that you can set up, for example, technical lineage and business lineage. The solution lets me associate the right people with the right assets, so anybody who has to look at end-to-end instances can use Collibra Governance and figure it out in terms of who to contact, what to do, and where to find what you need.

There's still room for improvement in Collibra Governance. Right now, the solution focuses more on publishing and subscription where metadata is being consumed from all systems and processes within Collibra Governance. I'd like to see more features around external systems that let those systems start consuming or start referring things from Collibra Governance automatically, in particular, more API-based integrations, so the solution can truly work as an enterprise governance tool at the heart of the organization.

There have been many cases where business stakeholders feel, "Okay. I'll be doing a manual activity because every time I have to maintain and make sure that the solution is working, for example, ensuring the reporting works, I have to go to Collibra Governance." I want this step taken out of the equation, and it has to be an automatic conversion or automatic notification that something has changed.

Scalability also needs improvement in the solution.

If there could be some sort of self-service where people can customize the solution a bit more, that would make Collibra Governance better.

What I'd like to see in the next release of the solution is an enhanced search feature because it's what users want to use. You want to search for a term and get all details in one go. Right now, if you type a term in the Collibra Governance global search function, it returns a lot of results that you need to know how to filter and what to filter, so there should be automatic filters that give accurate information to somebody who does a search on the solution. I want Collibra Governance to provide a capability where you can search and get relevant information.

I've been using Collibra Governance for two years now.

Collibra Governance is a stable solution. It has no downtime or issues, based on my experience.

Collibra Governance is not a scalable solution, and this is one of its areas for improvement. The solution needs more integration, and I'm also looking at how Collibra Governance can be more scalable.

The technical support team for Collibra Governance is very responsive and knowledgeable. On a scale of one to five, I'm rating support a five. My team gets very good support from Collibra Governance whenever required.

The initial setup for Collibra Governance isn't that complex. The UI is pretty straightforward and the structure is quite standard, so people can come and map. The main problem my team is facing is working in a federated environment, so every business or every unit you've given leverage designs it their way, and in that way, people can customize a tech model, so you have no control over that. It's more of how people perceive the business, business terms, and business data that varies. I'm struggling to build more standardizations around it, but I have no solution to it yet because, in my company, you don't work like a centralized organization. People research and build designs their way, so at times, this leads to different conclusions, and that's what I'm struggling to solve.

I'd rate the setup for Collibra Governance as three out of five, though I didn't do the setup myself. Another team was responsible for setting up the solution.

I'm not familiar with the pricing or licensing cost of Collibra Governance.

I've not used any other data governance tool apart from Collibra Governance. I've used a data quantity tool, a data reference tool, and a master data management tool, but not a data governance tool similar to Collibra Governance. In my previous organization, I did governance through files, SharePoint, etc., not a centralized tool such as Collibra Governance.

In the company, there are more than three thousand users of Collibra Governance.

My team has been using the solution daily, but I'm unsure of how frequently it's used by other teams.

My rating for Collibra Governance is seven out of ten.

My company is a customer of Collibra Governance.

Previously, I was in high-tech, now I'm in healthcare. In both instances, we used this solution to increase data literacy and business literacy. In short, we were building out business glossaries, coming to an agreement on term definitions, understanding what reports mean, what the metrics and calculations mean — essentially getting it all documented in an enterprise-facing view. That was the bulk of the focus in my prior company — along with some reference data. At my current company, we are focused heavily on bringing in data dictionaries, including schema tables and columns, and understanding what data is in which database. We also look at what data is flowing from database to database and how it's used in Tableau reports or in a business or archive.

Currently, we're on-premises, but we're planning on moving to the cloud later this year.

Over the last 12 months, we've had 643 unique new users. Most of our users tend to be what I would call "data geeks". They are the ones that understand the value of and/or the aspect of leadership to catalog their metadata for their data dictionaries, etc. The business users have not had as much adoption at my current company because that's not the particular strategy at this time. At my prior company, that was the singular strategy — to increase business literacy.

In regard to my previous company, for eight years, our primary customers were business users, not technical users. They just wanted to come in and say, "What does it mean? Who do I talk to if I have questions? Where do I go for more information? How does this relate to that, and how do those things affect me in my business world?" That was a fantastic use case at my prior company. In my current company, we're utilizing the tool specifically to support our data management strategy. Our technology risk office is very much supporting us in the effort to do the cataloging of all of the metadata for all of the systems that we're utilizing, cross-functionally.

Maintenance must be defined. As with any software product that exists, there are regular maintenance upgrades that occur that the company pushes out. If you're on-prem, you can choose to do it sooner versus later. In the Cloud, they push it to you unless you state that you wish to wait. From a maintenance perspective, I have talked to other customers who are in a cloud environment. They say that the maintenance has basically dropped to nil. For on-prem customers, it does require a little more maintenance because obviously, you've got to make sure that the servers are up and running, etc. In my prior role at my previous company, I was responsible for the business IT side of it, which meant I kind of managed the platform. I just didn't manage the server.

I took care of the customers, etc. I'm not even a technical person at all, but still, it was not difficult for me. From a maintenance perspective, I don't feel that it is difficult.

If you have custom integrations that have been created, then it will require a little bit more maintenance because those integrations need to be monitored. Some customers require a lot of integration, and some customers don't. It really depends upon the use case. Custom integration is really where it gets more challenging. Depending on whether it's a one-way integration or a two-way data feed, it can get pretty complex. Two-way data feeds are always custom. But that's something that will be on the customer anyway, not Collibra.

We've only just relaunched this solution within the last 15 months. Currently, we only have about 240,000 assets in the tool, but we have a roadmap and plan to onboard a number of our customers. We'll probably double or triple our users over the next 12 months. 

This solution has brought our very diverse cross-functional business teams to one enterprise-facing view, where they can see business glossaries that have been compiled by other teams. From here, they can leverage and understand what reports have been created. If the report exists already, why recreate it? 

Our data management strategy is to start cataloging our data dictionaries and our business glossaries to ensure that we have a common platform across the company. This is helpful when a database is being retired or being converted over to another one. A lot of work goes into documenting what that data attribute means, or what that field name means in regard to a particular report, or in a particular database.

I'm always putting in enhancement requests because we want everything to be perfect for us. We understand that there are thousands of companies that use the tool and many of them use it in different ways. They should allow the customer to have some additional flexibility.

Take Microsoft for example. Sometimes companies do something cool because their software programmer thinks it's cool, but for the user experience, it stinks. Something as simple as "Why did you decrease the font size from 12, down to nine on every page? Now eyes over 40, can't read it". As it relates to this specific software, I think that getting more feedback from users on changes to the software before implementing it would increased value for them. Overall, they're really great. We meet with our Collibra rep every other week. We talk about what's working, and what's not working. They're a fantastic company to collaborate with. Still, when they just go ahead and implement new things, a bunch of new tickets open, wanting it to go back to the way it used to be. 

As far as the functionality of the tool is concerned, it's pretty slick. It's very comprehensive. Still, sometimes they create an interface or an integration without thinking about how the business is going to use it. Virtually all software companies do this. Oracle does it, Informatica does it — every tool does it. They make changes and then they're like, "Oh, I didn't know you were going to use it like that". Why? nine-tenths of their customers use it like that. I think it's a common business challenge that any company has. They're just trying to appeal to a vast audience of customers.

They should consider that what makes a financial institution happy will not necessarily make a healthcare institution happy, which will not necessarily make a high-tech vertical happy either.

There's a lot of things available in their Data Intelligence Cloud that are not available on-premise. For me, if they could boost the search functionality so that if somebody types in a word, it automatically will pull up similar terms first — that would be nice. For business users, instead of what is just the most common volume of content in your tool, now they have a very cool faceted search. It would be very similar to Amazon. You can refine your search down to a fly's eyelash if you'd like. I see a lot of people in the community commenting that this would be a big help.

I have used this solution every day for the last eight years.

It's a pretty stable tool. In the last year, we've only had one time where there was a significant issue. We found out that it was simply because during an upgrade it required more server memory than the prior version did. Overall, that was a minor hiccup and it was quickly resolved.

Collibra has roughly half a dozen different products with which you can buy additional licenses for that will do amazing things. If you're interested in GDPR, you can buy that software — a module. If you're interested in what I would call a significant data lineage, you can buy that product, get a catalog, and it's available for data ingestions automatically. In today's world, this is pretty much essential. There's a lot of capabilities as far as scalability and expanding usage across the business.

It's easy to do that if the business users are being encouraged by their management to use it. I think you might agree that no matter what company you work for, nobody's going to use the tool unless their leadership tells them to — they're comfortable in their own box. It's like, "I'm busy. Don't bother me unless I have to do something." That's the case for what we have done both at the company I'm at now and my prior company. It's that leadership gained, cross-functionally that we have as one enterprise united under one tool. That's a pretty powerful thing to encourage people to do. The implementation of a tool like Collibra is far more effective if you have leadership executive sponsorship. I think that's hands-down, one of the most important things to ensure the healthy adoption of a solution.

Sure, you can use it without embracing it, but the teams that have embraced it are the ones that have leadership that says, "I understand the value of it, let's do this and get creative with it." These are the teams that are the most robust at using it; they have really learned how to use the tool and are constantly pushing the limits of it. From a scalability standpoint, the workloads come out of the box, but a lot of the workflows are made for the most common use case. As such, most customers customize the workflows. From that standpoint, it's very scalable.

I always recommend to anyone who is considering going with Collibra, to ensure that they have someone that will be trained on building the customized workflows — you're going to need them. Sure, you can pay Collibra to do that; you can pay the professional services to do that and they'll do a fantastic job, but it's expensive. It's a lot cheaper to invest in somebody in your own company to get some training. You can really scale quickly if you have somebody in-house that can create customized workflows and manage them.

The technical support is very good. 

As with any vendor, you can get out-of-the-box support, or you can buy additional support. Both at my prior company and at my current company, we have engaged with professional services and we meet with them once a month just to say, "Hey, I've got this weird thing I'm trying to do and I ran into this problem." Although it's not required, if you really want to accelerate the usage of the tool and the adoption of it, I always advise other people to talk with users at other companies and to consider paying for some coaching services or professional services. Even if it's just one call a month for an hour, it's still worth it, especially when you're trying to do very creative things, as most customers want. You gave me Mickey Mouse and I want to make it Donald Duck — a lot of companies do that.

The Collibra Professional Services guides are great — they're fantastic actually. I've never had a bad experience in the eight years I've been using this solution. I've never had a bad experience with their support staff, both on the technical side and on the business side.

The initial setup is not that difficult. I cannot speak to moving to the cloud because we have not done that yet, but I hear that it's not very difficult. It's been a couple of years since I have set up the platform, but as far as upgrading to a major new version, it's actually pretty straightforward. Collibra has actually done a fantastic job over the last few years to make this whole experience a lot easier. Years ago it was not as easy as it is now.

It's matured a tremendous amount over the last few years. absolutely tremendously. The company has been around for over 12 years now. When they first launched, it was a completely different animal. Now, it's a very robust metadata management and data governance tool.

One and a half, full-time employees are required for maintenance. 

I am not sure how long deployment took at our current company. I have heard from other customers who use the platform that it can take anywhere from one to three months, depending upon the complexity and how much testing they want to do. It also depends on the amount of customization they want to do. That's one of the great things about this tool — you can customize the heck out of it. If you go with everything out of the box, it's pretty straightforward and doesn't take very long. I would say deployment takes less than a month.

It's more of a soft benefit versus a hard benefit. What is the value of saving someone time? I did a cost analysis at my previous company. Our CFO used some vocabulary and some acronyms that I had never heard of — and I'd been with the company for 13 years. It took me 20 minutes — and I'm really good at sleuthing — to figure out what those things meant. I added those into our Collibra instance so that other users could quickly find out what those things meant. If you look at it from that standpoint, right after an "all-hands", our usage of our Collibra solution always spiked.

Everybody was like, "What did he mean when he said that? If it took me 20 minutes to find out what X, Y, Z meant, and it took me two minutes to get it into Collibra, then if a hundred people saved time because it took them only two minutes to find out, too — can you put a value on that? Yes. You can say, X dollars per hour, FTE, and how much time that saves. I did that very briefly just for one use case and my boss said, "Nevermind, they get it." 

I think that's the biggest value — how do you save employees time? Because everybody's too busy to waste time.

I think all software is expensive, but that's just me. Still, I would say it's probably in line with what other vendors charge for licensing. I would just say it's probably comparable. I have not done a side-by-side comparison in about three years, so I can't speak as to what's going on currently.

There's a baseline product called Data Governance Center. That is what I would consider their baseline product. You can choose to purchase other licenses, whether it's the data catalog, their privacy module for GDPR, or their Data Lineage modules — there are plenty of different licensing options. Some of them are user-based, and as with any company, the more you buy, the more of a discount you get.

You can buy as little or as much as you want. It just depends upon what your budget is. I've talked to some financial institutions that have just thrown so much money at the tool. It just makes my jaw drop to the floor — it's insane. We're doing almost what they're doing at a third of the cost. It really just depends upon your strategy.

The question is how do you help new users understand and leverage this solution to get people to come in, start using it, and understand what they're doing? Well, we've got three people that help onboard our business users.

Every use case is different because every business team wants to use the tool in a different way. It's all about business consultation, but Collibra doesn't have anything to do with that. I used to run a users meetup group for Collibra in the Bay Area. I've talked to many customers who have used Collibra, and all of them experience the same challenges — how do I get my business users? Even technical users that are on the business side want to know how to get them to onboard and adopt.

That's the piece that will really make or break in your implementation. So, make sure you have some type of stewardship team in place, whether it's on the business side or the technical side, just to help onboard new users. This is absolutely critical because as with any tool, it takes some adoption and some communication and collaboration.

When you first buy the software, you could just buy it and figure it out yourself, or you could buy their Coaching Services and their Quick Start packages. I would strongly recommend investing upfront. There is a Quick Start package, which is basically paying Collibra to help you, whether it's standing it up, whether it's your initial implementation, etc. I think it takes 10 days. I highly encourage taking this route. It will really accelerate your installation and decrease frustration. Make sure you've got leadership or executive support regarding what you're trying to do for your strategy.

The biggest lesson I've learned is that you can never assume what somebody means when they use a word. I've got 35 years of business experience under my belt. I've come to coin the phrase "What's your operational definition of that word?" You can be 45 minutes into a meeting with 10 people using the same word and find out halfway through the meeting that you're talking about four different things or two different things and everybody's frustrated and walks away.

You need to understand the meaning of the vocabulary, whether it's data vocabulary or business vocabulary. Doing so will absolutely accelerate your business and save people so much time. That's one of the things I really like about the Collibra platform. From talking to other companies, other people, and friends of mine, I know that other companies that use tools similar to Collibra — even they say the same thing. You need a data catalog, that will allow your business to quickly find what they're looking for and help you understand what that means in the context of the conversation they're having.

Overall, on a scale from one to ten, I would give Collibra Governance a rating of eight.