Everyone in education policy circles agrees on project-based learning now. It's the safe bet. Students designing backpacks to learn math, building robots to preserve Indigenous languages, tackling real problems instead of worksheets. The consensus feels progressive, practical, unassailable.
So let's question it anyway.
The real issue with PBL isn't whether it works. The real issue is what it obscures: the widening gap between schools that can actually execute ambitious project work and schools that cannot.
We hear the success stories. A student learns geometry through authentic design. Another discovers purpose in engineering for community benefit. These are real wins. But here's what the consensus glosses over: these victories are clustered. They happen in schools with adequate funding, teacher preparation time, materials budgets, and administrative support for experimentation. They happen where "let's redesign the math curriculum around real projects" doesn't mean cutting something else to the bone.
The uncomfortable truth is that project-based learning, when done well, is expensive and labor-intensive. It requires teachers who understand both content and pedagogical flexibility. It requires time for planning, collaboration, and iteration. It requires materials, tools, technology, and sometimes community partnerships. It requires the kind of institutional stability that permits risk-taking.
And we're not providing that equally.
Meanwhile, schools operating on razor-thin margins are being told they should embrace PBL too. The message is that this approach is universally beneficial, scalable, the future of K-12 instruction. But without the infrastructure, without the resources, without the teacher prep, "project-based learning" becomes a hollow mandate. Teachers get a professional development afternoon. They improvise. They do their best with nothing. The projects become window dressing on the same constrained system.
That's not innovation. That's equity theater.
Here's what breaks next: the pretense that pedagogical solutions are content-neutral. They're not. They're infrastructure-dependent. A brilliant teaching method means nothing if the conditions don't support it.
We've seen this cycle before. Technology in classrooms was supposed to transform everything. Then we learned that handing tablets to under-resourced schools while doing nothing else changes very little. Competency-based progression was going to revolutionize pacing. Then struggling districts tried to implement it without the assessments, the training, the curricular coherence it required.
Project-based learning will follow the same arc if we're not careful. The early adopters will thrive. They'll publish their results, write their case studies, speak at conferences. The broader field will nod along, convinced this is the answer. Meanwhile, the schools that needed help the most will be left holding a mandate they can't execute.
This isn't an argument against PBL. It's an argument against pretending that good pedagogy transcends structural inequality. It doesn't.
The real work isn't designing better projects. It's asking what needs to be true in a school before project-based learning becomes possible rather than performative. It's asking who gets access to the conditions under which this approach actually works. It's admitting that implementing ambitious instruction at scale requires ambitious investment.
The consensus says project-based learning is the future. The better question is: Future for whom? And what are we not funding while we're busy celebrating the schools that figured out how to do this despite the system, not because of it?
Until we answer that, we're just applauding islands of excellence while the rest of the mainland gets talking points.