Velocity Arena — Facilitator Experience Map

Section 01

Environment as Curriculum

Before Day 1 — Setup

Physical Space

Four corners, four stats

Label each corner of the room with a stat name (Speed, Endurance, Turning, Power) before any student arrives. Students will physically move to stat corners during activities. The labels must be there on Day 1.

Driving Question

Visible from every seat

If it is not visible from every seat, it does not function as a driving question. Post it large. Leave it up all four weeks. Students read the walls before they read the materials.

Bot-Naming Wall

Empty slots, ready to fill

Pre-label slots for each team's bot name and origin story. The empty labeled slots signal that something meaningful will go there — this is an invitation before it becomes an artifact.

Also ready before Day 1: stat allocation reference cards at every seat, sentence starters posted in the four categories, sample data dashboard printed and filled in for your own reference. The room says what the program is before you say a word.

Section 02

The Challenge Block

Every day — 45 to 70 minutes

When students are stuck
Productive struggle vs. genuine confusion
The pause creates thinking time — trust it. A student who has not answered in 5 seconds is usually still processing. A student who looks genuinely lost (not just thinking) needs a different response.

The distinction that matters

Struggling with the math vs. missing the vocabulary

Struggling with the math: wait, then ask a question that opens the thinking. Missing vocabulary blocking access: explain the term, then return the thinking to the student. Not knowing what a word means is not a thinking failure.

Redirecting correctness questions

"Did we do this right?"

Redirect to their own data: "What would a correct answer look like? Is that what you see?" The match result is the teacher. Your job is to keep students in contact with their own data, not to validate in real time.

When to step in

Frozen, not just slow

Guidance is appropriate when students are frozen and have no direction, when the task requirements are genuinely unclear, or when a vocabulary gap is blocking access. Discomfort with a hard problem is not the same as being lost.

The rule of thumb: If a student can state what they are trying to figure out, they are not lost — they are in productive struggle. If they cannot state the question they are working on, they need help finding it.

7

seconds of wait time

That pause is students thinking. Hold it until the threshold — 7 seconds is when processing becomes visible across all confidence levels, not just the students who answer first.

"Under 3 seconds, only high-confidence students respond. At 7 seconds, thinking is happening across the room."

Section 03

The First Loss Moment

Day 7 — First Season 1 match result

What you will see

The reaction varies — all of it is real

Some students go silent. Some get angry. Some laugh it off. Some look at the floor. All of these are genuine emotional responses to a competitive loss. None of them signal that your facilitation is failing. They signal that the stakes are real enough to matter.

Teacher action — Step 1

Acknowledge the emotion, genuinely and briefly

Acknowledge the emotion genuinely and briefly. Give the moment space. Don't redirect yet — warmth here is appropriate and real. Students need a beat to feel heard before they can engage with evidence. A brief acknowledgment before moving forward is not rescuing. It's human.

What to say

"That was a hard result. Take a moment."

The dropout risk

This is the moment that determines Week 3

Students who don't get a structured recovery after their first real loss disengage from the data. They stop predicting, stop revising hypotheses, stop caring about the dashboard. Everything from Week 3 onward depends on the loss recovery running correctly from Day 7.

What not to do

Three moves that cut students off from their data

Jumping straight to "let's look at the data" before acknowledging the emotion. Saying "you'll get them next time" — that skips the evidence step. Letting the team start the next match without completing all three recovery steps first.

What makes this moment different at the Championship (Day 15): The script does not change based on the stakes of the match. Higher stakes mean the emotion is more intense — not that the protocol should be longer or different. The three steps are the structure regardless of the match.

Section 04

3-Step Loss Recovery Protocol

Every match day — every losing team — Days 7–10, 13–15

Step 1

Acknowledge the Emotion

Don't explain, don't redirect yet. A brief word of acknowledgment is fine. The emotion needs a beat before it can become analysis. Warmth here is not rescuing — it's what makes Step 2 possible.

"That was a hard result. Take a moment."

Step 2

Locate the Decision

Open the dashboard. Find one specific decision — not the whole allocation, one stat — that most likely created the gap. Ask a question that puts the analysis in their hands: "Which stat's output was furthest from your prediction?"

"Your model predicted [X]. Actual was [Y]. That gap is the most interesting thing that happened today. Which decision created it?"

