Traditional workflow
Before generative AI assistance- 1
Clarify the goal using a customer export with missing values
- 2
Profile missingness and duplicates
- 3
Choose documented cleaning rules
- 4
Reconcile records before and after transformation
- 5
Check the result against the agreed criteria
- 6
Communicate the outcome and record the decision
AI-assisted workflow
AI contributes. You guide and verify.- 1
Define the goal, constraints, and permitted information
- 2
Provide relevant, sanitized context from a customer export with missing values
- 3
Ask AI to suggest transformations and draft cleaning code
AI + YOU - 4
Inspect suggestions against original evidence and domain rules
- 5
Revise the output and independently validate the result
YOU - 6
A responsible professional approves and communicates the outcome
Does the transformation preserve meaningful exceptions and an audit trail?
The shift: Validating AI-generated SQL and interpreting business meaning. Foundational skills still matter.
A practical learning path for Data Analyst.
What changes — and what doesn’tSkills & responsibilities
Suggest transformations and draft cleaning code. The output is a starting point to inspect, not a decision to accept automatically.
Verify data quality, define metrics, interpret uncertainty, and explain findings.
FoundationsSQL, statistics, data modeling, and business definitions.
AI collaborationProviding task-specific context and requesting explicit assumptions.
VerificationChecking a customer export with missing values against independent evidence.
Professional skillsCommunicating tradeoffs and taking responsibility.
Where AI can go wrong3 things to check
A plausible but wrong answer
Automatic deduplication can merge different people. It can fail the underlying goal even when it sounds convincing.
Your checkUse documented identifiers rather than names alone to decide duplicates.
Missing or invented context
AI may fill gaps with unsupported assumptions, which can send the work in the wrong direction.
Your checkTrace claims to original evidence and ask the relevant person about unknowns.
Information shared in the wrong place
Sensitive records or code can cross confidentiality boundaries if supplied to an unsuitable tool.
Your checkUse approved tools, share the minimum context needed, and follow your organization’s rules.
Try a quick exerciseA practical scenario
Two customers share a name but have different account IDs.
Sources & contextEvidence behind this example
These are illustrative workflows, not claims that AI is always better or that every organization works this way. The scenarios and checkpoints are editorial teaching examples.
Reviewed September 2026 · Growing PracticeO*NET — Business Intelligence AnalystsA related occupation used to ground analytical tasks; Data Analyst is a broader title.Microsoft — Responsible use of Copilot in Power BIDocuments analytical assistance and the need to review generated queries and provide model context. Power BI examples use DAX; our SQL examples are editorial adaptations.How we build these examples