What does a business simulation facilitator do?
A facilitator protects the learning cycle: question, prediction, controlled action, evidence, explanation, and next decision. The teacher does not need to explain every control or rescue every weak result. Instead, the teacher makes the task and boundaries visible, listens for reasoning, notices shared blockers, asks questions that return students to evidence, and ends play early enough for reflection.
Before the run
Narrow the decision, preview access barriers, publish roles and evidence, and define what students must hold constant.
During the run
Circulate for process evidence, use short prompts, stop unsafe or unfair choices, and reset only shared misconceptions.
After the run
Compare claims, surface tradeoffs, separate model results from real-world proof, and require a bounded next step.
Choose a route before students begin
| Route | Launch | Investigation | Evidence and close |
|---|---|---|---|
| 20 minutes | 3-minute question, controls, prediction | 8-minute baseline and one change | 5-minute pair check, 4-minute exit claim |
| 50 minutes | 7-minute model and team setup | 22-minute baseline, test, and repeat | 8-minute evidence check, 10-minute debrief, 3-minute exit |
| Two sessions | Session 1 launch and investigation | Comparable repeats plus calculation or chart | Session 2 peer review, briefing, and revision |
| One device | Project controls; teams submit predictions | Teacher operates the voted test | Teams analyze the same result independently |
Plan backward from the close: if students must submit an evidence-based recommendation, protect at least the final 20 percent of class for comparison, explanation, and revision. A shorter completed reasoning cycle is more useful than an unfinished long game.
Use the PAUSE facilitation loop
- P — Prepare the decision: name the stakeholder, choice, outcome measure, time horizon, and non-negotiable boundary.
- A — Ask for a prediction: students state what should change, why, and what result would challenge their belief before operating.
- U — Unstick with questions: ask for the baseline, changed variable, relevant dashboard measure, unit, or smallest comparable next run.
- S — Safeguard the process: protect equitable roles, accessible participation, records, privacy, safety, legality, and truthful interpretation.
- E — Exit through evidence: stop play, compare results, name uncertainty and tradeoffs, then commit to an action, monitor, and stop rule.
A useful 45-second group conference
- “What decision question are you answering?”
- “What changed, and what did you keep constant?”
- “Which result with a unit best supports or challenges your prediction?”
- “What is the smallest useful next test?”
If students can answer, leave them with ownership. If they cannot, point to the task card or evidence record and ask them to reconstruct the missing step. Supply the decision only when the learning target is following a modeled procedure rather than making and defending a choice.
Match the intervention to the problem
| What you notice | Teacher move | Avoid |
|---|---|---|
| One group cannot find a control or measure | Point to the named area, reread the task, or provide an interface map | Stopping every group for a tour they do not need |
| Several groups change many variables | Run a two-minute reset: name one decision, baseline, one change, and controls | Accepting an uninterpretable run because it looks busy |
| A student is passive or one operator dominates | Pause that team, rotate roles, and ask each member for one prediction or interpretation | Grading device control as the whole contribution |
| A surprising result appears | Ask students to check units, period, saved settings, randomness, and repeatability | Calling it wrong solely because it differs from the teacher prediction |
| A choice risks safety, privacy, fairness, or law | Stop the choice, state the non-negotiable boundary, and redesign within it | Treating profit or score as permission to ignore real duties |
| Time is nearly gone | Freeze play, capture the current comparison, and move to an exit claim | Using reflection time for “one more run” |
Printable teacher page
Launch, monitor, and debrief checklist
Launch
☐ One decision question and stakeholder are visible
☐ Outcome measure, unit, and time period are named
☐ Baseline, one main change, and controls are clear
☐ Students record a prediction before operating
☐ Roles, rotation, and individual evidence are set
☐ Device and no-device routes are ready
☐ Permitted help and integrity expectations are stated
☐ Safety, legal, privacy, and fairness boundaries are stated
Monitor
| Team code | Prediction before action? | Comparable run and record? | Participation / access check | Prompt or follow-up |
|---|---|---|---|---|
Debrief
☐ Stop play with evidence time protected ☐ Compare at least two claims ☐ Ask for units and calculations ☐ Name a tradeoff and model limit ☐ Check responsible boundaries ☐ Collect an individual exit response
Shared misconception to address next time:
Access or participation adjustment for next time:
Debrief results without declaring one winner
Invite two teams with different conclusions to state the decision, comparison, and strongest measure. Ask the class whether the evidence differs, the interpretation differs, or the teams used different constraints. Then test the boundary of each claim: would it still hold with lower demand, higher costs, less cash, or a stricter safety requirement?
- Result: What changed numerically, with what unit and period?
- Explanation: What mechanism might connect the decision to the result?
- Alternative: What else, including model randomness or an uncontrolled setting, could explain it?
- Responsibility: Which legal, safety, privacy, accessibility, worker, customer, or advertising duty constrains the decision?
- Transfer: What action is supported, what should be monitored, and what would trigger revision or stopping?
Score the quality of the evidence chain, not the highest simulated profit. A losing strategy can produce excellent learning when students identify why it failed, correct the comparison, and specify a better next test.
No-device café case with facilitation notes
Case: A café has 100 morning customers available. With one barista it serves 78, average wait is 9 minutes, labor costs $160, waste costs $40, rating is 3.5/5, and profit is $220. A team proposes adding a barista and a promotion at the same time. Their changed run serves 94, wait is 5 minutes, labor costs $230, promotion costs $45, waste costs $55, rating is 4.1/5, and profit is $226.
First teacher prompt: “Which decision are you trying to evaluate?” Students should notice that staffing and promotion changed together. Ask them to select one variable, predict its mechanism, and design two matched paper tests rather than interpreting the combined run as proof.
Evidence prompt: “What improved, by how much, and what tradeoff appeared?” Served demand rose by 16 customers, wait fell 4 minutes, rating rose 0.6 points, and profit rose only $6 while the listed labor, promotion, and waste costs rose by $130 in total. The information supports further controlled testing, not a claim that both changes are always worthwhile.
Exit response: Students choose a staffing-only or promotion-only test, name settings to hold constant, identify profit plus one service measure and one guardrail, and write a stop rule. No device is required to practice the complete reasoning cycle.
Keep facilitation accessible, private, legal, and ad-safe
- Provide written and spoken directions, visible time checks, keyboard-compatible routes, readable records, and equivalent individual, pair, projected, or paper participation.
- Use fictional business information and team codes. Do not enter student personal data, real customer records, confidential employer data, or sensitive traits.
- Do not reward unsafe staffing, unlawful discrimination, deceptive claims, hidden sponsorship, privacy intrusion, accessibility barriers, or other prohibited conduct even if a simplified score improves.
- Keep any advertising separate from simulator controls, task directions, downloads, and required classroom actions. Never require or reward ad views or clicks.
- Present simulations as simplified learning models. Results are not financial, legal, employment, safety, or professional advice and do not establish real-world causation.
For detailed planning, pair this page with the accessible classroom guide and the academic integrity and responsible AI guide.
Frequently asked questions
How should a teacher introduce a business simulation?
Start with one decision question, a short tour of only the controls students need, a prediction, and a clear evidence record. Explain the time limit, group roles, permitted help, and responsible boundaries before the first run.
When should a teacher pause a business simulation lesson?
Pause when many groups share the same blocker, students are changing several variables without a record, a safety or fairness boundary is at risk, or too little time remains for evidence and debrief. Use a brief whole-class reset, then return control to students.
How can teachers help without giving away the answer?
Ask students to restate the question, locate the relevant measure, name what changed, compare it with the baseline, and choose the smallest next test. Provide process support or a sentence frame before suggesting a business decision.
What should teachers observe during a business simulation?
Observe whether students predict before acting, change one main variable, record units and time periods, involve every team member, distinguish results from explanations, and use legal, safety, privacy, and fairness constraints.
Can this facilitation guide work with one device or no devices?
Yes. Project one teacher-controlled simulator and collect team recommendations, or use the printable café case on this page. Students can still predict, calculate, compare, challenge a claim, and recommend a bounded next test.
Build the complete classroom sequence
Choose a subject in the lesson-plan directory, prepare a low-device or outage route with the technology contingency guide and RESTORE plan, assign equitable work with the printable team role cards, capture process evidence with the observation and conference toolkit, and close with the debrief question guide.