What project-based learning actually requires
The structure, not the enthusiasm, is the variable
Project-based learning is frequently reduced to "doing projects". The distinction that matters is structural, and REALM's program illustrates it.
- Sustained inquiry over coverage. A genuine project runs for weeks, and its driving question is one the teacher cannot fully answer in advance.
- A public product. Work is shown to an audience beyond the classroom. The audience is what creates the stakes.
- Embedded academics. Content standards live inside the project rather than beside it. This is the hardest design problem, and the reason most implementations stay shallow.
- Tolerance for productive failure. Timetables, grading and school culture have to absorb prototypes that do not work.
The research literature on project-based learning and its relatives — inquiry learning, design-based learning, maker education — points consistently in one direction: well-structured programs match or beat conventional instruction on content mastery and beat it clearly on engagement and transfer, while poorly structured ones underperform both. The variable is structure.
REALM's closure is not evidence against the model. The school's finances failed; the pedagogy is the part that other schools went on to adopt.