> ## Content Index > Fetch the complete content index at: https://the-daily-constraint.ghost.io/llms.txt > Use this file to discover other available public pages before exploring further. # Your Average Is Hiding the Problem You Asked AI to Find - URL: https://the-daily-constraint.ghost.io/your-average-is-hiding-the-problem/ - Published: 2026-09-27T07:23:26.000Z - Updated: 2026-09-27T07:23:26.000Z - Description: You hand AI your hourly run rate. One clean number. It builds you a capacity plan that looks solid. Then a real peak hits. The plan falls apart in the first hour. - Author: Andrea Bullock You hand AI your hourly run rate. One clean number. It builds you a capacity plan that looks solid. Then a real peak hits. The plan falls apart in the first hour. Nothing was wrong with the math. The number you fed it was never real to begin with. It was an average. An average is the one number built specifically to erase the problem you were trying to find. **What an Average Really Throws Away** ![](https://storage.ghost.io/c/6a/5a/6a5a81c1-c40d-4db0-af99-e0cedc71c0c2/content/images/2026/09/B1-8.png) Every hour on your floor is different. A smooth hour, a rough one with three micro-stops, a changeover that ran long, a shift handoff where nobody caught the gap for ten minutes. Average those hours together and every one of those real events disappears into a single tidy number. The average doesn't describe your floor. It describes a floor that never existed on any single real day. Specifically, averaging erases: - Micro-stops, the ten-second and thirty-second stops nobody logs individually. - Changeover friction, the extra minutes a changeover runs long when tooling isn't quite ready. - Shift handoff lag, the gap between one crew stepping off and the next one really running at speed. None of these show up in the average. All of them show up the moment you need capacity to hold during a real peak. **There's a Real Term for This** Industrial engineers already have language for the trap. Plans built on the number from the equipment manual use what's called theoretical capacity, the maximum possible output with zero stops, zero changeovers, zero defects. That number doesn't come from your factory. It comes from a manual. The number that should get used instead is demonstrated capacity, the real, historical, measured output of a line, with every loss already baked in. If a line rated for 200 units an hour has historically run at 160, its demonstrated capacity is 160. Planning against 200 builds a 25 percent error into the schedule before the shift even starts. A smoothed average sits somewhere between those two numbers, closer to the fiction than the reality. It's exactly what most people hand an AI tool without thinking twice about it. **The River That's "On Average" Three Feet Deep** There's an old illustration economists still use for this exact mistake. A statistician tries to cross a river that's three feet deep on average. He drowns anyway, because parts of it run six feet deep. [The idea has a name](https://hbr.org/2002/11/the-flaw-of-averages?ref=the-daily-constraint.ghost.io), the flaw of averages. It applies just as directly to a capacity plan as it does to a river crossing. The average tells you almost nothing about the part that could sink you. Your peak demand hour is the six-foot section of the river. A plan built on the average was never built to survive it. **Why Averaging Also Hides the Real Bottleneck** ![](https://storage.ghost.io/c/6a/5a/6a5a81c1-c40d-4db0-af99-e0cedc71c0c2/content/images/2026/09/B2-6.png) There's a second trap sitting right next to the first one. Averaging capacity across an entire line, not just across time, hides which station is really holding everything else back. If your filler runs 200 units an hour but your labeler tops out at 150, the line's real capacity is 150, full stop. Average the two stations together. You get a number describing a line that doesn't exist, one where the bottleneck's constraint has been smoothed away along with everything else. **How to Tell Your Data's Already Been Averaged** A few tells show up before you've even asked for a capacity number. - The number handed to you is a single figure with no range attached. - Nobody can tell you the worst hour on record, only the typical one. - The data came from a monthly or weekly report instead of a raw hourly log. Any one of those means you're working with a smoothed number, whether anyone meant to hand you one or not. **The Prompt: Force It to Ask for the Real Numbers** **1\. Set the Role** - Tell it to act as a capacity planning analyst who refuses to build a plan on a single averaged number. **2\. Hand It the Data** - Your hourly run rate broken out hour by hour, not pre-averaged. Include known micro-stops, changeover times, and shift handoff windows if you have them. **3\. Set the Constraints** - It must ask for the actual variance, not just the mean, before proposing a capacity number. - It must flag if the data it received is already smoothed or aggregated. - Any capacity recommendation must state what happens during the worst observed hour, not just the average one. **4\. Define the Output** - A capacity number based on demonstrated performance, not theoretical maximum. - The worst-case hour identified specifically, with its cause if known. - A clear flag on whether the plan can survive that worst-case hour, or only the average one. **What Comes Back on the Run Rate Example** Feed it a week of hourly output for a line that averages 160 units an hour. **The average-only plan** - Capacity recommendation: 160 units an hour, based on the weekly average. - What it misses: the two hours per shift that regularly drop to 110 due to changeover friction. **The variance-aware plan** - Capacity recommendation: 160 units an hour on a typical hour, 110 during known changeover windows. - What changes: any commitment made against this line has to account for the 110 number during those specific hours, not the flattering 160. Same data. Same line. One plan survives a real changeover. The other quietly assumed changeovers don't happen. **A Second Example: Staffing, Not Just Machines** The same trap hides in a headcount plan just as easily as a run rate. **The average-only version** - Average attendance over the last quarter: 92 percent. Staffing plan built around a 92 percent showing rate. **The variance-aware version** - Attendance on the Monday after a holiday weekend has historically dropped to 78 percent, three separate times this year. - A staffing plan built on 92 percent has no cushion for a day that's happened three times already and will happen again. Same mistake, different number. An average headcount plan works fine on an average day. An average day was never the one that really needed the plan. **You Don't Need to Fix Every Average at Once** Not every smoothed number is worth chasing down immediately. Some averages genuinely don't matter much, a slight blur on a line that never runs near capacity anyway costs nothing real. Prioritize the averages sitting closest to a real commitment. A capacity number feeding a customer delivery promise deserves the real hourly spread. A capacity number used for a rough internal estimate can probably stay smoothed a while longer. The test is simple: if this number is wrong, who finds out, and how expensive is that discovery? The more expensive the surprise, the sooner that average needs replacing with the real spread underneath it. **Where This Connects** This is the same math-versus-reality gap covered in [AI Can Balance the Line. It Can't See the Line.](https://the-daily-constraint.ghost.io/ai-line-balancing-cant-see-the-floor/), a tool optimizing a version of the floor that only exists in clean numbers. It's also the same idea behind [You Didn't Fix the Bottleneck: How AI Predicts Where It Moves Next](https://the-daily-constraint.ghost.io/you-didnt-fix-the-bottleneck-how-ai-predicts-where-it-moves-next/), since an averaged capacity number is exactly the kind of smoothing that hides which station is really holding the line back. **Before You Trust Any AI Capacity Number** Ask what number went in. An average erases exactly the information a real capacity plan depends on. Hand over the real hourly spread instead, worst hours included. The plan that comes back will be one that can survive a real peak instead of just looking good on a slide. The river isn't three feet deep everywhere. Plan for the six-foot section, not the average one. If you want a repeatable version of this check built into your regular AI workflow, that's exactly the kind of pattern [the Operations Manager's AI Prompt Field Guide](https://the-daily-constraint.ghost.io/24-ai-prompts-that-actually-survive-contact-with-your-floor/) is built to catch before it costs you a real commitment. *Comment below* with the last capacity plan that looked perfect on paper and fell apart the first time it got tested for real.