How I Boil Down an OpenSciEd Lesson Plan

Start with what students will figure out. Then build a day that gives them time to do it.

By William P. Pirl | Pirl Experimental — Education & Consulting

When I open an OpenSciEd lesson for the first time, my eyes go straight to the bullets under “What students will figure out.”

The title gives me a direction. The teacher edition gives me the details. But those bullets are usually where I begin to see the lesson’s biggest ideas. Before I work through every discussion prompt, slide, and transition, I want to know what students are supposed to understand by the end.

I have taught OpenSciEd long enough to know that its timing can be tricky in my classroom. Something listed as six minutes can take ten before anyone has done anything wrong. Materials need to move. Students need directions again. A good question opens a conversation. At the beginning of the year, even getting a notebook organized takes time.

Here is how I work through a lesson so I can protect its purpose and make the day manageable.

First, find what students are supposed to figure out

I read those statements and look for the ideas that hold the lesson together. I notice key vocabulary, but I also notice the relationships: what causes what, what changes, what students will compare, or what they will need to explain.

Then I try to finish one sentence:

By the end of this lesson, students should be able to explain or show ______.

That sentence gives me something to plan around. If all I have is a list of terms, I need another pass. Knowing a word and using an idea are different accomplishments.

I also distinguish the destination of the whole unit from the job of this particular lesson. An anchoring lesson might need to surface ideas and unanswered questions. It does not need to teach the complete scientific explanation before students have investigated anything.

If the expected depth is unclear, I check the adopted state standards, clarification statements, assessment boundaries, and local course requirements. I want to teach the essential content and prerequisites well. Extra detail should earn its place in the time available.

Next, read the planning snapshot with your actual schedule beside it

The next place I go is the planning snapshot. How many class periods does the lesson assume? How long are those periods? What does that mean in my room?

For the Unit 8.1 Lesson 1 snapshot I am working from here, the plan spans three 45-minute periods and lists 15 segments. That is 135 minutes. Two of my 66-minute blocks give me 132 minutes.

On paper, that looks close enough to preserve most of the lesson’s work. But the three-minute difference is not the main issue. Fifteen segments mean a lot of changes in what students are doing. Not every segment requires a physical transition, but each is another place where directions, attention, materials, or discussion may need to shift.

At the beginning of eighth grade, I would start by giving this launch two blocks. Then I would plan for the students who will actually be there. Do they know the notebook routine? Have they used a Scientists Circle? Are we still learning how to work with materials and respond to one another?

What I sometimes call “fluff time” is really a buffer for classroom reality. I want that time visible in the plan instead of silently borrowing it from the most important activity.

Let the student documents and slides show you the work

After I scan the lesson, I open the student documents. I look for the main page students are supposed to complete: the initial model, data table, investigation record, or explanation.

Then I look through the slides. I want to see what students will actually be looking at and doing. Which slides introduce evidence? Which explain directions? Which launch a discussion? Where does the teacher edition’s long description turn into one substantial piece of student work?

I let the documents and slides help me interpret the lesson. I still read the relevant teacher guidance, especially preparation, safety, anticipated ideas, and the purpose behind a discussion. The slides are a map of the student experience, not the entire teaching plan.

In 8.1, the publicly available initial-model handout asks students to identify two colliding objects and explain what they think happens to the materials at two moments: first contact and a split second later. That is a substantial thinking task. Looking at the actual handout makes it easier to see why students need time to develop their ideas. View the OpenSciEd handout.

Now I can ask a more useful planning question: What activity deserves the largest share of today’s time?

Read the segments for purpose, then make decisions

As I scan the segments, I am looking for what each one contributes. I mark things to keep, combine, move, shorten, or defer. I also mark anything I need to verify before changing it.

In this example, I want to keep the opening collision experience. It gives students something interesting to react to and something concrete to explain. I would check the current teacher directions and safety procedures before using any breaking-material demonstration; the planning idea is to preserve the phenomenon, not improvise a way to smash things.

The extended related-phenomena sharing is something I would consider moving toward the end. Students’ experiences matter, and I want those connections available later. But I would rather collect them during a closure or return to them next class than let an extended opening share-out consume the time students need for initial models.

