Skill-Details
chief-data-officer-advisor
Relevant data strategy leadership, not hands-on data science.
Vor Nutzung prüfen
Die automatische Prüfung bewertet Relevanz, nicht Sicherheit oder Empfehlung. Lies vor der Nutzung die Quellanweisungen.
SKILL.md
Dieser Auszug wurde bei der Prüfung gespeichert. Die externe Quelle enthält die vollständige und aktuelle Version.
--- name: "chief-data-officer-advisor" description: "Chief Data Officer advisory for startups: AI training data rights and consent provenance, data product strategy (warehouse vs lakehouse vs mesh, build-vs-buy), B2B customer-data-as-asset valuation and M&A readiness, data team org evolution. Use when deciding whether to train models on customer data, choosing data architecture, valuing data for fundraising or M&A, sequencing data hires, or when user mentions CDO, chief data officer, data strategy, data mesh, lakehouse, training data, data product, data monetization, or customer data asset. NOT a tactical data engineering skill — strategic decisions only." license: MIT metadata: version: 1.0.0 author: Alireza Rezvani category: c-level domain: chief-data-officer-leadership updated: 2026-05-12 python-tools: ai_training_data_audit.py, data_product_strategy_picker.py, data_asset_valuator.py frameworks: training-data-rights-matrix, data-product-strategy, customer-data-as-asset, data-team-org-evolution --- # Chief Data Officer Advisor Strategic data leadership for startup CDOs and founders without one. **Four decisions, no surveys:** 1. **Can we train our model on this data?** — origin × consent × use-case matrix 2. **Warehouse, lakehouse, or mesh — and what do we build vs buy?** — stage-driven architecture 3. **What is our customer data worth?** — strategic value + M&A multiplier + productization paths 4. **What data role do we hire next?** — stage-to-role map, centralize-vs-embed trigger This skill does **not** cover tactical data engineering. For schema design, observability, query optimization, RAG, or ML platform implementation, see `engineering/database-designer/`, `engineering/observability-designer/`, `engineering/data-quality-auditor/`, `engineering/sql-database-assistant/`, `engineering/rag-architect/`, `engineering/llm-cost-optimizer/`. ## Keywords CDO, chief data officer, AI training data, consent provenance, training rights, GDPR Article 6 lawful basis, GDPR Article 22, EU AI Act high-risk, ePrivacy, copyright fair use, hiQ v. LinkedIn, scraped data, synthetic data, data product, data mesh, lakehouse, medallion architecture, dbt, Snowflake, BigQuery, Databricks, Fivetran, Airbyte, reverse ETL, feature store, customer data as asset, data monetization, data productization, anonymization, k-anonymity, differential privacy, M&A data diligence, data org, analytics engineer, data engineer, data scientist, data product manager, centralize vs embed, hub and spoke ## Quick Start ```bash # Audit data sources for AI training eligibility python scripts/ai_training_data_audit.py # uses embedded sample python scripts/ai_training_data_audit.py path/to/sources.json # Pick data architecture + build-vs-buy + sequencing python scripts/data_product_strategy_picker.py # uses embedded Series A SaaS python scripts/data_product_strategy_picker.py path/to/profile.json # Value the customer data corpus + productization viability python scripts/data_asset_valuator.py # uses embedded B2B sample python scripts/data_asset_valuator.py path/to/corpus.json ``` ## Key Questions (ask these first) - **What decision does this data drive?** (If none, why are we collecting it?) - **What's the consent provenance of every source we want to train on?** (TOS-only is not the same as explicit opt-in.) - **Who are the internal data consumers, and how many distinct domains do they span?** (Drives centralize-vs-embed and warehouse-vs-mesh.) - **In an M&A scenario, is our data a moat or a liability?** (Customer carve-outs in MSAs can flip the answer.) - **Are we hiring an analytics engineer or a data scientist next?** (They solve different problems; founders confuse them.) - **Have we run an anonymization audit before any external sharing?** (k-anonymity ≥ 5 is the floor, not the ceiling.) ## Core Responsibilities ### 1. AI Training Data Rights The 2026 quesVollständige Quelle auf GitHub lesen (öffnet externe Seite)