Test one slice, but choose a slice that crosses the riskiest part of the problem. A tiny easy demo will only prove the easy part. Use this decision rule: - If reversing the choice is cheap, try it. - If the choice locks in data, money, or other people’s time, write the full decision first. - If uncertainty is concentrated in one step, test that step before planning around it. For metrics with fuzzy definitions, make the first test produce evidence you can compare, not just something that looks complete.

This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For metrics with fuzzy definitions, I would start with these checks: - Fix the grain before calculating - Keep assumptions next to the metric - Show uncertainty in the output If you share real material, remove anything private first and replace bracketed fields with concrete details.

## Copy-ready prompt ```text Act as a chief data officer. Answer this question: “How should data governance change for generative AI?” Objective: update data governance for prompts, embeddings, model outputs, agents, and third-party providers. First, ask up to five concise questions needed to tailor the analysis. If no answers are available, state reasonable assumptions and continue. Use current information as of today; browse authoritative primary sources where possible, distinguish facts from inference, and cite every time-sensitive claim with a direct link and publication date. Cover: class