I would also bring together the work on factors and variables. Have students identify and record possible factors, then immediately share and build the class poster. I would rather complete that connected piece of thinking while it is fresh than stop and restart it later.

Before moving a segment, I check whether a later task depends on it. Moving an activity should not leave students missing evidence, a direction, or an idea they need to participate.

Give the main activity a protected block

For the first day, I would protect initial modeling. My first rough thought is about 20 minutes for the opening experience, time to identify and share factors, and as much useful modeling time as I can give students.

Once I put that on a clock, I have to make a choice. Twenty minutes for the opening, ten for individual factors, ten for sharing, twenty for models, and five for closure uses 65 minutes. That leaves one minute for everything else. It is not much of a beginning-of-year buffer.

Here is a more workable starting plan. These are my proposed allocations, not the published pacing.

This is a starting point, not a promise that every class will fit it. If setting up notebooks needs longer, I would prepare part of the setup ahead or reduce the opening share-out. I would not automatically take those minutes from modeling.

If students finish their models early, I can return to related phenomena. That makes the additional discussion available without allowing it to crowd out the work I meant to prioritize. I would schedule a brief return to those examples in the next class if we do not reach them.

On day two, let the consensus discussion do its job

I would probably begin the second block in a Scientists Circle. For students who already know the routine, five minutes may be enough to revisit the norms and choose one to practice. If the class is new to it, I would budget more; eighth grade by itself does not guarantee that experience.

Then I want students comparing models and developing an initial consensus model. I would give that a substantial block and let the discussion continue while students are adding ideas, identifying disagreements, and clarifying what they do not yet understand. Repeating the same point is a cue to move the discussion forward.

If the discussion genuinely needs more time, I can use some of the buffer and collect a smaller number of questions. I still want every student to have a way to contribute. The initial consensus model should preserve uncertainty; I am not trying to turn the first lesson into the unit’s final explanation.

Keep the questions. Simplify how you collect them.

A Driving Question Board can take a great deal of time to assemble. I would consider simplifying the collection and organization while preserving students’ questions and the class’s responsibility for making sense of them.

One option is a Google Form with three open-response fields: Question 1, Question 2, and Question 3. Ask for their strongest question first. Make the additional questions optional if time is tight.

I could copy the question columns into an approved AI tool and ask it to propose groups of related questions. I would remove names and identifying details first. The useful job for AI is clerical organization: propose themes, flag duplicates, and keep unusual questions visible.

It should not decide which questions deserve to exist or invent questions students never asked. I would review the grouping, retain the original questions, and bring the categories back to students to rename, move, split, or challenge. They still need to recognize their thinking in the board.

From there, I could write questions on index cards or cardstock, or print the grouped questions large enough to read. In the next lesson, we can identify which questions an investigation might help answer. That is what makes the board useful after it is assembled.

If I have only five minutes, sticky notes work. Students write one priority question, post it, and we return to sorting next class. I would rather preserve their questions quickly than rush through a complicated procedure and lose them.

Finish with a plan you can explain in a few sentences

By the end of my first pass, I want to know the learning goal, the main student product, the activity that gets the most time, the pieces I am combining or moving, and the evidence that will tell me whether students are ready for the next lesson.

For this launch, that means preserving the phenomenon, individual models, a shared initial explanation, and student questions. The procedure can change around those priorities.

That is the purpose of Creator Tool 07: The First-Pass Lesson Checklist. It follows the order I actually use: figure-out statements, the planning snapshot, the segments, the student documents and slides, and then a realistic classroom sequence. Creator Tool 06 helps decide what learning to prioritize; Tool 07 helps turn the lesson in front of you into a teachable plan.

If you want help working through a lesson, send the teacher plan, student documents, slides, and the time you actually have. I can help identify the main work, simplify the transitions, and build the notebook page, mini-lesson, or question-collection tool that makes the plan usable. Discuss a resource with Pirl Experimental.

About this example: This worked example is based on William Pirl’s narrated walkthrough, including the three-period, 15-segment planning snapshot. The public OpenSciEd 8.1 overview confirms the collision anchor and role of student questions; the linked initial-model handout confirms the main modeling task. The schedules are proposed adaptations, not a report of a completed classroom trial. Match segment names, preparation, and safety directions to the edition you teach.