Business Pill · The average hides the slow ones
A percentile is the wait that a stated share of people beat once everyone is lined up from fastest to slowest. It shows what an average hides: the few who wait the longest.
A short explainer video, under a minute. The manager, the robot and the customer are an illustration, and the numbers in it are round numbers for illustration.
At a glance
What a Percentile Is
The average hides those customers. So the video lines everyone up, fastest to slowest.
A Worked Example
The video's illustration uses round numbers. The average says two seconds.
Why It Matters
The video turns this into one question: who waits longest, and are we counting them?
The Short Answer
Picture a manager who checks how long customers wait at the help desk. The average wait is two seconds, and she is pleased.
But a few customers wait twenty seconds, and they are the ones who leave.
What a Percentile Is
The average hides those customers. So the video lines everyone up, fastest to slowest.
The wait that most people beat has a name. It is called a percentile.
A Worked Example
The video’s illustration uses round numbers. The average says two seconds. The seventy fifth percentile says five. And the slowest few wait twenty.
The same crowd of customers gives three different answers, depending on which one you read.

The Idea on One Board
Illustration: the wait, in seconds
Average 2
75th percentile 5
Slowest few 20
The honest limit
The Honest Limit
Even a percentile hides what lies beyond it. So the video’s advice is to pick the one that matches the pain.
Why It Matters
The video turns this into one question: who waits longest, and are we counting them?
Its takeaway is short. An average hides the slow ones, so look at the slow end.
The key insight: An average hides the slow ones. So look at the slow end.
The honest limit
But even a percentile hides what lies beyond it.
So pick the one that matches the pain.
Where This Shows Up in AI Business Today
From our news coverage
Anthropic: claude.ai 3x Faster in Two Weeks, 3,000+ Changes
One recent AI product claim is quoted at a percentile. Our report on Anthropic’s engineering post says Anthropic states that at the 75th percentile the time to a typeable page on a fresh load of claude.ai went from 3.1 seconds to 0.55, and that starting a new Claude Code session went from 0.8 seconds to 0.3. Those are Anthropic’s own results from a post dated 23 September, 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
- Who waits longest, and are we counting them?
Related Business Pills
See It in the News
Anthropic: claude.ai 3x Faster in Two Weeks, 3,000+ Changes. 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
- Sale-Leaseback Explained: Sell the Asset, Keep Using It
- Mixture of Experts Explained: Many Specialists, Few at Work
- Data Quality Explained: Fewer, Better Examples
- Financial Conditions Explained: Several Prices Pulling at Once