Step 3

Restore Agency

One hypothesis entry in the dashboard. Not a revised allocation — a written prediction of what would change if they made one specific change. This is the move that converts a loss into data rather than discouragement.

"What's the one change you'd make? Write it as a hypothesis: 'If we change [stat] from [X] to [Y], we expect [outcome] because [reason].'"

The steps are sufficient. Follow the sequence. Every losing team. Every match day. No team starts their next match without completing all three steps. The protocol does not change based on how intense the loss was — more emotion means Step 1 gets a few more seconds, not extra steps.

Section 05

Silence Protocol

Every time you ask a question — all 16 days

A tool, not a rule.

Ask the question. Stop talking completely.
Wait. Don't rephrase. Don't add "think about it." Scanning the room — writing, looking at data, leaning in — is fine.
At ~7 seconds, look for a raised hand or visible processing. If you see it, call on them.
If no one responds at 8 seconds, use Turn and Talk — not a repeat of the question.
After Turn and Talk, return to the original question. You will get responses.

Why 7 seconds matters: wait time under 3 seconds produces short answers from high-confidence students only. 7 seconds activates processing across all confidence levels. The pause is a tool — it creates thinking time for students who don't answer fast. If you notice a student in genuine distress rather than productive thinking, respond to the student. The silence is in service of thinking, not a rule to follow at all costs.

Section 06

Circulating During Work Time

Every Challenge Block and Match-Build-Make — what to look for

1

Check the dashboard first
Before approaching any team, look at their data entry. A blank prediction field or a missing post-match row is the most actionable signal. Data integrity issues are visible before you reach the table.

Listen for: silence at a table where there should be work happening.
2

Identify productive struggle vs. frozen confusion
A team discussing what to try is in productive struggle — don't interrupt. A team that has been still for more than 90 seconds with no conversation or writing is frozen. That is the team to approach.

Listen for: "We don't know what to do" vs. "Wait, let me try something."
3

Ask a question that opens — don't give the answer
Your first move with any team should be a question. "What are you trying to figure out right now?" surfaces whether they have a direction. If they can answer, they are not lost. If they cannot, that is the thing to work on first.

Exception: if the task requirements are genuinely unclear, clarify them. Confusing the task with confusion about the math is a common facilitator error.
4

Exit clean — return thinking to the team
After your question, step back. Don't wait for the answer. Let them work. Coming back in 3 minutes tells you more than standing over them for 3 minutes.

Listen for: the team resuming work after you step away — that is the signal the question landed.
5

Flag the mathematically significant moments
When a team says something worth sharing — a pattern they found, a hypothesis they've named, a gap they can articulate — note it. These become the material for full-group discussion. "Before we move on — Team 3, say what you just told me."

Listen for: a gap sentence with all three parts, a correct percent change with the calculation shown, a hypothesis with a specific number.

Section 07

Hold the Gap — Talk Move

After every question — the most-violated protocol in the program

Move	When to Use It	What to Do	What to Avoid
Hold the Gap	After asking a question — every time. Wait the full 7 seconds before doing anything else.	Wait 7 full seconds. Don't rephrase or prompt. Then Turn and Talk if still nothing — not a repeat of the question. If you can see a student is genuinely lost (not just thinking), a brief redirect is fine. The goal is thinking, not silence for its own sake.	Jumping in before 7 seconds, restating the question, calling on the same eager hand every time, filling silence with "take your time" or hints
Press for Evidence	Any time a student makes a claim without a number	"Where in your data does it show that?" or "Which formula supports that claim?"	Accepting "I think" or "it feels like" as complete answers
Turn and Talk	When a question needs processing time before public sharing, or when Hold the Gap hits 8 seconds with no response	"Take a minute — tell your partner what you'd change about your allocation and why." Maximum 90 seconds. Always debrief after.	Giving more than 90 seconds; skipping the debrief; using it as a substitute for the original question rather than a path back to it
Revoice	When a student says something mathematically significant but unclear	"So you're saying that raising Speed by 2 reduces your remaining budget by 2 — is that right?"	Paraphrasing in a way that adds precision the student didn't provide — that's answering for them
Add On	After one student shares, to pull in others without breaking momentum	"Who can build on that?" or "Does anyone see a connection to what we worked on yesterday?"	Restating the previous answer before prompting the next student