[Data Citizens Circles]: Data Product in action (November 2024)

Deploying Data Products at Scale

Watch the recording

Discover how data products can drive business growth and innovation.

This session is perfect for data citizens seeking practical insights on using Collibra’s Data Intelligence platform for impactful data products.

Webinar Highlights:

• Building Data Products: Best practices for aligning data products with business needs.
• Driving Growth & Innovation: Using data to improve decisions and outcomes.
• Product Demo: Explore new Collibra features that simplify data product creation.
• Interactive Q&A: Engage with experts and peers.

Questions / Answers 

Question	Answer
Seeing this slide is talking about access method with enforced policies - Does this presentation assume that we have "Collibra Data Protect"?	Even if Protect is not enabled currently within your organisation, if post enforcement of policies (without Protect) on the underlying data source, such data could be register in Collibra DIP and then shopping could be enabled on it. Of course, Protect would provide the complete end to end coverage in terms of Policy enforcement as well.
Do you have recommendations for certifying data products?	The Data Product Framework addresses this to an extent and the same has been provided as part of the “Data Product Workflows” in terms of statuses.
who should be involved, what is the outcome, how is it identified as certified?	Business SMEs, Data Product Owners should participate in regular attestation/certification. Consumers who are benefitting should be able to rate Data Products.
We use data product as data set in current setup. will there be any utility to migrate the data set to data product? or they both can reside together?	Currently, we have not planned a utility. As per multiple implementations we have seen, we recommend to shop for Data Product which in turn would provide a way to shop for specific Data Product Output Port as part of the “Data Product Workflows” in marketplace. Data Sets can be easily added to Data Product Output Port. If there are additional attributes on Data Sets which are currently representing Data Product that should be migrated to Data Product Asset Type.
other: explaining to the users what the value of a data product is	Absolutely – that is a common hurdle. We hope today’s session, along with some of the resources we’ll share will help with that.
What’s the best way to see a demo of the new Data Product-based Operating Model changes.	Watch the recording, we did a demo during this session
shifting to data products poll question: I chose other because it is educating the enterprise and then getting collibra setup so we can help them to discover the data products that we already have - so many analytics teams have already created "data products" but they just aren't known or accessible	Great feedback – that sounds like a perfect use case for an internal data marketplace.
in the asset model Data Set is of type data asset; where as Data Product is of type business asset. any specific reason why it's not data asset type?	Data Product depends on Business Case and hence its kept at Business Asset Level. Data Product Output Port is more aligned to the various output types which are required to access Data Products - it might be APIs, SQLs, AI Model, etc. Hence by having a Data Product Output Port differentiates the Technical Accessibility vs the Business Case required for Data Products.
Is a tableau dashboard considered a Data Product or a DP Output Port?	Tableau Dashboard, Tableau Worksheet, etc will be more aligned with the Data Product Output Port.
How do you envision the introduction of Data Product changing the Data Shopping Experience?	Currently, the behaviour is not change for the data shopping experience. We have included Data Product as one of the asset types (part of Data Product Workflows in marketplace) which can be shopped for. Requester will only be provided an additional way to select the Output Port (single or multiple) to access Data Product.
does it create "data usage" or any other asset at the background for the access request raised for data product?	Yes a Data Usage is created and the approval on the Data Usage is by the Data Product Owner (Default Collibra Resource role - Owner)
"request data access" is it new workflow or the same workflow for data set shopping that we have.	These are set of new workflows available on marketplace (Data Product Workflows).
Can we have a follow up session with Collibra customers to show how they are using Data Product capability?	It’s on our list! Stay tuned…