Who it's for
For those who need to share data with confidence and without bureaucracy.
Six types of organisation and six professional profiles find in KDV an answer to similar pains. Open each one to see the pains, what changes and a good first case.
Types of organisation
Organisations like yours.
Open an item to see typical pains, how KDV responds and a good first case.
01Public sector, agencies and professional councils
Typical pains
- Data protection and transparency
- Accountability to oversight bodies
- Data locked in legacy systems
- Data exchanged between agencies by spreadsheet
- Tight licence budgets
How KDV responds
A common baseline with owner, contract, classification and policy-based access; evidence of every decision; data stays in the agency's environment.
A good first case
A product that answers a question from the oversight body.
Closest example: Prioritise inspections with current, traceable information.
02Networks and multi-organisation ecosystems
Typical pains
- They want to share data without losing control
- There is no common rule
- Nobody knows who approved what
How KDV responds
An ecosystem with a common purpose; minimum common rules and local decisions; time-limited, revocable access.
A good first case
An indicator two members need and neither has alone.
Closest example: Anticipate pressure on services with data from scattered systems.
03Mid-sized companies moving beyond spreadsheets and siloed BI
Typical pains
- Each area has its own number
- Reports without an owner
- Dependence on one person
- No governance team
How KDV responds
Start with one data product; four stages; ready templates; governance proportional to team size.
A good first case
The indicator that causes the most debate in the board meeting.
Closest example: From conflicting sales reports to an agreed revenue product.
04Regulated sectors (health, finance, energy, utilities, education)
Typical pains
- Audits require proof
- Classification of sensitive data
- Access granted by email and never revoked
How KDV responds
Approval and implementation as distinct, recorded acts; time-limited exceptions; evidence indicators.
A good first case
The access review of a product containing personal data.
Closest example: Prioritise inspections with current, traceable information.
05Organisations starting with generative AI and agents
Typical pains
- Fear of exposing data to models
- Answers without a reliable source
- Nobody answers for the data used
How KDV responds
A data product with a contract and permitted use declared before any AI consumption.
A good first case
Declare in the contract whether and how the product may be used by AI.
Closest example: From conflicting sales reports to an agreed revenue product.
06Consultancies, integrators and independent practitioners
Typical pains
- They need a recognisable, reusable method
- Clients ask for “DAMA in practice”
- Artefacts are reinvented on every project
How KDV responds
An open method (CC BY 4.0), editable templates and an explicit relationship with DAMA-DMBOK, DCAM and Data Mesh.
A good first case
Apply the Playbook with a client using the ready templates.
Closest example: From conflicting sales reports to an agreed revenue product.
Professional profiles
Who decides and who uses.
Select a profile. You can save it: the Documentation will then suggest a reading path.
Business area manager
“Every meeting starts with an argument about which number is right.”
Choose an important decision and sponsor the first case.
See what changes →CDO, data or IT manager
“We have tools, but no governance. DAMA is too big to start with.”
Define the common baseline and the roles of the first domain.
See what changes →Data protection officer (DPO), compliance and audit
“I can't prove who accessed what, why and until when.”
Review the access flow and the exception log.
See what changes →Data engineering and architecture
“Access requests arrive by email, pipelines have no owner and I'm afraid of vendor lock-in.”
Compare the three implementation paths.
See what changes →Data steward (sometimes without knowing it)
“I'm the one everyone asks what this column means.”
Start with the contract for the most requested product.
See what changes →Analyst, data scientist or AI team
“It takes me weeks to get access and I don't know if I can use the data.”
Read the product contract before requesting access.
See what changes →Questions from decision makers
What managers ask before starting.
Short answers, with no promises of timelines or results.
01How much does it cost?
The method is free and open (CC BY 4.0). You can apply it with documents and spreadsheets. Implementation and services from KDV Ecosystems are optional and contracted separately.
02Do I need to buy a platform?
No. Start with controlled documents and working practices, use your existing platform, or combine modular capabilities. Choose support appropriate to your context.
03How long does it take?
It depends on access to sources, the team available and the controls required. That is why the Playbook starts with a preparation that scopes the first case before any deadline.
04Does it replace DAMA-DMBOK, DCAM or Data Mesh?
No. KDV puts these references into day-to-day practice. See what each one covers and what requires your own work. KDV does not claim certification.
05Does it guarantee GDPR or LGPD compliance?
No. It supports compliance with explicit decisions and records, but it does not replace legal advice. See the guide AI and privacy.
06Who needs to be involved?
In the first case: a sponsor (domain owner), a product owner, a steward, someone from engineering and the consumer who will use the data. One person can hold several roles.