1. Predict
Before the run, name the changed input, expected direction, affected metrics, and a reason. A prediction is not graded for being correct.
Free printable classroom resource
Help students slow down between runs, connect decisions to evidence, and show individual learning even when the simulation work is completed by a team.
Direct answer
A useful reflection does more than describe whether the score rose or fell. It identifies the decision, compares like with like, cites results with units, explains a likely cause without overstating certainty, recognizes who or what absorbed a tradeoff, and proposes a next test that could challenge the conclusion.
The journal below separates four moments that students often collapse together: prediction, observation, interpretation, and revision. That separation makes reasoning visible and discourages after-the-fact claims that every result was expected.
Before the run, name the changed input, expected direction, affected metrics, and a reason. A prediction is not graded for being correct.
Copy comparable outputs with units. Mark surprises and data-quality concerns without explaining them yet.
Connect the changed input to the result, identify an alternative explanation, and state how confident the evidence permits the team to be.
Keep, reject, or qualify the idea. Design one controlled next test and name the result that would change the recommendation.
Use the prediction box, one three-metric comparison, and the claim-evidence-tradeoff exit ticket.
Teacher check: Can the student point to a number that supports the claim?
Complete one baseline, one controlled change, the interpretation prompts, and one individual exit ticket.
Teacher check: Did the student separate observation, inference, and assumption?
Duplicate the decision entry after each test. Finish with the synthesis and self-assessment on printable page three.
Teacher check: Did the team's strategy change in response to evidence?
Students can use the free student business calculators to check differences, margins, break-even quantities, and unit economics. Calculation accuracy does not replace interpretation.
Printable page 1
Decision question: How does changing __________ affect __________ and __________?
Prediction before the run: I expect __________ to change from __________ to __________ because...
One input changed:
Important conditions held constant:
| Measure and unit | Baseline | Changed run | Difference |
|---|---|---|---|
Surprising result or data-quality concern:
Printable page 2
What I directly observed:
My explanation of the likely cause:
An alternative explanation or missing factor:
Tradeoff and affected stakeholder:
Non-negotiable guardrail involving safety, fairness, privacy, accessibility, law, or another duty:
What this simplified model cannot establish about a real business:
Next controlled test, success measure, and stop condition:
Evidence that would make me revise my recommendation:
Printable page 3
My initial strategy and how it changed:
The strongest result across all runs, with numbers and units:
The most important mistake, failed prediction, or uncertainty and what I learned from it:
My final qualified recommendation:
One question I would investigate with better real-world evidence:
I cited comparable metrics. I separated observations from assumptions. I identified a tradeoff.
I stated a model limitation. I proposed a repeatable next test. I named what could change my mind.
My contribution to the team's reasoning:
I recommend ___ because ___ changed from ___ to ___. The important tradeoff is ___.
I expected ___. Instead I observed ___. I now think ___ because ___.
This simulation helps us examine ___. It cannot tell us ___ because ___.
The decision benefits ___. It may burden ___. A responsible guardrail is ___.
Next I would change only ___, measure ___, stop if ___, and revise my view if ___.
Preselect the decision and measures, provide word banks for increase/decrease/unchanged, allow labeled sketches or oral responses, and use one exit-ticket sentence frame. Keep the requirement to cite evidence.
Require repeated trials, percentage differences, competing explanations, confidence ratings, sensitivity tests, or a short critique of which omitted real-world evidence could reverse the recommendation.
Let the team share the evidence table, then ask every student to complete the interpretation and next-test prompts independently. Compare answers in a two-minute conference or peer challenge.
Project teacher-run scenarios or distribute printed result cards. Students can still predict, calculate differences, interpret evidence, and design a follow-up without operating the simulator themselves.
Students should identify the decision, compare a baseline with a changed run, cite specific metrics, explain a tradeoff, distinguish observations from assumptions, name a model limitation, and propose a controlled next test.
Use a short checkpoint before and after each meaningful run. For a single lesson, one prediction and one exit ticket may be enough; for a longer project, collect a decision entry after every test and a final synthesis.
Yes. Teams may share the run data, but each student should independently explain one result, tradeoff, limitation, and next test. This gives teachers evidence of individual reasoning without duplicating the entire team record.
No. A teacher or team operator can project the simulation or share printed results while every student completes an individual prediction, evidence interpretation, and exit ticket.
No. Grade the quality of the question, comparison, evidence, reasoning, responsibility, and reflection. A low-profit run can demonstrate strong learning when the student diagnoses it honestly and designs a better next test.
Use the assessment and feedback toolkit to plan the sequence, choose an activity from the lesson-plan directory, copy the assignment template, organize groups with the team role cards, collect longer project artifacts in the evidence portfolio and progress tracker, assess the journal with the 16-point rubric, and finish with the debrief question bank. The teacher hub links to every simulator and worksheet.