run a simulator or tool activity so students reason about what they see rather than click until something happens.
A simulator can teach a great deal or nothing at all. Research on simulations in science and mathematics classrooms tends to reach the same conclusion: open-ended exploration without structure leaves many students clicking without learning, while activities that ask students to commit to a prediction, observe deliberately and explain the difference produce understanding. Every sim block in the charter courses is written as a guided task for this reason. It tells students what to set, what to observe, what to record and what question the observation answers. Your job is to protect that structure.
The routine. Use Predict, Observe, Explain with every activity. Predict: before touching the tool, each student writes what they expect and why. The prediction is the most important step, because it creates the gap that the observation fills. Observe: students carry out the task’s steps and record what happens, including numbers, sketches or screenshots. Explain: students reconcile the observation with the prediction in writing, and the class discusses the explanations, not the clicks.
Time boxes. Give a short, bounded period of free play at the start of a new tool, perhaps three to five minutes. Students will explore anyway; a named window makes it legitimate and ends it. Then move to the task.
Discourse. The Mathematical Discourse Lab, the Statistical Discourse Lab and the science labs all ask students to argue from evidence. A tool gives every student the same evidence. Ask students to point at what they saw, to predict what would happen if one setting changed, and to test that prediction. MP.5 asks students to use tools strategically, which includes knowing a tool’s limits: a simulation is a model, and students should be able to say what it leaves out.
The non-tool route. Every activity in the curriculum has a printed or hands-on alternative in its task text. Use it for students without reliable access, and also, occasionally, for everyone: doing the reasoning without the tool shows whether students understand the idea or only the interface.
Predict, Observe, Explain
The prediction creates a question the tool can answer; the explanation turns the observation into understanding.
- Pose the task’s question. Students write a prediction and a reason before opening the tool.
- Allow a short, named free-play window for a new tool.
- Students follow the task steps and record observations: numbers, sketches or screenshots.
- Students write how the observation matched or contradicted their prediction, and why.
- Discuss explanations as a class. Ask what would change if one setting changed, and test it.
- Close by naming one thing the simulation leaves out of the real situation.
Look-fors during a tool activity
| What you see | What it means | What to do next |
|---|---|---|
| Students clicking rapidly with nothing written | Exploration without a question | Pause the class; ask each student to write a prediction first |
| Screenshots with no interpretation | Recording without explaining | Ask: what does this show, and did you expect it? |
| “The sim says so” | The model treated as reality | Ask: what does the simulation leave out? |
| A few students waiting on a slow device | Access gap | Move them to the printed route immediately; do not wait |
Which step of Predict, Observe, Explain is most often skipped, and most important?
How confident are you that you can run a tool activity with Predict, Observe, Explain?