Business Pill · Fewer, better examples
Data quality means the examples a model learns from set the habits it picks up. A model copies what it is shown, the careful parts and the sloppy parts alike.
A short explainer video, under a minute. The engineer and the robot are an illustration.
At a glance
What Data Quality Is
Her fix was simple: keep only the examples that cite their claims.
Which Examples to Keep
The video sets two choices side by side. Keep everything, and the pile is huge but the robot learns the sloppy habits.
Why It Matters
The video turns this into one question: what does a good example look like in our work?
The Short Answer
Picture an engineer who teaches a robot to write reports. She gives it a big pile of examples.
The robot copies them all, even the sloppy ones, where a claim comes with no source. So its own reports do the same.
What Data Quality Is
Her fix was simple: keep only the examples that cite their claims. That is data quality.
The idea in the video is plain. A model copies what it is shown, so the choice of examples is a choice about its habits.
Which Examples to Keep
The video sets two choices side by side. Keep everything, and the pile is huge but the robot learns the sloppy habits. Keep only the cited ones, and there are far fewer examples, but it learns the careful ones.
The board names a risk on each side. The first copies the noise. The second drops some good examples.
The Idea on One Board
Which examples to keep
Keep everything
Examples
a huge pile
Habits it copies
the sloppy ones
Risk
copies the noise
Keep the cited ones
Examples
far fewer
Habits it copies
the careful ones
Risk
drops some good ones
The honest limit
The Honest Limit
A filter can throw good examples away too. The video’s advice is to check what it removes.
A cleaner set is not automatically a complete one.
Why It Matters
The video turns this into one question: what does a good example look like in our work?
Its takeaway is short. A model copies its examples, so check the examples first.
The key insight: A model copies its examples. So check the examples first.
The honest limit
But a filter can throw good examples away too.
So check what it removes.
Where This Shows Up in AI Business Today
From our news coverage
Ai2 Open-Sources AstaBrief: 8B Model, 3.5x Faster Reports
Data quality is where one open lab says it found its biggest gain. Our report on Ai2’s AstaBrief says Ai2 credits its largest training improvement to a plain filter that keeps only reports that cite their claims, and says more elaborate filtering did not help. Starting from a pool of 90K research queries, Ai2 says, it kept 47K usable training examples after quality filtering. These are Ai2’s claims, and our piece verified none of them independently.
The Business Engineer Lens
Where this idea sits in the Business Engineer library:
The Question to Ask
- What does a good example look like in our work?
How This Concept Connects
Layer 2 of 8 · Models & Training, on the Business Engineer Concept Map
- Data Quality builds on Data Labeling. Both say a model copies what it is shown: labels set the ceiling, and sloppy examples teach sloppy habits.
- Data Quality constrains Synthetic Data. Invented complaints come out tidy and polite while real ones are not, a quality gap the model then copies.
- Data Quality constrains Few-Shot Prompting. Few-shot models copy the flaws of the examples too, the data-quality lesson’s point applied at prompt time.
- Data Quality contrasts with Unlearning (lesson unlocks soon). Filtering examples before training is something you can check; taking one back out afterwards means retraining or hoping.
- Data Flywheel (lesson unlocks soon) builds on Data Quality. The flywheel feeds user corrections back into the product, and the data-quality lesson says a model copies what it is shown.
The Four Intelligence Moats
Curated data as a defensible input.Business Engineer framework
AI Quality Plateau
Data quality as a lever when scale plateaus.
Get the full Concept Map as a free poster.
Related Business Pills
See It in the News
Ai2 Open-Sources AstaBrief: 8B Model, 3.5x Faster Reports. The news story this pill grew out of.
All Business Pills
- The Memory Wall: Why a Faster AI Chip Is Not Faster AI
- Tokens per Watt: What an AI Data Centre Actually Produces
- Why AI Can’t Be Both Instant and Cheap: Latency vs Throughput
- The Model and the Harness: Why Same-Model Products Differ
- Context, Not Capability: Why a Smart AI Model Gives Poor Answers
- Discardable Software: When Code Is Cheap Enough to Throw Away
- Human in the Loop vs Human on the Loop: Supervising AI Agents
- The AI Audit Problem: When Making Work Is Cheaper Than Checking It
- AI Evaluation as Acceptance Test: How to Know It’s Good Enough
- Extensibility Is Control: Who Holds the Power in an AI Product
- RLHF Explained: How an AI Model Learns What People Prefer
- Pretraining Explained: How an AI Model Learns Before Anyone Teaches It
- Fine-Tuning Explained: How to Adapt a General AI Model to One Job
- Tokens Explained: The Unit AI Reads, Writes and Bills In
- Embeddings Explained: How a Machine Compares Meaning
- RAG Explained: How a Model Answers From Your Documents
- AI Hallucination Explained: Why Models State False Things
- Distillation Explained: How a Small Model Learns From a Large One
- Reasoning Models Explained: What Changes When AI Thinks First
- Tool Use Explained: How an AI Model Goes From Text to Action
- Capex and Depreciation Explained: Why Chip Lifetime Drives AI Profits
- Run-Rate Revenue Explained: What an AI Company’s Number Means
- Backlog Explained: Revenue That Is Signed but Not Yet Earned
- Switching Costs Explained: Why It Is Hard to Leave an AI Supplier
- Temperature Explained: The Dial That Sets How Predictable an AI Model Is
- Guardrails Explained: Rules Enforced Around an AI Model, Not Inside It
- Benchmarks Explained: Why a Test Score Is Not Your Own Result
- Agent Memory Explained: How an AI Assistant Remembers You Between Chats
- MCP Explained: The Shared Plug That Connects AI Models to Tools
- Quantization Explained: How a Large AI Model Is Shrunk to Fit
- Parameters Explained: Where an AI Model’s Knowledge Lives
- Scaling Laws Explained: Why AI Labs Keep Building Bigger
- Synthetic Data Explained: When a Model Writes Its Own Training Examples
- Transformers and Attention Explained: How AI Reads Every Word at Once
- Context Window Explained: How Much Text an AI Model Can Keep in View
- Prompt Injection Explained: When Text a Model Reads Gives the Orders
- Inference Explained: The Cost Paid on Every AI Answer
- Multimodal Explained: AI Models That Work With Images, Sound and Video
- AI Agents Explained: From Answering to Doing
- Open Weights Explained: Rent the Model or Run It Yourself
- Gross Margin Explained: What an AI Company Keeps From Each Dollar
- Usage-Based Pricing Explained: Paying for Work, Not for Seats
- Total Cost of Ownership Explained: Why the Cheap Robot Is the Expensive One
- Free Cash Flow Explained: Profit on Paper, Cash in the Bank
- Few-Shot Prompting Explained: Why Showing a Model Examples Beats Describing
- Knowledge Cutoff Explained: The Date Where an AI Model Stops Knowing
- Overfitting Explained: Why Memorizing Is Not Learning in AI
- Model Routing Explained: Sending Each Question to the Right AI Model
- GPUs Explained: Why AI Runs on a Chip Built for Video Games
- Data Labeling Explained: The Human Work Behind an AI Model
- Churn Explained: The Customers Who Leave Through the Back Door
- Customer Acquisition Cost Explained: The Price of a New Customer
- Operating Leverage Explained: Why Profit Grows Faster Than Sales
- Burn Rate Explained: How Fast Cash Goes and How Long It Lasts
- Computer Use Explained: When an AI Agent Operates the Screen
- Multi-Agent Systems Explained: One Agent or a Team
- Outcome-Based Pricing Explained: Paying for the Result
- Agentic Commerce Explained: When the Shopper Is an Agent
- Sovereign AI Explained: Who Controls the Model and the Data
- Context Engineering Explained: What a Model Sees Before It Answers
- Forward Deployed Engineers Explained: The Engineer Who Moves In
- On-Device AI Explained: A Model in Your Pocket
- Physical AI Explained: When AI Gets a Body
- Neoclouds Explained: Renting the Chips by the Hour
- Prompt Caching Explained: Why You Should Not Pay Twice to Read the Same Page
- Structured Output Explained: Why Programs Need a Form, Not a Paragraph
- Model Deprecation Explained: What Breaks When the Model Under You Changes
- The Jevons Paradox Explained: Why Cheaper AI Can Mean a Bigger Bill
- Take-or-Pay Explained: Paying for AI Chips Whether You Use Them or Not
- Least Privilege Explained: Giving an AI Agent Only the Access Its Task Needs
- Rate Limits Explained: Why an AI Product Can Stall in Its Busiest Minute
- Red Teaming Explained: Attacking Your Own AI System Before Someone Else Does
- Shadow AI Explained: The AI Tools Your Company Cannot See
- Data Flywheel Explained: When Using a Product Makes It Better









