Treating curriculum as infrastructure, not content

"Content" is a word that lets institutions underinvest in curriculum without feeling like they're underinvesting. Content gets written, reviewed once, and shipped. Infrastructure gets versioned, tested against real conditions, and revisited on a schedule — because infrastructure is expected to still be load-bearing five years from now.

A curriculum built like infrastructure has the same properties software does: a clear owner, a change log, a way to roll back a bad revision, and a test suite — in this case, classroom pilots — before a wider rollout. It's slower to produce than content. It's also still standing when a cohort of students changes, a teacher turns over, or a ministry updates its standards.

The schools we work with that struggle most with curriculum aren't the ones with the least material — they're the ones whose material was never built to survive contact with next year.