Key AI Terminology for Oversight Professionals
Why AI Terminology Matters for Oversight
This lesson provides a concise, professional glossary of AI terms that oversight professionals will encounter, defined in context rather than academically.
At the Awareness level, your primary goal is to build a solid conceptual foundation. You do not need to operate AI systems yourself at this stage—but you must understand what they do, how they work at a high level, and why they matter for oversight. This knowledge will be the bedrock upon which all subsequent levels build.
This lesson is designed to be accessible to professionals at all experience levels while providing the depth needed for practical application. Whether you are encountering these concepts for the first time or building on existing knowledge, the material ahead will strengthen your ability to navigate AI governance challenges with confidence and competence.
Why This Matters for Risk, Compliance & Audit
These terms are the vocabulary of serious AI governance conversations. They come up constantly in governance work: a vendor pitch ("Our model achieves 94% accuracy with 12% false positive rate"), an audit question ("Are you monitoring for bias in the classification?"), a risk assessment ("The model experienced drift; it's being retrained"), and a governance decision ("Should we lower the threshold to catch more issues, given the higher false positive rate?").
Understanding the terminology allows you to participate meaningfully in these conversations. Precision in terminology is a sign of rigor; vagueness is a red flag.
Core Concepts
Core Concepts and Definitions
Accuracy / Precision / Recall
- Accuracy: The proportion of correct predictions (both true positives and true negatives) out of all predictions. A model that is 90% accurate gets 90 out of 100 predictions right. NOT the same as usefulness. A 90% accurate fraud detection model might still generate too many false positives to be usable.
- Precision: Of the items flagged as high-risk, how many actually are high-risk? High precision means fewer false positives (lower false alarm rate). Important when you want to investigate only things likely to be real issues.
- Recall: Of all the actual high-risk items, how many did the model find? High recall means fewer false negatives (fewer missed issues). Important when you cannot afford to miss problems.
Professional use: Precision and recall are trade-offs. A vendor might say, "Our model has 95% precision," meaning "when we flag something, we're right 95% of the time." But it might have only 60% recall, meaning "we miss 40% of actual issues." Both matter; the vendor's emphasis on one might obscure weakness in the other.
Algorithm
A step-by-step procedure for solving a problem or accomplishing a task. In AI contexts, often used to describe the mathematical procedure an ML system uses to learn patterns from data. Not usually something you need to understand in detail, but the term comes up when vendors discuss their approach.
Professional use: "Our model uses a random forest algorithm" tells you something about the technical approach but not necessarily whether it will work for your use case. Ask instead: "What does the model do? How is it trained? What is its accuracy on your data?"
Bias (in AI)
A systematic error in an AI system's outputs, usually learned from biased training data. If an AI system is trained on data that overrepresents certain groups or underrepresents others, the AI system will learn and replicate that imbalance.
Example: If a credit approval AI is trained on historical data where minority applicants were approved at lower rates, the model might learn to approve minority applicants at lower rates too, replicating historical bias.
Professional use: "We've tested for bias" is vague. Ask: "What specific groups were tested? What metrics did you use? What bias was found, and how was it corrected?" Bias testing is not a one-time box; it is ongoing monitoring.
Black Box
An AI system whose decision-making process is not transparent or understandable to humans. You can see the input and output; the internal logic is opaque.
Professional use: Black-box status is common in large neural networks. It is not necessarily a reason to reject an AI system, but it is a reason to require stronger human oversight, monitoring, and performance validation.
Classification
The task of assigning items to categories. An AI system trained to classify divides items into discrete groups.
Example: Classifying documents as "policy," "procedure," or "evidence."
Professional use: Classification is one of AI's strengths. Ask about the categories (are they clearly defined?), the training data (does it represent all categories fairly?), and the accuracy on each category (some categories might be more error-prone than others).
Confidence Score / Probability Score
A number (usually 0-1 or 0-100) representing how confident the model is in its own prediction. 0.95 means the model is very confident; 0.55 means the model is barely more confident than a coin flip.
Professional use: Confidence is not accuracy. A model can be confidently wrong. Always ask: "What is the actual accuracy of high-confidence predictions on your data?" Use confidence scores to set thresholds for human review, not as a measure of how right the model is.
Data (Training Data, Test Data, Production Data)
- Training data: The dataset used to teach the AI system. The model learns patterns from this data.
- Test data: Held-back data used to estimate how well the model will perform on new, unseen data.
- Production data: Real-world data the model encounters after deployment.
Professional use: A critical question for any AI system: "What was it trained on?" If it was trained on data that doesn't represent your organization's context, performance may differ significantly. Also ask: "How is production data monitored?" to ensure the model continues to perform well.
Drift (Model Drift / Performance Drift)
A decrease in an AI model's accuracy over time, usually because the real-world data has changed and the model was trained on older, different data.
Example: A fraud detection model trained on pre-pandemic transaction patterns may perform poorly on pandemic transaction patterns. The environment drifted; the model did not.
Professional use: AI systems require ongoing monitoring. If a vendor says, "We deployed it and haven't retrained since," that's a red flag. Performance drift is expected; the question is how it is monitored and addressed.
Explainability / Interpretability
The ability to understand and explain an AI system's decision. Some AI systems (decision trees, linear models) are inherently explainable. Others (deep neural networks) are not.
Professional use: For high-stakes decisions, explainability matters. If you cannot explain why the system decided something, you cannot defend the decision to a regulator or audit. This is a governance control, not a technical luxury.
False Positive / False Negative
- False positive: The model flags something as high-risk that is actually normal. (Type I error)
- False negative: The model misses something that is actually high-risk. (Type II error)
Professional use: These are trade-offs. Reduce false positives and you increase false negatives. Set the threshold based on the cost of each type of error. In fraud detection, false negatives (missed fraud) are often more costly than false positives (false alarms requiring investigation).
Generalization
The ability of an AI model to perform well on new data it was not trained on. Good generalization means the model learned underlying patterns, not just memorized training examples.
Professional use: Ask: "How was the model tested on data it hadn't seen before?" If the answer is "we tested on a holdout set from the same dataset," that's fine for basic confidence, but not sufficient to verify it will work on your data, which may differ significantly.
Hallucination
When an AI system (especially an LLM) generates false information with confidence, as if it were fact.
Example: An LLM generates: "Section 404(b) of SOX requires annual board certification of controls," inventing an obligation that does not exist in the actual regulation.
Professional use: Hallucination is inherent to how LLMs work (they predict statistically likely text). Never assume an LLM has verified information. Require expert human review of any LLM output before it is used in governance decisions.
Large Language Model (LLM)
An AI system trained on vast amounts of text data to predict and generate language. Examples: ChatGPT, Claude, Gemini, LLaMA.
Professional use: LLMs are powerful for summarization and draft generation but dangerous for fact-dependent tasks like policy interpretation. Use them as assistants that generate drafts; always require expert validation before use.
Machine Learning (ML)
AI where the system improves its accuracy by learning from data, rather than being programmed with explicit rules.
Professional use: When a vendor says "machine learning," they mean the system learns patterns from data. This is different from a rules engine (which is programmed) or analytics (which is human-interpreted). Understanding this distinction is critical for governance.
Model
In AI contexts, the trained system that makes predictions or generates content. It's the "learned" representation of patterns found in training data.
Professional use: "Our model flagged this transaction" means "our trained AI system, based on patterns it learned, flagged this." The model is not perfect; it is a probabilistic tool that requires validation.
Neural Network
A type of AI architecture (inspired by the brain) composed of interconnected nodes. Deep neural networks (many layers) are especially powerful for complex pattern recognition but are also difficult to explain.
Professional use: You don't need to understand neural networks technically. Just know: systems using neural networks can detect complex patterns but are often opaque (black boxes). Require strong oversight.
Overfitting
When an AI model learns the training data too well, including its quirks and noise, rather than learning generalizable patterns. The model performs well on training data but poorly on new data.
Professional use: This is a common problem in AI. It's why testing on data the model hasn't seen is important. A vendor claiming 98% accuracy might be overfitted. Ask: "How was accuracy measured? On held-out test data? On production data?"
Performance Metrics
Quantified measures of how well an AI system works. Examples: accuracy, precision, recall, F1 score, AUC-ROC.
Professional use: When a vendor says "our model is 95% accurate," insist on understanding which metric and on what data. Also ask: "What are the false positive and false negative rates? What is the cost of each?" Metrics matter; context matters more.
Regression (Predictive)
An AI task where the model predicts a continuous numerical value (e.g., predicted risk score, predicted fraud amount) rather than a category.
Professional use: Regression is useful for scoring. It's different from classification (assigning to categories). Understand which task the model is designed for.
Retraining / Fine-Tuning
Updating a model with new data to maintain or improve accuracy as the environment changes.
Professional use: An AI system that is not retrained will experience performance drift. Ask vendors: "How often is the model retrained? What process ensures retraining happens?" This is part of responsible AI governance.
Supervised Learning vs. Unsupervised Learning
- Supervised: The training data includes both inputs and correct answers. The model learns to predict the correct answer for new inputs. Example: Training data includes transaction examples labeled as "normal" or "fraud." The model learns to classify new transactions.
- Unsupervised: The training data includes only inputs; the model learns to find structure or patterns without knowing the "correct answer." Example: Training data includes all transactions (without fraud labels). The model learns to group similar transactions and flag unusual patterns as anomalies.
Professional use: Supervised learning requires curated training data with correct labels (expensive but accurate). Unsupervised learning requires less curation (cheaper but may find spurious patterns). Know which one your vendor is using.
Threshold
The confidence level at which the model takes action (flags something, makes a decision, etc.). Setting the threshold is a governance choice.
Example: A fraud model might flag any transaction with > 70% fraud probability. Raising the threshold to 85% reduces false positives but misses more fraud.
Professional use: The threshold is where governance controls the model's behavior. Ask: "Who set the threshold? Based on what criteria?" This is not a technical decision; it is a governance decision.
Training Data Quality
How representative, complete, and accurate the training data is. Poor-quality training data leads to poor model performance and bias.
Professional use: Ask: "What data was the model trained on? How large is the dataset? Does it represent all relevant groups and scenarios?" Training data quality is often the biggest predictor of model success.
Validation / Cross-Validation
Testing a model on data it was not trained on to estimate real-world performance.
Professional use: A vendor claiming accuracy must show how they validated it. "Tested on a hold-out set" is the minimum. "Tested on multiple years of different data" is better. "Tested on your specific data" is ideal.
Practical Use Cases
Understanding concepts in the abstract is valuable, but the real test is whether you can apply them in professional practice. This section bridges the gap between theory and application with concrete scenarios drawn from oversight work. Each example is designed to help you recognize similar situations in your own work and respond with appropriate professional judgment.
Example 1: Reading a Vendor Proposal
Vendor claims: "Our AI system is 95% accurate at detecting compliance violations."
What you should ask:
- Accurate at what task? (Detecting violations in what type of data?)
- What data was it tested on? (Is it similar to our data?)
- What is the false positive rate? (How many false alarms should we expect?)
- What is the false negative rate? (How many violations might we miss?)
- Was it validated on data it hadn't seen before? (How?)
- Has it been validated on your type of data? (If not, why should we assume 95% accuracy applies?)
These questions distinguish serious vendors from marketing.
Example 2: Evaluating a Proposal to Retrain a Model
Request: "We propose retraining the model monthly using the last month's transactions."
What you should consider:
- How much new data becomes available monthly? (Is retraining necessary that often, or is it overkill?)
- What is the cost and effort of retraining? (Is it worth the benefit?)
- What validation will be done after retraining? (You can't just retrain and deploy blindly.)
- How will you know if retraining improved or worsened performance? (What metrics will you measure?)
Example 3: Governance Language
Instead of: "We are using an advanced AI system to detect fraud."
Write: "We deploy an ML model trained on historical transaction data to flag unusual transactions for investigation. The model achieved 85% accuracy and 15% false positive rate in validation. The model is re-evaluated quarterly for performance drift. All flagged transactions are reviewed by a compliance analyst before escalation."
The second statement demonstrates governance clarity.
Anti-Patterns
Using jargon without understanding: Throwing around terms like "neural network," "algorithm," or "machine learning" without knowing what they mean makes governance less rigorous, not more.
Accepting metrics without context: "95% accuracy" is meaningless without knowing: tested on what data, in what context, with what false positive and false negative rates?
Confusing related terms: Accuracy vs. confidence, precision vs. recall, training data vs. test data. These distinctions matter in governance.
Human Judgment Checkpoints
Terminology supports human judgment; it does not replace it. At each checkpoint below, a person must apply professional judgment rather than defer to the model.
- Confidence vs. accuracy: A model can be confidently wrong. Treat confidence scores as a trigger for human review, not as proof the model is right.
- LLM outputs: Because hallucination is inherent to how LLMs work, require expert human review of any LLM output before it is used in a governance decision.
- Setting the threshold: Deciding the confidence level at which the model acts is a governance decision, not a technical one. A human must own that choice and the trade-off between false positives and false negatives it implies.
- Explainability for high-stakes decisions: If you cannot explain why a system decided something, you cannot defend it to a regulator or audit. Require human-owned explanation for high-stakes outputs.
Responsible AI Considerations
- Fairness: Bias is a systematic error learned from biased training data. Ask which specific groups were tested, what metrics were used, what bias was found, and how it was corrected—and treat bias testing as ongoing monitoring, not a one-time box.
- Transparency: Black-box systems are not automatically disqualified, but opacity is a reason to require stronger oversight, monitoring, and explainability for high-stakes decisions.
- Accountability: Performance drift is expected; an AI system that is never retrained will degrade. Responsible governance defines how drift is monitored, how often the model is retrained, and who is accountable for that process.
- Validity: Training data quality is often the biggest predictor of model success. Insist that vendors show how performance was validated—ideally on your own data, not just a holdout set.
Practice and Reflection
- Terminology in your organization: Are there AI systems in use in your organization? Can you describe them using at least three terms from this glossary?
- Vendor proposals: Find a recent vendor proposal about an AI tool. Map the vendor's claims to terminology in this glossary. Are the claims precise or vague?
- Your communication: In your next governance meeting about AI, use at least one term from this glossary correctly. Note whether the conversation becomes more precise.
As you apply this lesson, keep these guiding principles in mind:
- Start with awareness: Begin observing where AI is currently being used—or proposed for use—in your organization. You do not need to evaluate it yet; simply notice it.
- Build your vocabulary: Use the terminology from this lesson precisely. Clear language prevents misunderstandings that lead to governance gaps.
- Ask questions: When colleagues mention AI, ask clarifying questions: What type of AI? What data does it use? How are outputs verified? Your questions alone improve organizational awareness.
- Document what you learn: Keep brief notes on AI-related observations and questions. This habit will serve you well in later levels when formal documentation becomes a professional requirement.
Key Takeaways
- These terms are the vocabulary of serious AI governance conversations.
- Precision in terminology is a sign of rigor; vagueness is a red flag.
- When evaluating AI systems, insist that vendors use specific terms: accuracy on which data, precision vs. recall, how bias was tested, etc.
- Governance discipline requires understanding what the terms mean and holding vendors/teams accountable to them.
Frequently Asked Questions
Do I need to understand AI systems technically at this stage?
No. At the Awareness level you do not need to operate AI systems yourself. You must understand what they do, how they work at a high level, and why they matter for oversight.
If a vendor says their model is 95% accurate, is that enough?
No. Accuracy is meaningless without context. Ask which metric, on what data, and what the false positive and false negative rates are.
Is a black-box model an automatic reason to reject an AI system?
No. It is not necessarily a reason to reject the system, but it is a reason to require stronger human oversight, monitoring, and performance validation.
Glossary
| Term | Definition |
|---|---|
| Accuracy | Proportion of correct predictions |
| Algorithm | Step-by-step procedure for solving a problem |
| Bias | Systematic error learned from biased training data |
| Black Box | AI system whose reasoning is opaque |
| Classification | Assigning items to discrete categories |
| Confidence Score | Model's estimate of certainty in its prediction (0-1) |
| Drift | Decrease in model accuracy over time |
| Explainability | Ability to understand and explain a model's decision |
| False Positive | Flagging something as risky that is normal |
| False Negative | Missing something that is actually risky |
| Generalization | Ability to perform well on new, unseen data |
| Hallucination | LLM generating false information as fact |
| LLM | Large Language Model trained on vast text data |
| Machine Learning | AI where system learns patterns from data |
| Model | The trained AI system making predictions |
| Overfitting | Learning training data too well; poor generalization |
| Precision | Of flagged items, how many are actually high-risk |
| Recall | Of actual high-risk items, how many the model found |
| Retraining | Updating a model with new data |
| Threshold | Confidence level at which model acts |
| Training Data | Data used to teach the AI system |
| Validation | Testing model on unseen data |
Skill.re