Here's what everyone agrees on: traditional curricula are too rigid. Students need flexibility. They need real-world relevance. They need to build competencies, not just memorize facts. Schools should embrace mistakes as learning opportunities. STEM should challenge rather than bore.
These aren't wrong observations. But the consensus around competency-based learning has become so comfortable that nobody's asking the harder question: what does this shift actually break?
The competency movement promises liberation from the tyranny of seat time and standardized benchmarks. Instead of forcing all ninth graders through algebra at the same pace, competency frameworks let students advance when they demonstrate mastery. On paper, this sounds revolutionary. In practice, it's revealing some uncomfortable truths about how we've organized schooling.
Start with the obvious problem: competency frameworks require robust assessment infrastructure. Schools need teachers trained to evaluate mastery in granular, consistent ways across classrooms. They need systems to track which competencies students have actually acquired. They need time for this work. Most schools don't have any of this. The result? Competency frameworks often become a repackaging of the same old thing, with new vocabulary and slightly more flexibility, but without the underlying systemic change.
But there's something subtler breaking here too. Traditional curricula, for all their flaws, shared something: a common sequence. When you teach algebra before calculus, you're building on established scaffolding. When you organize history chronologically, you're creating connective tissue between events. Yes, this approach is rigid and excludes relevant context. But it also creates something that competency frameworks struggle to replicate: shared intellectual experience and deliberate progression toward complexity.
Competency-based models tend to atomize knowledge. A student "masters" analyzing primary sources, then moves on. Another student demonstrates competency in data visualization. But what happens when they need to analyze primary sources AND visualize data to understand a social phenomenon? The framework doesn't always explain how competencies interact or build toward deeper thinking.
The real concern isn't that competency frameworks are wrong. It's that we're adopting them without acknowledging what we're trading away. We're breaking the assumption that curriculum should have intentional architecture.
Consider the recent conversation about making STEM lessons more challenging, or using mistakes productively in math classrooms. These are valuable insights. But they work best within a coherent curriculum structure that gradually builds conceptual understanding. A student needs to struggle productively with one concept before moving to the next. That requires sequence, not just a menu of achievable competencies.
This matters because education has limited resources and limited time. Every pedagogical choice excludes something else. If we organize entirely around competencies, we're implicitly deciding that common sequencing, broad narratives, and building toward intellectual complexity matter less.
Maybe that's right. Maybe our obsession with curriculum architecture was always overblown. Maybe students are better served by a flexible system where they acquire skills on demand.
But let's be honest about the trade-off. The comfortable consensus around competency-based learning is selling a version of educational liberation that requires substantial systemic infrastructure most schools don't have. And it's replacing a system that, whatever its rigidity, at least attempted to construct knowledge architecturally.
The better question isn't whether competency frameworks are good or bad. It's whether we're willing to invest in the systems, assessment capacity, and teacher training that would actually make them work. And whether we understand what older models of curriculum were actually doing for student thinking that we might be breaking in the rush to move beyond them.