What this system does: Supports facilitators in acting as cognitive coaches — modeling strategically, intervening selectively, and preserving student ownership of thinking. Facilitators should model, clarify, and teach when needed. The goal is adult support that leaves students responsible for thinking. Protocols constrain common failure modes; architecture reduces facilitator burden; the Minimum Success Floor in Layer 2 sets a realistic baseline.
← Facilitation Toolkit · Facilitator Guide

Protocol Cards

Physical. Portable. Ultra-short. Memorize the steps. Do not improvise.

Minimum Success Floor — if you do these five things consistently, the program works
✓
Students are participating — talking, writing, or building. A student who has stopped is a signal to act.
✓
The room is emotionally safe. Students take intellectual risks when they aren't afraid of embarrassment. Safety before rigor.
✓
You ask students to explain their reasoning, not just give answers. "How did you get that?" matters more than most protocols.
✓
You redirect answers to data or back to students, rather than providing solutions directly.
✓
Students are allowed to revise after mistakes. Error → correction is the learning sequence. Don't skip it.
These five, done consistently, produce a functional learning environment. The protocol cards in this layer are optimizations built on this floor — not substitutes for it.
These are diagnostic prompts, not performance scores. If you catch yourself monitoring your talk ratio or timing your silences while facilitating, you're watching the wrong thing. Watch the students.
Guidance Ladder — when and how much to intervene
Start at the lowest rung that might work. Move up only if the student remains stuck after a genuine attempt.
Silence is useful only when students are still thinking. If students are frozen, confused, dysregulated, or withdrawn, intervene earlier.
1
Wait. Hold silence for 15–30 seconds. Students often solve it themselves if given the pause.
2
Name what you notice. "You've been on that number for a bit — what are you thinking?" Surfaces the student's reasoning without providing any.
3
Ask a clarifying question. "What did your prediction say?" or "What does the graph show between those two points?" Narrows the problem without answering it.
4
Redirect to a resource. "Check the dashboard — that stat is in there." Points students to the tool they already have.
5
Give the method, not the answer. "The formula is (new − old) ÷ old × 100. You have the numbers." Student still does the work.
6
Model one example. "Here's how I'd set this up. Now you do the next one." Show it once. Hand it back immediately.
7
Direct instruction. Explain the concept fully when the student has no entry point and no resource will unlock it. Use sparingly — if you reach this rung frequently, that's a signal to revisit the task design or the student's readiness for that concept.
When in doubt
1Make the room safe
2Ask for reasoning
3Point to data
4Keep students participating
5Let mistakes become revision

Facilitator Simulation Training

Train via reps, not reading. Pick your response, then reveal. Run through all scenarios before Day 1 and again after Day 4. The last section trains facilitator self-awareness — because you are often the unstable variable.

System Architecture

Physical setup and system-level triggers reduce what depends on facilitator memory under pressure. Do these before Day 1.

Program Goals
🔁
Goal 1 · Transfer of Mathematical Reasoning
Students use mathematical formulas as predictive models of robot behavior, not just as procedures to execute. They generate predictions, compare them to what actually happens on the field, and revise their equations or assumptions when the two do not match. They can point to at least one specific change in their equation or parameters that reduced the gap between predicted and actual performance in later matches.
📐
Goal 2 · Genuine Intellectual Ownership
Students develop and defend their own mathematical models of the game, even when those models differ from other teams' equations, rather than copying a "right answer" from the teacher or from another group. They can explain why they chose a particular representation or equation, and they test their models against real match data. They can show at least one instance where they compared their model to another team's and made a specific decision about what to keep or change in their own equation, and can explain why.
Portfolio / stretch (documentation, not the goal sentence): in at least one case, they can trace how that keep/change decision led to improved fit to data or better match performance.
🔴
Goal 3 · Productive Relationship with Failure
Students treat losses, wrong predictions, and residual error as essential data for learning, not as detours or dead ends. They use structures like the Loss Recovery Protocol, gap sentences, and a residual error rule to name what went wrong, adjust their strategy or math, and try again. They can point to specific failures that led to measurable improvement in their models or performance (for example, reduced residual error, more consistent times, or better match results).
🎓
Goal 4 · The Ability to Teach
Students can explain their formulas and strategies clearly enough that a visitor can successfully complete all three mini-challenges after one explanation. They break ideas into steps and use the field and robot behavior as concrete examples, adjusting their explanations when someone is confused. They can document which explanations or demonstrations led visitors to complete the mini-challenges independently on the first try, and revise their explanations if visitors do not reach that standard.
Implementation note (Goal 2): Evidence for this goal often appears when teams encounter other teams' equations. Plan at least one "model comparison" activity or template so students can capture, in a single place, how they compared another model to their own, what they chose to keep or change, and why.
Room Setup
🏟️
Arena Layout
Tape or place space for 4 Velocity Arenas + 1 Skills Arena. Mats are 8×4. Leave enough clearance that students can stand back from all sides. Bots must not read students as balls.
📌
Wall Space
Room environment is curriculum. Students read the walls before they read the materials. Set up before Day 1: four corner labels (one per stat name); Driving Question poster, large and visible from every seat; bot-naming wall; Commissioner's rules wall; rivalry card display; skills badge wall.
🖥️
Dashboard Screen Position
Facilitator-facing dashboard visible during all match blocks.
Appendix: Extended notes on group dynamics and system design
Four ways group dynamics can concentrate around one student
Intellectual: Their framing of a problem becomes the team's default before anyone else forms a different hypothesis.
Physical: They migrate to other teams' workspaces during any gap in structure. Proximity tends to generate collaboration, which removes individual sense-making.
Social: Other students defer in Commissioner's Meetings, pitch preparation, and prediction choices. Deference is invisible until it becomes the default.
Recovery: After losses, they recover fastest and frame the team's interpretation before quieter students have finished processing.
Signs the protocol system is overloaded
Facilitators are reading protocol cards live during sessions. Cards are preparation tools, not real-time references.
Execution varies significantly between facilitators. This is a design problem, not a training problem.
Systematic cuts happen on match days. The protocol exceeds the actual conditions it was designed for.
The right response is better architecture (auto-triggers, physical constraints), not more protocols.
Contribution visibility (future feature)
A facilitator-facing view that shows contribution count per student: predictions logged, dashboard prompts answered, calculations completed. Makes airtime imbalance visible before it becomes a cultural norm. Not yet implemented.