Data as a strategic asset

The Data Management Capability Assessment Model (DCAM), developed by the EDM Council, is a cross-industry framework for assessing and developing organisational data management capability. DCAM v3 was announced in June 2025 with stronger coverage of AI, cloud, governance, security, privacy, and modern pipelines. DCAM v3.1 training material presents eight core components: Data Strategy, DMS and Business Case; Data Management Program and Funding; Architecture across business, data, and technology; Business Data Knowledge; Data Quality Management; Govern Data and DMP; Data Management Operations, Risk, and Control; and Analytics Management.

A maturity assessment is not a beauty contest. It asks whether the organisation can prove how data strategy is funded, how data meaning is managed, who owns quality, which controls govern access and use, how data operations are monitored, and how analytics are connected to business decisions. A policy document without adoption evidence is not maturity. A dashboard without ownership is not maturity. A platform without quality controls is not maturity.

Evidence should be specific. A governed customer data domain should show a named owner, glossary terms, approved definitions, lineage from source systems to reports, quality rules, issue workflow, access policy, retention policy, and active usage metrics. A leadership team should be able to see whether the data asset is improving, degrading, or accumulating unmanaged risk.

The DCAM assessment process identifies capability gaps and prioritises investment. A financial services firm with strong data governance (Level 4) but weak data culture (Level 2) has a different remediation roadmap than a retail firm with strong operational data (Level 3) but weak data architecture (Level 1). The framework makes these trade-offs visible.

Data monetisation takes three forms. Direct monetisation sells data or data products to external parties: weather companies selling historical data to insurers, financial data providers selling market feeds to hedge funds, credit bureaus selling risk scores to lenders. This requires careful legal due diligence on consent, data sharing agreements, and regulatory permissions.

Indirect monetisation improves internal decisions and products using data without directly selling it. Recommender systems improve product discovery; pricing models improve margin decisions; demand forecasts improve stock positioning; customer analytics improve retention. The data is not sold. It changes the quality, timing, or economics of decisions.

Risk reduction monetisation uses data to avoid losses: insurance fraud detection, credit default prediction, cybersecurity anomaly detection, quality control, safety monitoring, and predictive maintenance. The value is the expected loss avoided, adjusted for false positives, false negatives, control cost, and any customer or regulatory harm created by the intervention.

Valuing data as an asset is methodologically challenging because data has no standard accounting treatment (it does not appear on balance sheets in most jurisdictions). Three approaches exist: cost approach (what did it cost to collect and maintain?), market approach (what would comparable data sell for?), and income approach (what revenue or cost saving does it generate?). The income approach is most useful for strategic decision-making but requires attributing revenue or savings to specific data assets, which requires instrumentation.

Data literacy is the organisational ability to read, work with, analyse, communicate, and challenge data. Without it, dashboards go unread, models produce outputs that decision-makers distrust, and data products are built for analysts rather than for the people who need to act on evidence.

The programme should be one path for every learner. Everyone starts with definitions, quality, uncertainty, and ethical use. Everyone then learns modelling, pipelines, databases, analytics, governance, and strategy. The difference is not the path; it is the examples each learner brings. A board member still needs to understand base rates before approving a fraud model. An engineer still needs to understand capital allocation before designing a data product.

Measuring data strategy success requires a hierarchy of metrics. Input metrics measure programme activity: number of data products in the catalogue, percentage of datasets with documented ownership, number of staff completing data literacy training. Process metrics measure governance effectiveness: data quality scores by domain, percentage of pipelines with SLAs, mean time to resolve data quality incidents. Outcome metrics measure business impact: revenue attributable to data-driven decisions, cost reduction from predictive maintenance, reduction in compliance incidents.

The Chief Data Officer role succeeds when it can connect data work to decisions the organisation already values. A CDO should be able to show which business outcome is constrained by poor data, which data asset will change that outcome, who owns it, what control is missing, what investment is needed, and how success will be measured after release.