The Curriculum Is Not the Teacher

Those two things overlap quite a bit. But they are not the same thing.

I like OpenSciEd. I like the ambition of it. Students are supposed to experience science as something people do: notice something strange, ask questions, gather evidence, revise ideas, argue, model, and slowly build an explanation. That vision is much closer to the classroom I want than a march through vocabulary slides, worksheets, and a test on Friday.

But after teaching these units repeatedly, I have become more comfortable admitting that a high-quality curriculum can still ask too much of a particular moment, repeat an idea longer than my students need, bury the important thinking under procedure, or spend twenty-five minutes earning an insight that could have been developed more clearly in ten. When that happens, I change it.

What I am trying to preserve

OpenSciEd describes its instructional model as a coherent storyline driven by students' questions about phenomena. Students investigate, connect ideas across lessons, problematize their current explanations, and eventually put the pieces together. That matters to me. The storyline is not decorative. It gives the work a reason to exist.

The National Academies' Framework for K-12 Science Education makes a similar case for science learning that integrates knowledge with scientific and engineering practices. Students should not merely know scientific facts; they should learn to use ideas to investigate, model, explain, argue from evidence, and make sense of the world.

Separate the purpose from the procedure

A published lesson contains both a destination and a route. Those are easy to confuse. The route may include a discussion protocol, a data set, a card sort, an investigation, a notebook entry, a consensus model, and a navigation routine. The destination is the new idea students are supposed to be able to use when they walk out of the room.

Experience has made me much more willing to separate the two. What are students actually supposed to figure out? What evidence makes that conclusion reasonable? What misconception needs to move? What question should remain unresolved so the next lesson has somewhere to go?

Inquiry does not require me to hide information

Earlier in my career, I sometimes treated telling students something as a small defeat. If the lesson was inquiry-based, surely the students were supposed to discover the idea themselves.

I do not believe that anymore.

There are things worth investigating and things worth explaining. There are productive struggles that change how students think, and there are unproductive struggles that mostly consume working memory, time, and patience.

Research complicates the usual inquiry-versus-direct-instruction debate. Rosenshine emphasizes manageable steps, modeling, questioning, guided practice, checking for understanding, and movement toward independence. Kirschner, Sweller, and Clark similarly argue that novices often learn poorly from minimally guided instruction because they do not yet possess the schemas experts use to navigate complex problems.

That does not mean students should sit quietly while I explain the world to them. It means the rigor does not have to come from making every fact difficult to obtain.

Increasingly, my preferred rhythm looks like this:

A 66-minute period has an economy

The new A/B schedule made a problem impossible for me to ignore: instructional time is finite, and every decision has an opportunity cost. Ten extra minutes on one discussion are ten minutes I cannot spend on a dissection, a better debrief, a retrieval activity, a student conference, or an idea I have been complaining about for years that I never have time to teach.

This is not about racing through the curriculum. It is about buying back time so I can spend it where it matters.

Coherence beats completeness

One of the strange things about a well-designed curriculum is that the coherence may be obvious to the adult reading the teacher edition and nearly invisible to the twelve-year-old experiencing it across several weeks.

OpenSciEd emphasizes navigation: students should be able to connect what they are doing now to the questions and ideas developed earlier in the storyline. I have become more explicit about helping them do that.

I no longer see that narration as stealing ownership from students. When it is done well, it gives them the map they need to participate in the journey.

Accessibility is not the same as lowering the bar

The particular group of students sitting in front of me matters. Across a school day I may teach honors students, general education students, students in ICS, students receiving resource support, multilingual learners, strong readers, reluctant readers, kids who process quickly, kids who need repetition, kids who love science, and kids who arrived in September already convinced that they are bad at it.

They do not necessarily need different science. They often need different access to science.

Assessment should tell me something

I am trying to become less interested in assessments as point-generating machines and more interested in them as information.

OpenSciEd's assessment philosophy treats assessment as part of sensemaking: an opportunity to uncover students' ideas, see how those ideas change, and determine what students can do with their developing understanding.

The uncomfortable part: every modification costs something

There is a danger in writing about curriculum modification: it can quickly become a long victory lap in which every change I made was obviously brilliant.

That is not how this works.

The teacher is part of the curriculum

The biggest philosophical change for me may be that I no longer see professional judgment as contamination of curriculum fidelity.

A curriculum brings research, design, sequencing, common tasks, and a perspective larger than my own classroom. That deserves respect. My classroom brings a different form of evidence: what these students understood, where they got lost, what took twice as long as predicted, what became unforgettable, what never landed, and what I wish I had time to teach.

Experience helps me interpret the collision between the two.

The teacher is part of the curriculum: continued

Experience is not automatically correct. One reason for writing this series is to force myself to explain instincts that have become automatic.

So for every lesson I modify, I want to be able to answer:

1. What was the original lesson trying to accomplish?
2. What happened when I actually taught it?
3. What did I preserve?
4. What did I cut, combine, add, or explain directly?
5. What did the modification gain?
6. What did it sacrifice?
7. Would I make the same trade again?

If I cannot answer those questions, I probably have not thought hard enough about the modification.

What I am actually trying to build

That requires something between scripted fidelity and improvisation.

So this series will not be a collection of shortcuts for getting through OpenSciEd faster.

Sometimes my answer will be to leave the lesson almost untouched. Sometimes it will be to cut half of it. Sometimes I will add direct instruction. Sometimes I will protect an investigation even when it wrecks the pacing guide.

Research behind the argument