The Jagged Frontier: Why AI Fails at Easy Things and What It Means for Your Product

A common assumption in AI product development goes something like this: if a model can handle a hard task, it can definitely handle an easier one nearby. This assumption is wrong, and it's responsible for a category of production failures that no amount of benchmark reading prepares you for.

The research term for the underlying phenomenon is the "jagged frontier" — AI's capability boundary isn't a smooth line that hard tasks sit outside of and easy tasks sit inside. It's a ragged, unpredictable shape. AI systems can write production-grade database query optimizers and still miscalculate whether two line segments on a diagram intersect. They can pass PhD-level science exams and fail children's riddle questions that involve spatial relationships. They can synthesize 50-page documents and then confidently hallucinate a summary of a paragraph they just read.

This jaggedness isn't a bug that will be patched in the next release. It reflects something structural about how these models learn, and it has direct consequences for how you should design, test, and ship AI-powered features.

Where the Concept Comes From

The term "jagged technological frontier" was coined in a field experiment conducted by researchers from Harvard Business School, MIT, and Wharton, published in Organization Science in 2025. The study enrolled 758 knowledge workers from Boston Consulting Group and had them complete realistic management consulting tasks — market analysis, synthesizing research, writing reports.

The finding everyone quotes: AI-assisted consultants completed tasks 25% faster, produced outputs rated 40% higher quality, and improved their success rate by 12.5 points. But the finding that matters for product teams is the second one: for tasks that fell outside the AI's capability frontier, consultants who used AI anyway were 19 percentage points less likely to produce correct solutions than consultants who worked without AI at all.

AI didn't just fail to help on those tasks. It made experienced professionals perform worse than they would have alone. The confidence and fluency of AI output masked the incorrectness.

What "Jagged" Actually Means in Practice

The capability frontier is not defined by task complexity in any way humans intuitively understand. The jaggedness comes from the distribution of training data, the nature of the objective function, and the specific failure modes of next-token prediction.

A few examples that illustrate the shape:

Where AI routinely exceeds human expert performance:

• Writing, editing, and business ideation (AI-generated startup ideas rated better than business school students' by independent judges)
• Emotional support and reappraisal (performs better than 85% of humans in controlled studies)
• Reading comprehension on well-formatted documents
• Code generation for common patterns (state-of-the-art agents now exceed 80% on SWE-bench)
• Mathematical competition problems (o1-preview outperformed GPT-4o by 43 points on AIME 2024)

Where AI fails in ways that surprise practitioners:

• Spatial reasoning: models that generate flawless geometry proofs fail when asked whether two rendered lines cross on an actual image
• Sequential planning: Calendar scheduling, maze navigation, and constraint satisfaction problems show minimal improvement even with extended reasoning
• Encoding and format edge cases: Both o1 and o3 fail silently on CSVs with hidden encoding issues
• Visual perception of thin or suspended objects: Waymo's fifth-generation autonomous vehicle system was recalled after 1,212 vehicles collided with thin barriers — chains, utility poles, suspended gates — that its perception stack couldn't reliably detect despite excellent performance on standard obstacles

The pattern is not random. Tasks that have abundant, consistent training examples tend to sit inside the frontier. Tasks that require grounded, physical-world reasoning, or careful sequential logic without shortcuts, tend to sit outside it. But the exact shape is not predictable from first principles, which is the core problem for product teams.

The Product Design Traps

Loading…